-
Notifications
You must be signed in to change notification settings - Fork 47
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
Can't delete badly-versioned release #55
Comments
Hello @osvenskan, I've tried deleting this release myself but the admin UI also has trouble showing the release as it also uses the release name and the escaping confuses it badly. Maybe @ewdurbin can access the database and remove it there? As far as a bug I'd say there should be some checks around what constitutes a valid release version on twine first (assuming that's what you used to upload the release). The Warehouse user and admin UI should then make changes according to these if necessary. |
Thanks @yeraydiazdiaz for looking into it!
It was 10 years ago, I don't remember what I used to upload it. One way to fix this that might not be too hard (famous last words) would be to disallow (on the PyPI side) newlines in versions, or map all whitespace (newline, tab, NBSP, etc.) to ASCII 0x20. |
PyPI rejects non PEP-440 versions now, so a version like this isn’t possible anymore. We just didn’t remove existing versions that weren’t PEP440 compliant.
…Sent from my iPhone
On Feb 23, 2019, at 3:02 PM, Philip Semanchuk ***@***.***> wrote:
Thanks @yeraydiazdiaz for looking into it!
As far as a bug I'd say there should be some checks around what constitutes a valid release version on twine first (assuming that's what you used to upload the release).
It was 10 years ago, I don't remember what I used to upload it. :-) But it predates twine.
One way to fix this that might not be too hard (famous last words) would be to disallow (on the PyPI side) newlines in versions, or map all whitespace (newline, tab, NBSP, etc.) to ASCII 0x20.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Notes: Release ID is dbea92f6-a9e5-4840-95f5-4534cf6dadea
|
Assigning @ewdurbin to do some database magic here. |
If I can help (other than "don't do this again!"), please LMK. |
completed. |
Thank you so much @ewdurbin! |
Describe the bug
I'm the author & maintainer of sysv_ipc. Ten years ago I accidentally uploaded a release that contained the description in the version field, so instead of a standard version string like this --
the version is this --
Apparently this mess I created causes problems for some automated tools and I would like to delete this one release. (The
sysv_ipc
package as a whole is fine, I just want to delete this one release.) However, deleting the release requires me to enter the version for confirmation, and I can't seem to enter the multi-line version into the single-line text field, even via copy&paste.Expected behavior
To be able to delete this release
To Reproduce
The text was updated successfully, but these errors were encountered: