Control: clone 711744 -1 Control: reassign -1 devscripts Control: retitle -1 uscan should propagate the pasv option to PGP signature URL
On Tue 2014-01-07 04:48:58 -0500, Thijs Kinkhorst wrote: > When I [use pasv], the downloading of the orig.tar.gz works [...], but > the downloading of the signature fails. Does that code not use the > pasv option? > > $ uscan --verbose > -- Scanning for watchfiles in . > -- Found watchfile in ./debian > -- In debian/watch, processing watchfile line: > opts="pasv,pgpsigurlmangle=s/$/.sig/" > http://gnupg.org/download/.*/gnupg-(1\..*)\.tar\.gz > -- Found the following matching hrefs: > ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.16.tar.gz (1.4.16) > Newest version on remote site is 1.4.16, local version is 1.4.15 > => Newer version available from > ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.16.tar.gz > -- Downloading updated package gnupg-1.4.16.tar.gz > -- Downloading OpenPGP signature for package as gnupg-1.4.16.tar.gz.pgp > uscan warning: In directory ., downloading OpenPGP signature > ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.16.tar.gz failed: 400 FTP > return code 150 You are right, the pgpsigurlmangle code does not currently support the pasv option. It should do so to handle situations like gnupg's, above. --dkg
pgpgPAC5RvuTj.pgp
Description: PGP signature
