-
Notifications
You must be signed in to change notification settings - Fork 18k
x/vgo: failure to download when tag does not contain patch version #24024
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
Same here. [edit] |
This has me stuck in dependency purgatory. How do I tell vgo to use a commit hash instead of a tag? Do I need to suss out the timestamp of the commit and just shoehorn |
That was my workaround. It seemed to be fine. I don't believe the timestamp has to match the commit hash, either. But getting it close is probably a good idea to make updates work better. |
For those coming after us. vgo seems to ignore the timestamp(?) as any 14 digit number between the |
Actually this looks like a dupe of #23954, so I'll close this in favor of that. |
What version of Go are you using (
go version
)?go version go1.10 darwin/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?darwin, amd64
What did you do?
ran
vgo test all
in a module that depends on github.com/stretchr/objxWhat did you expect to see?
Tests running.
What did you see instead?
I believe this is caused by the repo having a v0.1 tag, which ends up parsed as
v0.1.0
internally, and it doesn't keep the original tag string, or something.The text was updated successfully, but these errors were encountered: