Bug#763071: devscripts: [uscan] allow setting download compression ordering (prefer xz over gz)

[James McCoy]

On Sat, Sep 27, 2014 at 06:50:06PM +0200, Andreas Metzler wrote:
> Given this watch file ...
> 
> -------------
> version=3
> opts=pgpsigurlmangle=s/$/.sig/ \
> ftp://ftp.gnu.org/gnu/autogen/rel([\d\.]+)/autogen-([\d\.]+)\.tar\.(?:xz|bz2|gz)
> -------------
> 
> ... uscan finds both .gz and .xz but selects the gzip version for
> download. Switching the two alternatives in the regex does not change
> this.

uscan debug: requesting URL ftp://ftp.gnu.org/gnu/autogen/rel5.18.4/
uscan debug: received content:
-rw-r--r--    1 3003     3002      1797980 Aug 30 17:55 autogen-5.18.4-5.src.rpm
-rw-r--r--    1 3003     3002          198 Aug 30 17:55 autogen-5.18.4-5.src.rpm.sig
-rw-r--r--    1 3003     3002       830780 Aug 30 17:55 autogen-5.18.4-5.x86_64.rpm
-rw-r--r--    1 3003     3002          198 Aug 30 17:55 autogen-5.18.4-5.x86_64.rpm.sig
-rw-r--r--    1 3003     3002      1794375 Aug 30 17:56 autogen-5.18.4.tar.gz
-rw-r--r--    1 3003     3002          198 Aug 30 17:56 autogen-5.18.4.tar.gz.sig
-rw-r--r--    1 3003     3002      1017936 Aug 30 17:56 autogen-5.18.4.tar.xz
-rw-r--r--    1 3003     3002          198 Aug 30 17:56 autogen-5.18.4.tar.xz.sig

The ordering actually comes from the ftp listing.  That being said, why
not just remove the bz2/gz parts of the regex if you know upstream is
shipping xz?  I don't see the benefit of matching the other extensions
(especially the bz2), when you know upstream already provides the
extension you want.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20140928/b4befed2/attachment.sig>