-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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 go.dkinom.dev/baseconv/characters #61400
Comments
please try following the instructions at #60985 (comment) |
@seankhliao I did as advised in the comment. It's been over an hour. Module is not retracted from pkgsite yet. |
According to https://proxy.golang.org/cached-only/go.dkinom.dev/baseconv/characters/@latest, the most recent version of (Did you forget step 3 of the instructions in that comment? Perhaps you accidentally fetched the root module instead of the nested one?) |
Yes, I did step 3. It failed with the following error, even when
By the way, module |
That error message is correct: the
|
(So maybe give it another hour for that version to propagate to |
It should have updated by now. I'm escalating to the |
This turns out to be a bug in |
In the meantime you may be able to work around it by adding a tag for the nested module on the latest commit, like |
Thank you.
Let me try this. |
This worked. Now, https://pkg.go.dev/go.dkinom.dev/baseconv/characters is retracted. But, In the go.dkinom.dev/baseconv module's directories section on the pkgsite I still see reference to go.dkinom.dev/baseconv/characters module. Is this an expected behaviour? Can't the references/links to characters module be removed? |
I agree that the “Directories” entry seems inappropriate; I've filed #61554 for that. |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
What is the path of the package that you would like to have removed?
go.dkinom.dev/baseconv/characters
Are you the owner of this package?
Yes
What is the reason that you could not retract this package instead?
Removed the module from GitHub repo
The text was updated successfully, but these errors were encountered: