-
Notifications
You must be signed in to change notification settings - Fork 1k
dep does not import same revision for dependencies that are declared in Godeps.json #1070
Comments
I think it is the same as #1069. |
Imho, this one is different. While #1069 tracks the fact that unneeded packages are vendored as well as unneeded repositories (if that's what However, this one reflects a bigger problem. Currently |
Agreed, dep cannot currently be trusted to not make changes after the importers are run. The issue which tracks that is #908. |
@carolynvs do you think I should close this in favor of #908? |
Following the discussion golang#1070 (comment) "Agreed, dep cannot currently be trusted to not make changes after the importers are run. The issue which tracks that is golang#908.", it is clear that the maintainers of the tool do not see it as a reliable project. As such, the users should be correctly informed about the status of the project and what are the goals in order to make it a production ready one.
Before closing, I'd like to understand if the issue was that our godep importer didn't preserve the original revision in the lock, or if the constraints later caused the solver to pick a different version for the slack project. Can you run |
i did the
@carolynvs i think we have an issue open for this already? trying to use the comments from |
@sdboyer Ah okay, yeah this is part of a bigger question that I had about locking to untagged revisions during import. Can you take a look at my question and let me know what you think? #939 (comment) |
In the following project https://github.com/gopheracademy/gopher , running
dep init
.See:
Observe the difference between versions for
github.com/nlopes/slack
:dep version: f134697
gopher version: 7bb1dd8a82cff5fb8172bcb768d0decd9ba80420
The text was updated successfully, but these errors were encountered: