Importing configuration from godep. These are only initial constraints, and are further refined during the solve process.
Couldn't this tell me what package it's doing this for?
@mattfarina I'm not sure what you're referring to. Could you follow the issue template and provide some more details?
@mattayes The issue template doesn't work well for feature requests. It appears to be more targeted at bugs. But, here goes...
dep are you using (dep version)?commit 4c74ecd27d7c268e1e9ce6a043c10cf7c46db40f
It was installed with go get -u
卤 dep version
dep:
version : devel
build date :
git hash :
go version : go1.10
go compiler : gc
platform : darwin/amd64
features : ImportDuringSolve=false
dep command did you run?dep init
When dep imports config from another package manage I expected it to tell me what package it found the config in.
Importing configuration from godep. These are only initial constraints, and are further refined during the solve process.
Dep didn't tell me the dependency it was importing godep config from.
For example, in the message here log the dir this happened in relative to the vendor dir.
@mattfarina Is looking at the generated Gopkg.toml not enough for this (honest question: I don't know the answer)?
To follow on a bit here. I encountered the message while doing a dep init -v -skip-tools:
Importing configuration from vndr. These are only initial constraints, and are further refined during the solve process.
followed by what seemed like a long term hang. The first time I ctrl+c'd out of worry. I ran it agan and used strace on dep just showed it was in a wait state. Putting dep in the shell background and checking for new processes it looks like it was doing an ls-remote call to repos and then getting stuck at bitbucket.org/ww/goautoneg. I think the request here is to be more verbose about what is going on, at least when the verbose flag is used.
FWIW the issue I encountered was due to not having hg installed.
This worked for me: https://github.com/golang/dep/issues/1896
Or try doing a strace on dep init -v
Bitbucket hang is a known issue. See @theckman PR for an upgrade here - we can try to detect the SCM type before making a request.
If you also append .git or the Mercurial equivalent to the source URL the deducer will do a better job of figuring out git vs. Mercurial
the same problem.锛氾紙
Importing configuration from godep. These are only initial constraints, and are further refined during the solve process.
dep init -v -skip-tools is work. thanks @ashcrow
Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!
Most helpful comment
To follow on a bit here. I encountered the message while doing a
dep init -v -skip-tools:followed by what seemed like a long term hang. The first time I ctrl+c'd out of worry. I ran it agan and used
straceondepjust showed it was in a wait state. Puttingdepin the shell background and checking for new processes it looks like it was doing anls-remotecall to repos and then getting stuck atbitbucket.org/ww/goautoneg. I think the request here is to be more verbose about what is going on, at least when the verbose flag is used.FWIW the issue I encountered was due to not having
hginstalled.