-
Notifications
You must be signed in to change notification settings - 8000 Fork 539
Unable to resolve update issue #432
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
Comments
I too am getting this error, with glide 0.10.2. It only started happening after I added an additional subpackage to Here is the before yaml:
Here is the after yaml:
Here is the error text:
Here is the full BEFORE glide.yaml:
Here is the full BEFORE glide.lock file:
|
I don't think it was a matter of adding that extra subpackage, I think it was an issue with having it regenerate the lock file, because even if I keep the same yaml file as before, but regenerate the lock file, then I still get the same error. |
This is the commit to golang.org/x/net that showed this problem in glide: golang/net@3b99394 Glide can't find Seems the maker's of x/net are using a library in a future version of golang... |
This may be related to some special handling logic that went in to glide in order to accommodate the core team's committing |
...or, yeah, it's the issue with needing to deal with release tags, as well as build tags, when deciding what to analyze. |
So what is interesting is that we have locked golang.org/x/net in glide.yaml
which is from back in February. Is there anyway to force glide to use this and not HEAD for it's analysis? Is this a challenge specific to glide's implementation or would I hit this with native vendoring? Any advice on how we can unblock development would be appreciated - Thanks! |
My temporary work around for now is to
Note the imported packages and add to
In the
A |
@radamsfc Thanks for a fantastic bug report. Glide should have been using New additions to the standard library are rare, thankfully. I'll fix this shortly. |
@mattfarina I built a version from your fix and it resolved our issues with |
Fixed #432: Issue with new net/http/httptrace std lib package
Thanks :) |
Could someone release a fixed version please? |
I'm still having this issue with latest master on go1.6. Is it supposed to be fixed? |
same...I am running into problems here with this on just the install command. Same net/http/httptrace problem. |
looks like patch was only for http/trace but i am having trouble with golang.org/x/net/publicsuffix.. |
Using glide 0.10.2
We have a glide.yaml and glide.lock generated from it. Glide install works fine.
Updating glide.yaml in any way and trying to run an update results in errors that I have been unable to identify the source after many hours of trying to resolve this.
glide.yaml
The update command used (and we have used many permutations) is
glide --home $(a_dir) update --cache --force --update-vendored --strip-vcs --strip-vendor --delete
We have deleted the cache, (btw there are errors that
cache/info
does not exist when the cache directory is first created - creating it makes the errors disappear) and used various permutations of that command.The first of many errors occurs here
Any thoughts on how we can identify the cause and resolve this?
FULL OUTPUT
The text was updated successfully, but these errors were encountered: