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

Can't delete badly-versioned release #55

Closed
osvenskan opened this issue Feb 23, 2019 · 8 comments
Closed

Can't delete badly-versioned release #55

osvenskan opened this issue Feb 23, 2019 · 8 comments
Assignees
Labels
support Users asking for help using PyPI

Comments

@osvenskan
Copy link

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 --

3.2.1

the version is this --

Sysv_ipc gives Python programs access to System V semaphores, shared memory 
and message queues. Most (all?) Unixes (including OS X) support System V IPC. 
Windows+Cygwin 1.7 might also work. 

Sample code is included.

This extension is released under the GPL. 

You might also be interested in the similar POSIX IPC module at:
http://semanchuk.com/philip/posix_ipc/

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

  1. Go to https://pypi.org/manage/project/sysv-ipc/releases/#modal-close
  2. Try to delete the release with the ridiculous version string
@yeraydiazdiaz
Copy link

yeraydiazdiaz commented Feb 23, 2019

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.

@osvenskan
Copy link
Author

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.

@dstufft
Copy link
Member

dstufft commented Feb 23, 2019 via email

@ewdurbin
Copy link
Member

ewdurbin commented Jun 25, 2019

Notes:

Release ID is dbea92f6-a9e5-4840-95f5-4534cf6dadea
Version is:

        | Sysv_ipc gives Python programs access to System V semaphores, shared memory   +
        | and message queues. Most (all?) Unixes (including OS X) support System V IPC. +
        | Windows+Cygwin 1.7 might also work.                                           +
        |                                                                               +
        | Sample code is included.                                                      +
        |                                                                               +
        | This extension is released under the GPL.                                     +
        |                                                                               +
        | You might also be interested in the similar POSIX IPC module at:              +
        | http://semanchuk.com/philip/posix_ipc/

@di
Copy link
Member

di commented Oct 25, 2019

Assigning @ewdurbin to do some database magic here.

@di di transferred this issue from pypi/warehouse Oct 25, 2019
@di di added the support Users asking for help using PyPI label Oct 25, 2019
@osvenskan
Copy link
Author

If I can help (other than "don't do this again!"), please LMK.

@ewdurbin
Copy link
Member

completed.

@osvenskan
Copy link
Author

Thank you so much @ewdurbin!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Users asking for help using PyPI
Projects
None yet
Development

No branches or pull requests

5 participants