This repository was archived by the owner on Sep 9, 2020. It is now read-only.
This repository was archived by the owner on Sep 9, 2020. It is now read-only.
Why did dep not used my imported version? #939
Description
Warning: I am testing dep out on Kuberentes, and am using a few fixes to the godep config file to get this far.
go version: go version go1.8.3 darwin/amd64
dep version: v0.2.1-1-ga085554 ( PR #938 )
The dependency on cloud.google.com/go was for 0.1.0-115-g3b1ae45, specifically the untagged revision 3b1ae45. After running dep init and importing the config from godep, that preferred/imported revision was ignored during solve. Or at least that's the way it looks.
dep init -v
Importing configuration from godep. These are only initial constraints, and are further refined during the solve process.
Detected godep configuration files...
Loading /Users/carolynvs/go/src/k8s.io/kubernetes/Godeps/Godeps.json
Converting from Godeps.json ...
... TRUNCATED
Using ^0.1.0-115-g3b1ae45 as initial constraint for imported dep cloud.google.com/go
Trying * (3b1ae45) as initial lock for imported dep cloud.google.com/go
... TRUNCATED
Root project is "k8s.io/kubernetes"
1506 transitively valid internal packages
439 external packages imported from 112 projects
(0) ✓ select (root)
... TRUNCATED
(3) ? attempt cloud.google.com/go with 1 pkgs; 15 versions to try
(3) try cloud.google.com/go@v0.11.0
(4) ✗ cloud.google.com/go@v0.11.0 not allowed by constraint ^0.1.0-115-g3b1ae45:
(4) ^0.1.0-115-g3b1ae45 from (root)
(3) try cloud.google.com/go@v0.10.0
(4) ✗ cloud.google.com/go@v0.10.0 not allowed by constraint ^0.1.0-115-g3b1ae45:
(4) ^0.1.0-115-g3b1ae45 from (root)
(3) try cloud.google.com/go@v0.9.0
(4) ✗ cloud.google.com/go@v0.9.0 not allowed by constraint ^0.1.0-115-g3b1ae45:
(4) ^0.1.0-115-g3b1ae45 from (root)
(3) try cloud.google.com/go@v0.8.0
(4) ✗ cloud.google.com/go@v0.8.0 not allowed by constraint ^0.1.0-115-g3b1ae45:
(4) ^0.1.0-115-g3b1ae45 from (root)
(3) try cloud.google.com/go@v0.7.0
(4) ✗ cloud.google.com/go@v0.7.0 not allowed by constraint ^0.1.0-115-g3b1ae45:
(4) ^0.1.0-115-g3b1ae45 from (root)
(3) try cloud.google.com/go@v0.6.0
(4) ✗ cloud.google.com/go@v0.6.0 not allowed by constraint ^0.1.0-115-g3b1ae45:
(4) ^0.1.0-115-g3b1ae45 from (root)
(3) try cloud.google.com/go@v0.5.0
(4) ✗ cloud.google.com/go@v0.5.0 not allowed by constraint ^0.1.0-115-g3b1ae45:
(4) ^0.1.0-115-g3b1ae45 from (root)
(3) try cloud.google.com/go@v0.4.0
(4) ✗ cloud.google.com/go@v0.4.0 not allowed by constraint ^0.1.0-115-g3b1ae45:
(4) ^0.1.0-115-g3b1ae45 from (root)
(3) try cloud.google.com/go@v0.3.0
(4) ✗ cloud.google.com/go@v0.3.0 not allowed by constraint ^0.1.0-115-g3b1ae45:
(4) ^0.1.0-115-g3b1ae45 from (root)
(3) try cloud.google.com/go@v0.2.0
(4) ✗ cloud.google.com/go@v0.2.0 not allowed by constraint ^0.1.0-115-g3b1ae45:
(4) ^0.1.0-115-g3b1ae45 from (root)
(3) try cloud.google.com/go@v0.1.0
(3) ✓ select cloud.google.com/go@v0.1.0 w/2 pkgs
I was expecting to see a line like this instead:
try cloud.google.com/go@3b1ae45
It's not clear from the output why the revision wasn't considered before those other versions? Is it because the constraint is for a version and not a branch?