x/pkgsite: package removal request for github.com/vinegarhq/vinegar and github.com/vinegar-dev/vinegar

[lunarlattice0]

What is the path of the package that you would like to have removed?

github.com/vinegarhq/vinegar

Are you the owner of this package?

Yes

What is the reason that you could not retract this package instead?

Currently, there are two vinegar packages, github.com/vinegarhq/vinegar and github.com/vinegar-dev/vinegar, both of which are outdated. Previously, we failed to follow the go recommendations for v2 releases which caused issues with the pkgsite, so we have reset our versioning back to v1.0.0. Ideally, we would like for there to be a singular github.com/vinegarhq/vinegar package with only the new v1.0.0 release available.

[findleyr]

Hi, this package removal request includes removing github.com/vinegarhq/vinegar, but you say that you want to github.com/vinegarhq/vinegar to be available?

That is not how removal requests work, I'm afraid: we can only remove paths entirely, not selected versions. To remove selected versions, you will need to use module retraction: https://go.dev/ref/mod#go-mod-file-retract

Can you please look into this, and let us know if you are able to achieve what you want with module retraction?

[lunarlattice0]

We currently have a versioning issue, which means the pkgsite has an old 1.0.0 version cached from February, while we currently have a new 1.0.0 from March. Will retracting 1.0.0 remove both versions or just one?

Additionally, the github organization name changed, so github.com/vinegar-dev/vinegar is safe to remove.

[lunarlattice0]

Just to reiterate, we are unsure what to specify to retract (as we have two 1.0.0s) but we are OK with the vinegar-dev link being removed.

[lunarlattice0]

Nevermind, the version retraction is a moot point. We have v1.0.1 now, so we will simply retract the other versions. However, we still need github.com/vinegar-dev/vinegar removed.

Thanks

[findleyr]

However, we still need github.com/vinegar-dev/vinegar removed.

This is done.

[apprehensions]

Could you also remove the import path github.com/vinegarhq/vinegar/v2? Vinegar is now on 1.0.1 and version 2 does not exist anymore.

Thanks.

[findleyr]

Will retracting 1.0.0 remove both versions or just one?

Retracting v1.0.0 will prevent the Go command from resolving v1.0.0.

@apprehensions you should be able remove github.com/vinegarhq/vinegar/v2 using module retraction. Just retract v2.3.5.

[findleyr]

(note that this retraction must be done with a v2 module: see for example #59577 (comment)).

It is probably not a good idea to exclude the v2 prefix, as if you ever decided to publish a v2 version in the future the exclusion would prevent it from being visible on pkg.go.dev.

[apprehensions]

go: downloading github.com/vinegarhq/vinegar v1.1.2
go: github.com/vinegarhq/vinegar@v1.1.2: parsing go.mod:
	module declares its path as: github.com/vinegar-dev/vinegar
	       but was required as: github.com/vinegarhq/vinegar