Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/pkgsite: package removal request for cloud.2linfo.fr/gitea/2linfo/golibarr #59263

Closed
dragonis41 opened this issue Mar 27, 2023 · 5 comments
Closed
Labels
FrozenDueToAge pkgsite/package-removal Issues for package removal. See https://pkg.go.dev/about#removing-a-package pkgsite WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone

Comments

@dragonis41
Copy link

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

https://cloud.2linfo.fr/gitea/2linfo/golibarr

Are you the owner of this package?

Yes I am.

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

  • This package does not exist anymore and I didn't know it was cached on pkg.go.dev.
  • This package is no longer maintained and contains multiples sever bugs.
  • We plan to create a new one from scratch on GitHub, so the URL will also change.
@gopherbot gopherbot added this to the Unreleased milestone Mar 27, 2023
@adonovan
Copy link
Member

Hi, this seems like a duplicate of #57260, which timed out due to lack of information. Can you provide evidence that you are the owner of the package? (e.g. by temporarily recreating the package with a message that references this issue?) Thanks.

@seankhliao seankhliao added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Mar 30, 2023
@dragonis41
Copy link
Author

Hello, yes this is my boss at 2LINFO.
Unfortunately, we can't put it online due to the fact that this is a private package intern to Adrien's company.
If you still have access to the git repository (cached on pkg.go.dev for example), you can see that almost all commits are signed with my GPG key C7D19B2BA2890526 (the subkeys are 4137B6C1D91817FC and 4FF8DF9CBCECFE97).
This package has been added to pkg.go.dev because during a software release, we temporarily open this repository to the public to debug an issue that we encored with doing a go get on our production server. At the time we didn't know that this repository will be cached on pkg.go.dev and as Adrien says in the issue #57260 the repo does not mean to be public.
Whatever happens, the link to the repo will always lead to a 404 error because it won't be publicly available and we won't open our Git server to the internet for confidentiality reason.
Thanks

@adonovan
Copy link
Member

Though I can confirm that https://api.github.com/users/dragonis41/gpg_keys contains those GPG keys, unfortunately (or perhaps fortunately) I don't have access to the git history of the delete repo. (The Go module proxy stores only versioned .zip files.)

But in this case I will assume good faith and activate the process to block this module in pkgsite.

@dragonis41
Copy link
Author

Thank you Alan, I appreciate !

We will do everything we can to ensure that this does not happen again in the future.

@findleyr
Copy link
Member

findleyr commented Apr 6, 2023

Looks like this is done, as https://pkg.go.dev/cloud.2linfo.fr/gitea/2linfo/golibarr is serving a 404.

Marking as closed. Please let me know if I missed something.

@findleyr findleyr closed this as completed Apr 6, 2023
@findleyr findleyr added the pkgsite/package-removal Issues for package removal. See https://pkg.go.dev/about#removing-a-package label Apr 13, 2023
@golang golang locked and limited conversation to collaborators Apr 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge pkgsite/package-removal Issues for package removal. See https://pkg.go.dev/about#removing-a-package pkgsite WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Development

No branches or pull requests

5 participants