We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
% vgo version go version devel +104445e Wed Feb 7 19:22:09 2018 +0000 linux/amd64 vgo:2018-02-20.1
Some gopkg.in repos use tags instead of branches to tag the major versions. Here's one example:
% cat xx.go package main // import "github.com/rogpeppe/xx" import ( _ "gopkg.in/natefinch/lumberjack.v2" ) func main() { } % vgo build vgo: resolving import "gopkg.in/natefinch/lumberjack.v2" vgo: import "github.com/rogpeppe/xx" -> import "gopkg.in/natefinch/lumberjack.v2": unexpected status (https://api.github.com/repos/natefinch/lumberjack/commits?sha=v2&until=2018-02-21T09%3A22%3A29Z&per_page=2): 404 Not Found
The text was updated successfully, but these errors were encountered:
Change https://golang.org/cl/107658 mentions this issue: cmd/go/internal/modfetch: make gopkg.in support more seamless
cmd/go/internal/modfetch: make gopkg.in support more seamless
Sorry, something went wrong.
golang/vgo@84430ca
No branches or pull requests
Some gopkg.in repos use tags instead of branches to tag the major versions.
Here's one example:
The text was updated successfully, but these errors were encountered: