This repository has been archived by the owner on Sep 9, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1k
Sirupsen/logrus uppercase->lowercase rename breaks golang/dep #806
Comments
Ok, I resolved all of the issues locally. There was one more transitive dependency imporging the old uppercase logrus repository URL. Also, I had to Can we please error out early if we see conflicting |
hi! thanks for the detailed issue. definitely a known problem here - see #433. (the rename happened quite a while ago). erroring out, as you suggest, is probably our simplest recourse while we weigh the more complex solutions. (closing this as duplicate) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
github.com/Sirupsen/logrus (uppercase) recently renamed to github.com/sirupsen/logrus (lowercase)
Since one of our transitive dependencies switched to the new name, I was forced to switch as well.
So, I've renamed all the imports in our project to the new lowercase logrus and I've also updated the
Gopkg.toml
file manually.But running
dep ensure -v
failed with this error:Yes, I'm on MacOS (which has case-insensitive file system), so checking out the two conflicting repos is not possible.
Note: Actually, even
git
itself has troubles renaming a single directory name to lowercase. What a bummer.So I'm thinking there is probably yet another transitive dependency that is still importing the old uppercase repository and golang/dep is cloning it while resolving the dependencies. But which one? The error message coming from golang/dep is not useful at all.
I'm gonna dig deeper into my vendor/ directory and try to debug the problem and report back.
Any guidance / feedback appreciated, though.
What did you expect to see?
Useful error message on conflicting (lowercase/uppercase) repositories. I would like to know which transitive dependency introduced the conflict, if possible.
What version of Go and dep are you using?
go version go1.9beta1 darwin/amd64
dep v0.1.0-206-ge99676b
What
dep
command did you run?dep ensure -v
The text was updated successfully, but these errors were encountered: