-
Notifications
You must be signed in to change notification settings - Fork 1k
Dep init fails with "Unable to update checked out version: fatal: reference is not a tree: " #928
Comments
hi, welcome! thanks for the issue 😄
there is - it should be at could you tell me the output of |
Hi @sdboyer, thanks for your help. I attached the files you requested. git-branch.txt Is there any documentation about |
ah, i don't need the git output from your project, sorry - i need it from what's in
there isn't any specific documentation about it, primarily because it's an implementation detail that users, ideally, shouldn't have to worry about. but, we should definitely add just a general FAQ item about the source cache area. |
Ah. Sorry. I was just on the wrong machine. I'm going to upload it again. |
@sdboyer I'm a bit confused. I just checked the files again. The files given up there, are from within What I can tell is, that after removing the cache, it works now, but this is kinda cumbersome. I attached the newly generated files + the old ones as I backed up the "old" repository of
git-branch-25c4ec8.txt This is the repository causing the issue: |
unfortunately, this means we can't investigate what may have gone wrong there, now 😢 😢 😢
right, ok, brief explanation about what's going on. the verbose output you see there is the solver trying to find a version of your dependencies that will work, according to various criteria (not an exhaustive list):
both 2 and 3 entail that we actually inspect the source code of
no argument - all of our design is geared towards not requiring the user to know or care about that cache area. we've gotten a lot better at this over the past couple months, but it seems you've found a hole! that's why i was hoping to inspect the state of the problem repository on disk - it might have given us a clue about what went wrong. |
No. 😄 I made a backup of the whole cache! After I put the old one in place, I get a similar error. Though I've got another package in "that" cache which makes
|
oh, brilliant! looking forward to more details, then 😀
…On August 4, 2017 10:45:15 AM EDT, "Dennis Günnewig" ***@***.***> wrote:
> nfortunately, this means we can't investigate what may have gone
wrong there, now :cry: :cry: :cry:
No. :smile: I made a backup of the whole cache!
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#928 (comment)
|
But how can I help to identify the problem? |
oh...wait, when i first responded to that comment, you didn't have the links to the files there. they're there now, i think that's what i need. i probably won't be able to get back to this for a bit, but it looks like the info we need is there. |
Good. I also attached the cached repository as tar.gz-file to the issue. Just in the case you need access to it. |
closing this one out, as whatever the underlying cause was, #1279 almost certainly has it covered. |
Had the same problem. Turns out this was because my project is the GOPATH and I opened the package in intelliJ with gofmt and goimports configured which resulted in all packages checked out in GOPATH/pkg/dep/sources to be formatter causing this problem. Had to add a scope to stop intellJ from running gofmt or goimport on these files. |
Generated with: $ rm -rf "$(go env GOPATH)/pkg/dep/sources" # to avoid errors like "Unable to update checked out version: fatal: reference is not a tree" # possibly [1] $ dep ensure -update using: $ dep version dep: version : v0.5.0 build date : git hash : 22125cf go version : go1.10.3 go compiler : gc platform : linux/amd64 features : ImportDuringSolve=false I haven't reviewed all of these changes, but I want this to pull in openshift/hive@b1cad987 (contrib/pkg/awstagdeprovision: Allow for OR filters, 2018-10-18, openshift/hive#47). [1]: golang/dep#928 (comment)
What version of Go (
go version
) anddep
(git describe --tags
) are you using?$ git describe --tags # => v0.1.0-310-g8a46f4d
What
dep
command did you run?What did you expect to see?
dep
generates theGopkg.toml
andGopkg.lock
What did you see instead?
Questions
The text was updated successfully, but these errors were encountered: