x/pkgsite: package removal request for github.com/timwehrle/alfie

[timwehrle]

Hi,
I'm running into an issue after renaming my project. Here's the error I'm seeing:

go install github.com/timwehrle/asana@latest
go: github.com/timwehrle/asana@latest: version constraints conflict:
	github.com/timwehrle/asana@v0.0.2: parsing go.mod:
	module declares its path as: github.com/timwehrle/alfie
	        but was required as: github.com/timwehrle/asana

I tried deleting the releases and tags from the repository, but that didn’t resolve the problem. What steps can I take to fix this? I want the package to be listed under github.com/timwehrle/asana instead of github.com/timwehrle/alfie.

For context, I didn’t release v0.0.2 for the Asana package—this seems to be leftover from the previous repository.

Thanks in advance!

[Jorropo]

https://pkg.go.dev/github.com/timwehrle/asana works for me

[timwehrle]

@Jorropo Yeah, I tried that too and it worked, thanks for pointing out. Just weird that the https://pkg.go.dev/github.com/timwehrle/asana shows the old README and the versions don't match the actual versions either.

[Jorropo]

¿

[timwehrle]

@Jorropo Does that support my point or what are you trying to point out?

[Jorropo]

I want the package to be listed under github.com/timwehrle/asana instead of github.com/timwehrle/alfie.

asana is the old or new name ?

[timwehrle]

@Jorropo asana is the new name.

[Jorropo]

I see asana readme on https://pkg.go.dev/github.com/timwehrle/asana not old readme.

[timwehrle]

I think we are talking past each other. My point is that the readme is not updated when I change something in it.

[Jorropo]

It looks to me like you tagged v0.0.2 on asana https://github.com/timwehrle/asana/releases/tag/v0.0.2 but https://pkg.go.dev/github.com/timwehrle/asana@v0.0.2 was already indexed as https://pkg.go.dev/github.com/timwehrle/alfie so pkg.go.dev sends a redirect.

also pkg.go.dev has indexed v0.0.3 for asana

but this looks like it were removed from github https://github.com/timwehrle/asana/releases/tag/v0.0.3 ?

To me it seems your resolution path is to tag v0.0.4 on asana I don't think removing the alfie would help you since v0.0.3 is already indexed for asana.

[timwehrle]

Hmm, weird. I never published a v0.0.3. But I will publish a stable version the next days so then I will look if this resolves the issue. Thanks.

[seankhliao]

I see that it works now?
(fwiw 0.0.3-0.... is a pseudoversion for the commit that sorts (in semver) after 0.0.2 but before any 0.0.3 that you may publish).