Control: retitle -1 devscripts: uscan: support --download-version in git mode Control: severity -1 wishlist
On Sat, Jul 25, 2020 at 11:30:03PM +0200, Jérémy Lal wrote: > debian/changelog: > node-formidable (1.2.1+git20200129.8231ea6-1) unstable; urgency=medium > > debian/watch: > version=4 > opts="mode=git, pgpmode=none, gitmode=full, pretty=1.2.1+git%cd.%h" \ > https://github.com/node-formidable/formidable \ > HEAD debian uupdate > > uscan --download-version 1.2.1+git20200129.8231ea6 > uscan: Newest version of node-formidable on remote site is > 1.2.1+git20200529.5110ef8, specified download version is > 1.2.1+git20200129.8231ea6 > Leaving ../node-formidable_1.2.1+git20200529.5110ef8.orig.tar.xz where it is. > uupdate: ../node-formidable-1.2.1+git20200529.5110ef8 directory exists. > uupdate: remove ../node-formidable-1.2.1+git20200529.5110ef8 directory. > uupdate: -> Copy to > node-formidable_1.2.1+git20200529.5110ef8-1.debian.tar.xz > > What was expected ? > building tarball of specified version. Yes, it's expected. The manpage mentions that it's a "best effort feature", and due to the way the git thing works it's kinda of more tricky than with plain tarballs. Let's turn this into a wishlist bug. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
