New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing vendors #1778
Fixing vendors #1778
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with latest version of dep. I would expect that dep ensure (without removing the lock file) would recreate the same vendor folder content.
$ rm -rf vendor
$ dep ensure
ensure Solve(): No versions of github.com/opencontainers/runc met constraints:
v0.1.1: Could not introduce github.com/opencontainers/runc@v0.1.1 due to a case-only variation: it depends on "github.com/Sirupsen/logrus", but "github.com/sirupsen/logrus" was already established as the case variant for that project root by the following other dependers:
(root)
github.com/docker/distribution@edc3ab29cdff8694dd6feb85cfeb4b5f1b38ed9c
v0.1.0: Could not introduce github.com/opencontainers/runc@v0.1.0, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v0.0.9: Could not introduce github.com/opencontainers/runc@v0.0.9, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v0.0.8: Could not introduce github.com/opencontainers/runc@v0.0.8, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v0.0.7: Could not introduce github.com/opencontainers/runc@v0.0.7, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v0.0.6: Could not introduce github.com/opencontainers/runc@v0.0.6, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v0.0.5: Could not introduce github.com/opencontainers/runc@v0.0.5, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v0.0.4: Could not introduce github.com/opencontainers/runc@v0.0.4, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v0.0.3: Could not introduce github.com/opencontainers/runc@v0.0.3, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v0.0.2: Could not introduce github.com/opencontainers/runc@v0.0.2, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v0.0.1: Could not introduce github.com/opencontainers/runc@v0.0.1, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v1.0.0-rc4: Could not introduce github.com/opencontainers/runc@v1.0.0-rc4, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v1.0.0-rc3: Could not introduce github.com/opencontainers/runc@v1.0.0-rc3, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v1.0.0-rc2: Could not introduce github.com/opencontainers/runc@v1.0.0-rc2, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v1.0.0-rc1: Could not introduce github.com/opencontainers/runc@v1.0.0-rc1, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
master: Could not introduce github.com/opencontainers/runc@master, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
fs-named-cgroup: Could not introduce github.com/opencontainers/runc@fs-named-cgroup, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
relabel_fix_docker_1.9.1: Could not introduce github.com/opencontainers/runc@relabel_fix_docker_1.9.1, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
resource-hf: Could not introduce github.com/opencontainers/runc@resource-hf, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
v0.0.2.1: Could not introduce github.com/opencontainers/runc@v0.0.2.1, as it is not allowed by constraint 0.1.1 from project github.com/appcelerator/amp.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Tested on Mac.
I don't find this discrepancy. I followed the test steps described in the PR as well as tried the steps by @ndegory.
|
I've tested on Mac with different versions of dep, same result:
@neha-viswanathan can you please do the test again with: |
@ndegory tested with the steps you suggested. I don't see any errors. |
@ndegory I couldn't reproduce this issue either. Can you please:
|
|
There are no occurrences of Can you please run these commands in your
|
If my other projects' vendors impact what happens in amp, we're in trouble. I have indeed a few projects using a different case:
|
makes me think we should add dep in our gotools image and run it with ampmake to avoid any environmental impact. |
@ndegory yeah, adding dep to our build tools could fix your issue. Please open a ticket. |
now that the branch is rebased on master with the ampmake target for vendor installation, I still have the issue: |
Working great now with the --vendor-only. |
Fix https://techweb.axway.com/jira/browse/AMP-98
This PR fixes vendor (again).
The version for each dependency has been fixed so that we're less vulnerable to any transitive dependency update.
The code has been updated to comply with the new dependencies.
How to test
Make sure you have the latest release version of dep (0.3.2):
Test with the following instructions:
Note that your vendor folder may differ from the one committed on this branch. It's probably because transitive dependencies might have been updated in the meantime. For more details on how
dep
works, please read https://github.com/golang/dep/blob/master/docs/FAQ.md#how-do-i-constrain-a-transitive-dependencys-versionThen make sure the code compiles and tests as expected:
Check Travis build.