Skip to content
This repository was archived by the owner on May 30, 2020. It is now read-only.

(possible) removal of directory listing broke how Debian checks for new upstream release #228

Closed
ewdurbin opened this issue Jan 30, 2015 · 7 comments

Comments

@ewdurbin
Copy link
Member

Originally reported by: sandrotosi (Bitbucket: sandrotosi, GitHub: sandrotosi)


Hello,
It seems like PyPI disable its directory listing on URLs like https://pypi.python.org/packages/source/n/numpy/ (while previously you were able to look at the dir contents: http://web.archive.org/web/20091124123725/http://pypi.python.org/packages/source/n/numpy/ )

This was used by a huge amount of packages in Debian to check for new upstream releases. It is possible to re-enable it?

Regards,
Sandro


@ewdurbin
Copy link
Member Author

Original comment by Richard Jones (Bitbucket: r1chardj0n3s, GitHub: r1chardj0n3s):


That's unfortunate, and certainly wasn't ever anything we explicitly supported (there are other, supported mechanisms for checking for upstream releases). I'm not sure those listings are going to be made available in the future either, as we move away from a file system backend.

@dstufft might be able to comment here.

@ewdurbin
Copy link
Member Author

Original comment by Donald Stufft (Bitbucket: dstufft, GitHub: dstufft):


This went away as I prepared to move us away from storing the files on a local file system and instead move to an object store like S3 or Cloud Files. I'm planning to add it back temporarily while we're still on the local file system but it's going to go away in the future either way when we move to being backed by the object store because the API calls we need to make it work are expensive API calls. I believe that someone from #debian-python on OFTC is planning on adding a lintian check to warn people that their packages are using the unsupported URL instead of the supported one which would be https://pypi.python.org/simple/numpy/ in this case.

@ewdurbin
Copy link
Member Author

Original comment by sandrotosi (Bitbucket: sandrotosi, GitHub: sandrotosi):


Thanks a lot for the quick answer (and the explanation of what happened) :)

@ewdurbin
Copy link
Member Author

ewdurbin commented Feb 3, 2015

Original comment by Barry Warsaw (Bitbucket: warsaw, GitHub: warsaw):


This is still painful I think. We have tons of packages for which the debian/watch file will have to be fixed. Ok, I can kind of live with that, but the urls on https://pypi.python.org/simple/foo/foo-x.y.tar.gz all end with #md5=blah. I think that makes it rather difficult to come up with a simple pattern to find the download url. I'm trying to figure out the magic debian/watch incarnation to make this work. :(

@ewdurbin
Copy link
Member Author

ewdurbin commented Feb 3, 2015

Original comment by Barry Warsaw (Bitbucket: warsaw, GitHub: warsaw):


This describes how unfortunate the simple urls are:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776267#10

@ewdurbin
Copy link
Member Author

ewdurbin commented Feb 3, 2015

Original comment by sandrotosi (Bitbucket: sandrotosi, GitHub: sandrotosi):


this is a working debian/watch file using simple: http://anonscm.debian.org/viewvc/python-modules/packages/astroid/trunk/debian/watch?view=markup

@ewdurbin
Copy link
Member Author

ewdurbin commented Feb 4, 2015

Original comment by Barry Warsaw (Bitbucket: warsaw, GitHub: warsaw):


See also pypi/warehouse#358

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

No branches or pull requests

1 participant