Perhaps the easiest way to fix it would be to delete the old documentation? That's not a problem as the actual package is not currently used.

It looks like you changed the tag on the new repo, which tends to confuse things.

Right now, the go.mod file in the new repo at v1.0.0 has a module path that matches the repo.

However, at some point the module path referred to the old repo, and that is the version that the proxy knows about:

> curl -L -o faces.zip https://proxy.golang.org/github.com/remyduthu/faces/@v/v1.0.0.zip
> unzip faces.zip
> cat github.com/remyduthu/faces@v1.0.0/go.mod
module github.com/remydt/faces
...

When pkgsite notices that the module path doesn't match the go.mod contents, it redirects you to the path in the go.mod file. That explains the gray banner "Redirected from github.com/remyduthu/faces" when you visit https://github.com/remyduthu/faces.

What you should have done is made a new tag when you changed the go.mod file. You can still do that: just tag master v1.0.1 and go get it, and soon pkgsite should show the right path.

Closing, but re-open if there are still problems after doing that.

Perhaps the easiest way to fix it would be to delete the old documentation? That's not a problem as the actual package is not currently used.

I could also remove the path github.com/remydt and all sub-paths from the site, but that wouldn't fix the problem I described above. I think we'd just redirect to a 404.

Would you like me to remove github.com/remydt?

Yes please, remove the old github.com/remydt repository. Thanks!

Done. https://pkg.go.dev/github.com/remyduthu/faces now returns a 404.