Re: PyPI and debian/watch

2015-02-04 Thread Donald Stufft
> On Feb 4, 2015, at 4:32 PM, Stefano Rivera wrote: > > Hi Donald (2015.02.04_22:06:25_+0200) >>> On 4 February 2015 at 06:08, Donald Stufft wrote: If it gets implemented it'll live at /uscan/ because it exists primarily to work around the deficiencies that exist in uscan (Particularl

Re: PyPI and debian/watch

2015-02-04 Thread Stefano Rivera
Hi Donald (2015.02.04_22:06:25_+0200) > > On 4 February 2015 at 06:08, Donald Stufft wrote: > >> If it gets implemented it'll live at /uscan/ because it exists primarily to > >> work around the deficiencies that exist in uscan (Particularly the > >> dificulty > >> in ignoring url fragments). Wou

Re: PyPI and debian/watch

2015-02-04 Thread Tianon Gravi
On 4 February 2015 at 13:06, Donald Stufft wrote: > We talked about this in #debian-python and there was concern that a new > version > of uscan wouldn’t be in Jessie and then wouldn’t cover the people who need it > the most. Ah right, that makes sense -- I forgot that we were talking about this

Re: PyPI and debian/watch

2015-02-04 Thread Donald Stufft
> On Feb 4, 2015, at 3:02 PM, Tianon Gravi wrote: > > On 4 February 2015 at 06:08, Donald Stufft wrote: >> If it gets implemented it'll live at /uscan/ because it exists primarily to >> work around the deficiencies that exist in uscan (Particularly the dificulty >> in ignoring url fragments). >

Re: PyPI and debian/watch

2015-02-04 Thread Tianon Gravi
On 4 February 2015 at 06:08, Donald Stufft wrote: > If it gets implemented it'll live at /uscan/ because it exists primarily to > work around the deficiencies that exist in uscan (Particularly the dificulty > in ignoring url fragments). This seems like we're building a workaround to a tool we cou

Re: PyPI and debian/watch

2015-02-04 Thread Donald Stufft
> On Feb 4, 2015, at 11:20 AM, Barry Warsaw wrote: > > On Feb 04, 2015, at 10:53 AM, Donald Stufft wrote: > >> That same page also mentions that qa.debian.org runs a number of >> "redirectors" for sites like SourceForge and GitHub so perhaps a better >> answer is for Debian QA to run a redirect

Re: PyPI and debian/watch

2015-02-04 Thread Barry Warsaw
On Feb 04, 2015, at 10:53 AM, Donald Stufft wrote: >That same page also mentions that qa.debian.org runs a number of >"redirectors" for sites like SourceForge and GitHub so perhaps a better >answer is for Debian QA to run a redirector for PyPI instead of PyPI >implementing a redundant API endpoint

Re: PyPI and debian/watch

2015-02-04 Thread Donald Stufft
> On Feb 4, 2015, at 10:07 AM, Barry Warsaw wrote: > > On Feb 04, 2015, at 08:08 AM, Donald Stufft wrote: > >> If it gets implemented it'll live at /uscan/ because it exists primarily to >> work around the deficiencies that exist in uscan (Particularly the dificulty >> in ignoring url fragments

Re: PyPI and debian/watch

2015-02-04 Thread Barry Warsaw
On Feb 04, 2015, at 08:08 AM, Donald Stufft wrote: >If it gets implemented it'll live at /uscan/ because it exists primarily to >work around the deficiencies that exist in uscan (Particularly the dificulty >in ignoring url fragments). Everyone else should just use the URLs at /simple/ >which most

Re: PyPI and debian/watch

2015-02-04 Thread Donald Stufft
> On Feb 4, 2015, at 3:05 AM, Ben Finney wrote: > > Tristan Seligmann writes: > >> The debian/watch file I wrote for python-nacl (which also verifies the >> PGP signature) seems to work. > > I can't get PGP signature retrieval to rowk (“uscan warning: > pgpsigurlmangle option exists, but the

Re: PyPI and debian/watch

2015-02-04 Thread Tristan Seligmann
On 4 February 2015 at 10:05, Ben Finney wrote: > Tristan Seligmann writes: > >> The debian/watch file I wrote for python-nacl (which also verifies the >> PGP signature) seems to work. > > I can't get PGP signature retrieval to rowk (“uscan warning: > pgpsigurlmangle option exists, but the upstrea

Re: PyPI and debian/watch

2015-02-04 Thread Ben Finney
Tristan Seligmann writes: > The debian/watch file I wrote for python-nacl (which also verifies the > PGP signature) seems to work. I can't get PGP signature retrieval to rowk (“uscan warning: pgpsigurlmangle option exists, but the upstream keyring does not exist”) even with your suggested patter

Re: PyPI and debian/watch

2015-02-03 Thread Barry Warsaw
On Feb 04, 2015, at 01:09 AM, Tristan Seligmann wrote: >The debian/watch file I wrote for python-nacl (which also verifies the >PGP signature) seems to work. It looks like this: > >version=3 >opts="pgpsigurlmangle=s/\#md5.*$/.asc/,filenamemangle=s|.*/(.*)\#md5.*$|$1|" \ > https://pypi.python.org/s

Re: PyPI and debian/watch

2015-02-03 Thread Tristan Seligmann
On 4 February 2015 at 00:40, Barry Warsaw wrote: > Unfortunately, I've not been able to get either the one described here: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776267#10 > > or another one that came up in #debian-python to work. The debian/watch file I wrote for python-nacl (whic

Re: PyPI and debian/watch

2015-02-03 Thread Barry Warsaw
On Jan 31, 2015, at 06:04 PM, Dmitry Shachnev wrote: >We already have a patch for Lintian to detect such watch files: >https://bugs.debian.org/776267 It's worse than that. All the urls in the pypi /simple indexes have #md5=blah suffixes on the urls, so a filenamemangle opt will be required in d/

Re: PyPI and debian/watch

2015-01-31 Thread Dmitry Shachnev
Hi, On Sat, 31 Jan 2015 14:16:58 +, Sandro Tosi wrote: > https://bitbucket.org/pypa/pypi/issue/228/possible-removal-of-directory-listing We already have a patch for Lintian to detect such watch files: https://bugs.debian.org/776267 -- Dmitry Shachnev signature.asc Description: OpenPGP digit