Skip to content
This repository was archived by the owner on Sep 9, 2020. It is now read-only.

dep fails to init docker #129

Closed
LK4D4 opened this issue Jan 24, 2017 · 16 comments
Closed

dep fails to init docker #129

LK4D4 opened this issue Jan 24, 2017 · 16 comments

Comments

@LK4D4
Copy link

LK4D4 commented Jan 24, 2017 

moroz@minigrind [±:master] docker % ~/project/workspace/bin/dep init
ouchie, solve error: No versions of github.com/gogo/protobuf met constraints:
        master: Could not introduce github.com/gogo/protobuf@master, as its subpackage github.com/gogo/protobuf/types is missing. (Package is required by (root).)
        v0.3: Could not introduce github.com/gogo/[email protected], as it is not allowed by constraint master from project github.com/docker/docker.
        v0.2: Could not introduce github.com/gogo/[email protected], as it is not allowed by constraint master from project github.com/docker/docker.
        v0.1: Could not introduce github.com/gogo/[email protected], as it is not allowed by constraint master from project github.com/docker/docker.
        master: Could not introduce github.com/gogo/protobuf@master, as it is not allowed by constraint master from project github.com/docker/docker.
        bigendian: Could not introduce github.com/gogo/protobuf@bigendian, as it is not allowed by constraint master from project github.com/docker/docker.
        bigskip: Could not introduce github.com/gogo/protobuf@bigskip, as it is not allowed by constraint master from project github.com/docker/docker.
        gopherjs: Could not introduce github.com/gogo/protobuf@gopherjs, as it is not allowed by constraint master from project github.com/docker/docker.
        ptypes: Could not introduce github.com/gogo/protobuf@ptypes, as it is not allowed by constraint master from project github.com/docker/docker.
        std: Could not introduce github.com/gogo/protobuf@std, as it is not allowed by constraint master from project github.com/docker/docker.
        wkt: Could not introduce github.com/gogo/protobuf@wkt, as it is not allowed by constraint master from project github.com/docker/docker.No versions of github.com/gogo/protobuf met constraints:
        master: Could not introduce github.com/gogo/protobuf@master, as its subpackage github.com/gogo/protobuf/types is missing. (Package is required by (root).)
        v0.3: Could not introduce github.com/gogo/[email protected], as it is not allowed by constraint master from project github.com/docker/docker.
        v0.2: Could not introduce github.com/gogo/[email protected], as it is not allowed by constraint master from project github.com/docker/docker.
        v0.1: Could not introduce github.com/gogo/[email protected], as it is not allowed by constraint master from project github.com/docker/docker.
        master: Could not introduce github.com/gogo/protobuf@master, as it is not allowed by constraint master from project github.com/docker/docker.
        bigendian: Could not introduce github.com/gogo/protobuf@bigendian, as it is not allowed by constraint master from project github.com/docker/docker.
        bigskip: Could not introduce github.com/gogo/protobuf@bigskip, as it is not allowed by constraint master from project github.com/docker/docker.
        gopherjs: Could not introduce github.com/gogo/protobuf@gopherjs, as it is not allowed by constraint master from project github.com/docker/docker.
        ptypes: Could not introduce github.com/gogo/protobuf@ptypes, as it is not allowed by constraint master from project github.com/docker/docker.
        std: Could not introduce github.com/gogo/protobuf@std, as it is not allowed by constraint master from project github.com/docker/docker.
        wkt: Could not introduce github.com/gogo/protobuf@wkt, as it is not allowed by constraint master from project github.com/docker/docker.

moroz@minigrind [±:master] docker % go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/moroz/project/workspace"
GORACE=""
GOROOT="/home/moroz/go"
GOTOOLDIR="/home/moroz/go/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build254478034=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"

I've removed vendor dir before doing init :)
@jessfraz
Copy link
Contributor

jessfraz commented Jan 24, 2017 via email

@jessfraz
Copy link
Contributor

#116

@jessfraz
Copy link
Contributor

I wonder if this is hitting the rate limiting problem and just had it all locally

@jessfraz
Copy link
Contributor

jessfraz commented Jan 24, 2017 via email

@sdboyer
Copy link
Member

sdboyer commented Jan 24, 2017 •
edited
Loading 

        master: Could not introduce github.com/gogo/protobuf@master, as its subpackage github.com/gogo/protobuf/types is missing. (Package is required by (root).)

Errors like this are vaguely familiar to me - protobuf generated code(?). I don't have an immediate solution, but this was the original root problem in the solve, and doesn't look like it would have been caused by API rate limiting. That package just wasn't there in master.

@LK4D4
Copy link
Author

LK4D4 commented Jan 24, 2017

@sdboyer It looks like it's in master though
https://github.com/gogo/protobuf/tree/master/types

@sdboyer
Copy link
Member

sdboyer commented Jan 24, 2017

Indeed, and since Aug 26. Might be a bug, then. Curious...did @jessfraz suggestions help? If not, did you have github.com/gogo/protobuf on your GOPATH when you ran dep init? If so, what branch/rev was it at?

@LK4D4
Copy link
Author

LK4D4 commented Jan 24, 2017

On second run I've encountered another error:

ouchie, solve error: No versions of github.com/docker/distribution met constraints:
        master: Could not introduce github.com/docker/distribution@master due to multiple problematic subpackages:
        Subpackage github.com/docker/distribution/digestset is missing. (Package is required by (root).)        Subpackage github.com/docker/distribution/registry/client/auth/challenge is mis
sing. (Package is required by (root).)

Both packages are exist at the master of distribution.
I wonder if there is way to specify versions first and then vendor them.
I have github.com/gogo/protobufin GOPATH indeed and it has 74b6e9deaff6ba6da1389ec97351d337f0d08b06 revision where there is no types package. On other side it's quite weird to depend on any package in GOPATH for init.

@jessfraz
Copy link
Contributor

jessfraz commented Jan 24, 2017 •
edited
Loading

yeah ok when the errors change like that, in the past for me it means rate limiting :( #115

@LK4D4
Copy link
Author

LK4D4 commented Jan 24, 2017

@jessfraz Cool. So, we need ratelimit in tool and better error reporting :)

@sdboyer
Copy link
Member

sdboyer commented Jan 24, 2017

I wonder if there is way to specify versions first and then vendor them.

This is one of the issues I need to write up - yes, we've discussed and would like to add some different init modes, rather than just inferring from GOPATH.

On other side it's quite weird to depend on any package in GOPATH for init.

Depends on your perspective :) In the simple/vanilla Go user case that still just uses GOPATH, it's certainly the right approach. For people who use a tool, something else is needed. Which is what those different import modes is about.

If you just remove these projects from your GOPATH, then you'll probably have better results - doing so will make dep init just operate from info available upstream.

I have github.com/gogo/protobufin GOPATH indeed and it has 74b6e9deaff6ba6da1389ec97351d337f0d08b06 revision where there is no types package.

Ahh yeah - that'd do it! It does highlight another thing I need to do in gps, though - we should make sure to visit the upstream state of master, too. So many issues to write today...

@sdboyer
Copy link
Member

sdboyer commented Jan 24, 2017

@jessfraz Cool. So, we need ratelimit in tool and better error reporting :)

yep! ratelimit over at #115; error reporting in #22 as a placeholder, and I'm writing a bigger issue about it, too.

@LK4D4
Copy link
Author

LK4D4 commented Jan 24, 2017 

If you just remove these projects from your GOPATH.

Heh, it's not really a cool option. I can try in empty gopath instead.

@LK4D4
Copy link
Author

LK4D4 commented Jan 24, 2017

I'm closing this as dupe of #115 to reduce noise.

@LK4D4 LK4D4 closed this as completed Jan 24, 2017
@sdboyer
Copy link
Member

sdboyer commented Jan 24, 2017

Heh, it's not really a cool option.

Totally fair - state mutation in GOPATH is never really an option. It's why we're in this mess! :)

I can try in empty gopath instead.

That should do it!

@jessfraz
Copy link
Contributor

jessfraz commented Jan 24, 2017 •
edited
Loading

this is terrible advice but if you want it to eventually work for now just continually running it after like 2 times w the rate limit and waiting should work, well it did for me, but yeah sad story, it just needs to populate the cache

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sdboyer @LK4D4 @jessfraz