Now go run main.go works as expected. However, go mod verify fails with the following message:
quote_alias v0.0.0-00010101000000-000000000000: missing ziphash: open hash: no such file or directory
What did you expect to see?
I expected go mod tidy to fix the go.mod file (which it did) and for go mod verify to accept the result.
What did you see instead?
The go mod verify command treated the requirement with a placeholder ZeroPseudoVersion as a real package, attempted to look for it and failed.
Shouldn't go mod verify ignore ZeroPseudoVersion-ed requirements on principle? After all, a ZPV is a synthetic placeholder, not a real version string. If the discussion here reaches this conclusion, I may already have a fix and a regression test ready for review.
The text was updated successfully, but these errors were encountered:
changed the title
go mod verify fails when requirement has ZeroPseudoVersionOct 22, 2021