-
Notifications
You must be signed in to change notification settings - Fork 1k
dep ensure: Unable to update checked out version #618
Comments
When the vendored or local copy of a dependency has been dirtied, in this case with untracked files, I would think that dep shouldn't care, and just repave it with the desired revision? I dug through |
I think this may have something to do with the file mode changing. I saw something similar when changing branches on my own repo, with the same files vendored. |
Hmm...those errors aren't coming out of anything on My first thought is something like #553. @elliots, could you have a look at that directory and see what the actual state of the dirty tree is?
Yeah, I hope we can add this - #596. |
@carolynvs, from what I can see, we are calling git directly in vcs_repo.go. You should be able to call @elliots I am unable to reproduce this either by following your steps, nor by manually adding and editing files in the azure vendor or GOPATH location. Can you plese confirm if you still see this. BTW, I am using latest dep. |
I am having the same problem with 0.3.0:
|
Possible workaround: rm -rf $GOPATH/pkg/dep/sources/ |
yeah, this is nigh-guaranteed to work if you have this problem - this is a symptom of corruption in the cache area, which can happen if you ctrl-C at a moment when underlying git processes are unhappy with it (i don't know why git can't clean up better after itself 😢). we're thinking about putting some adaptive bad-state detection processes into place which should help a lot of these problems go away. |
i just threw up #1279, which takes a stab at doing the adaptive cleaning. |
The error message is Unable to update checked out version: error: The following untracked working tree files would be overwritten by checkout
Tried newer versions of the package, which failed in the same way.
Gopkg.toml
Output
Versions
go version go1.8 darwin/amd64
git version 2.11.0 (Apple Git-81)
Darwin thor 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64
The text was updated successfully, but these errors were encountered: