Skip to content

Cannot Update My Packages #2342

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

Closed
Miserlou opened this issue Aug 28, 2017 · 4 comments
Closed

Cannot Update My Packages #2342

Miserlou opened this issue Aug 28, 2017 · 4 comments

Comments

@Miserlou
Copy link

I've logged into the new system to try to update one of my packages. It shows that I am logged in and that these are my packages, but there is no menu or interface to administer them. What's happening here?

@Miserlou
Copy link
Author

Even worse, while updating through the legacy site I get a I/O error (send request) error, and from setup.py, I get error: Upload failed (410): Gone (This API has been deprecated and removed from legacy PyPI in favor of using the APIs available in the new PyPI.org implementation of PyPI (located at https://pypi.org/). For more information about migrating your use of this API to PyPI.org, please see https://packaging.python.org/guides/migrating-to-pypi-org/#uploading. For more information about the sunsetting of this API, please see https://mail.python.org/pipermail/distutils-sig/2017-June/030766.html)

This is a small nightmare.

@Miserlou
Copy link
Author

Can anybody explain to me what's happening with these issues? I need to update a package that a lot of people depend on and right now I can't.

@di
Copy link
Member

di commented Aug 29, 2017

I've logged into the new system to try to update one of my packages. It shows that I am logged in and that these are my packages, but there is no menu or interface to administer them. What's happening here?

The index at https://pypi.org/ is a pre-production deployment of Warehouse. Work on making Warehouse have feature-parity with the legacy index is currently in progress, and thus it is essentially view-only, so any "administrative" edits still need to be done through the legacy index here: https://pypi.python.org/

EDIT: This does not include editing a description -- pypi-legacy does not and will not support this anymore. Please see #2170, specifically this comment.

Even worse, while updating through the legacy site I get a I/O error (send request) error

I'm assuming here you mean the index at https://pypi.python.org/. I'm not as familiar with the legacy code base and I don't know what this error means. The right place to report a specific issue with it is here: https://github.com/pypa/pypi-legacy

and from setup.py, I get error: Upload failed (410): Gone

I'm not exactly sure what command you ran to produce this, but I'm guessing it was python setup.py upload. You should take a look at the links the error messages provide, which describe that uploading to the legacy API (powered by pypi-legacy) has been sunsetted, and you should migrate to using the new API (powered by warehouse):

@dstufft
Copy link
Member

dstufft commented Sep 17, 2017

I'm going to close this issue as it seems to simply be a case of confusion, and there doesn't seem to be anything more actionable on it beyond what @di has already mentioned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants