Bug#814049: /usr/bin/uscan: uscan gives invalid example in manpage for github tags

Osamu Aoki osamu at debian.org
Mon Feb 8 13:14:42 UTC 2016


control: retitle -1 improve warning for safe_replace 

Hi,

This report discuss several things.

On Sun, Feb 07, 2016 at 11:03:06PM +0000, Ximin Luo wrote:
> Ximin Luo:
> > In uscan's manpage, it gives this example for github tags:
> > 
> >          version=4
> >          opts="filenamemangle="s%(?:.*?)?v?(\d[\d.]*)\.tar\.gz%<project>-$1.tar.gz%" \
> >              https://github.com/<user>/<project>/tags \
> >              (?:.*?/)?v?(\d[\d.]*)\.tar\.gz debian uupdate

This is fixed in CVS. Thanks.
 
> However, the error message is still pretty vague. What does "unsafe"
> mean? Could you at least make two different error messages for the
> "unsafe" vs "malformed" cases?

This is a valid point but not so easy to fix.

Maybe I should add warining messages to safe_replace and
quoted_regex_parse functions.

> Also I am getting this as further output:
> 
> ~~~~
> uscan: Don't downloading upstream package: baka-mplayer-2.0.4.tar.gz
> uscan: Start checking for common possible upstream OpenPGP signature files
> uscan: End checking for common possible upstream OpenPGP signature files
> uscan: Successfully downloaded package baka-mplayer-2.0.4.tar.gz
> uscan warn: No upstream tarball downloaded.  No further processing with mk_origtargz ...

Now the VCS version does not print out as much.  But this is problem I
see.  Now verbose output is fixed in VCS.

Now that 2 trivial bugs are fixed, let me retitle this bug as this.  So
I will work on this later.

Osamu



More information about the devscripts-devel mailing list