-
Notifications
You must be signed in to change notification settings - Fork 301
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
Migrate to Dep #317
Migrate to Dep #317
Conversation
It looks like you now have |
|
@samuelkarp, hmm, the logrus thing might be related to docker/libcompose#493. |
Yeah, we have a project of our own that depends on docker/libcompose as well as docker/docker and docker/cli, and we're blocked on moving to dep until they update their dependencies. Although with this merged it may help but I havent tried yet. You may want to try updating your dep to the latest master and trying the migration again. |
0d31395
to
ec85c18
Compare
d4e25ab
to
b7fe70d
Compare
145f9c2
to
d7adfeb
Compare
@rifelpet Out of curiosity, have you tried migrating to dep again recently? The case-sensitivity issue with logrus appears to have been fixed -- I'm in the process of trying this migration process again and it appears to be working with the latest version of dep, though it required a lot of manual dependency resolution on my end. |
@SoManyHs I did see it was fixed but have not had the chance to try migrating again recently |
Rebased on top of #412. |
what's left here for making this go from [wip] to not be wip anymore? |
f90f3c5
to
814156d
Compare
This seems like a spurious folder: https://github.com/SoManyHs/amazon-ecs-cli/tree/dep/ecs-cli/_vendor-20180112100655. Was that added by mistake? Or, is that required? If required, why is it required? |
@aaithal Oops, I thought I'd added that to the .gitignore but must have messed up. Should be fixed now--thanks for the catch! |
Can you also confirm if you need any changes to the |
@aaithal Yep, already on it. |
0491dae
to
8d2f800
Compare
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.
@SoManyHs i think we should explicitly constrain the dependencies to specific branch, version or revision in the Gopkg.toml
file.
Updated major dependencies (libcompose, golang.org/x/*, docker, Azure/go-ansiterm), largely to get rid of case-sensitive dependency collision of Sirupsen.
fd7c7cc
to
97dcef4
Compare
@@ -0,0 +1,66 @@ | |||
|
|||
# Gopkg.toml example |
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.
Should this example code be removed?
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.
i think the examples here are useful since there are a few ways to constrain your dependencies.
|
||
|
||
[[constraint]] | ||
name = "github.com/aws/aws-sdk-go" |
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.
Per @adnxn's comment, can you lock all of the dependencies on a specific version or githash, etc?
- From ecs-cli dir, ran `dep init` - Removed Godeps dir - Ran `make generate` (to update licenses)
Ran `dep ensure && dep prune` to get rid of unused vendor files added by `dep init` (dep v0.3.2)
- Updated Gopkg.toml manually (NOTE: Using the "revision" constraint is not usually recommended, but it was the easiest to do for the moment and would ensure consistency with what was previously in the Godeps manifest) - Ran dep ensure && dep prune (dep v0.3.2)
Okay, updated.
|
e40e223
to
402889b
Compare
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
we can close this now #282 |
Good catch. I'll close it when we next release. |
make build
succeeds