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 with
Tristan Seligmann mithra...@mithrandi.net 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
On 4 February 2015 at 10:05, Ben Finney ben+deb...@benfinney.id.au wrote:
Tristan Seligmann mithra...@mithrandi.net 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:
On Feb 4, 2015, at 11:20 AM, Barry Warsaw ba...@debian.org 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
On 4 February 2015 at 06:08, Donald Stufft don...@stufft.io 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
On Feb 4, 2015, at 3:02 PM, Tianon Gravi admwig...@gmail.com wrote:
On 4 February 2015 at 06:08, Donald Stufft don...@stufft.io 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
On 4 February 2015 at 13:06, Donald Stufft don...@stufft.io 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
Hi Donald (2015.02.04_22:06:25_+0200)
On 4 February 2015 at 06:08, Donald Stufft don...@stufft.io 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).
On Feb 4, 2015, at 4:32 PM, Stefano Rivera stefa...@debian.org wrote:
Hi Donald (2015.02.04_22:06:25_+0200)
On 4 February 2015 at 06:08, Donald Stufft don...@stufft.io wrote:
If it gets implemented it'll live at /uscan/ because it exists primarily to
work around the deficiencies that exist
On Feb 4, 2015, at 10:07 AM, Barry Warsaw ba...@debian.org 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
On Feb 4, 2015, at 3:05 AM, Ben Finney ben+deb...@benfinney.id.au wrote:
Tristan Seligmann mithra...@mithrandi.net 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:
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
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| \
13 matches
Mail list logo
