x/pkgsite: you cannot retract one module from a different module

[seancfoley]

The issue keeps getting closed with providing a proper resolution.

See #50631 and #50636

The simple declaration to use "retract", in both bugs, is insufficient. I cannot retract the existence of a go module away because a retraction requires creating a release of that same module. If there are two modules in play, how do you retract one module from the other module? The documentation for retract explains none of this.

If retraction is expected to work, I need to know what needs to be retracted from which module. Just stating the word "retract" is not providing a resolution here.

What is the URL of the page with the issue?

https://pkg.go.dev/github.com/seancfoley/ipaddress-go/ipaddr

What is your user agent?

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36

Screenshot

What did you do?

Move the go.mod from a subdir to the directory root so that I can use normal semantic versioning.

I have attempted to publish my module. The go modules documentation is not clear that you cannot use normal versioning numbering (eg v1.0.0) if you do not put the go.mod file at the root if the repository. So initially I had the go.mod in the main package ipaddr which is a directory in the repository. After a lot of trial and error, trying to figure out why the go tools would not work as I expected, I've now placed it at the root of the repo.

So my module is at https://pkg.go.dev/github.com/seancfoley/ipaddress-go

If I click on the "ipaddr" package is goes to https://pkg.go.dev/github.com/seancfoley/ipaddress-go@v1.0.2/ipaddr

On that page it has a red button "Go to latest" which takes me to my failed attempt to publish the package with the go.mod in a subdirectory. There are no versions in that failed attempt. Nor are the dates more recent. So it is clearly not the latest in any way, shape or form.

What did you expect to see?

I expect there to be no red button saying "Go to latest" taking you to a page which is not the latest.

What did you see instead?

I see a red button leading people to the wrong location. It takes you to a version of the package which is clearly not the latest, neither by date, nor by version. So the button should not be there, it is misleading.

[seankhliao]

modules are independent and have no relation with one another.

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.

For questions please refer to https://github.com/golang/go/wiki/Questions

[seancfoley]

"modules are independent and have no relation with one another"

exactly, that's what I already said