Hi,
On Thu, Mar 17, 2016 at 09:37:57AM +0100, Raphael Hertzog wrote:
> Hi,
>
> On Wed, 16 Mar 2016, Nikolaus Rath wrote:
> > For at least some packages, there's a consistent false positive when
> > running uscan (e.g. https://tracker.debian.org/pkg/s3ql):
> >
> > | uscan had problems while searching for a new upstream version:
> > | No upstream tarball downloaded. No further processing with mk_origtargz
> >
> > As far as I can tell, uscan didn't actually have any problems here.
>
> We get the data from UDD which gets it from uscan itself via "uscan
> --dehs".
>
> uscan had major changes recently... see https://bugs.debian.org/815980
> for some of the recent issues.
>
> This warning can be useful when you use uscan interactively but it really
> should not be displayed with --dehs. Yes we don't want to download
> anything, it's normal...
all --dehs output goes to STDOUT
all other output including verbose output goes to STDERR if --dehs is
used.
So use 2>/dev/null. Having verbose output available for -dehs is really
good for debug etc. In script, invoke uscan with 2>/dev/null
I have already killed almost all verbose output in VCS. So default
output is readuced much more for VCS
stable-bpo 2.16.1~bpo8+1
testing 2.16.1
These did not address all the regressions caused by the major changes
happened at 2.15.10
> Osamu, can fix this too?
PENDING FIXES are
[ Osamu Aoki ]
* uscan:
+ Print proper warnings for bad rules. Closes: #814049
+ Fix glitches around rules such as "s<...> <...>g" and add their
tests.
+ Reactivate --no-verbose mode. Closes: #815645
+ Fix --destdir for version 4. Closes:#814686
+ Always use uscan_warn and uscan_die.
+ Die if the action script fails. Closes: #810976
For --dehs, "Always use uscan_warn and uscan_die" is important.
I guess we need to wait for James McCoy to upload new version.
As for the current VCS code:
$ uscan --dehs --report 2>/dev/null
<dehs>
<package>s3ql</package>
<debian-uversion>2.15+dfsg</debian-uversion>
<debian-mangled-uversion>2.15+dfsg</debian-mangled-uversion>
<upstream-version>2.17.1+dfsg</upstream-version>
<upstream-url>https://bitbucket.org/nikratio/s3ql/downloads/s3ql-2.17.1.tar.bz2</upstream-url>
<status>newer package available</status>
<messages>Not downloading upstream package: s3ql-2.17.1.tar.bz2
</messages>
</dehs>
Status report good.
No warnings to indicate there were no scanning errors.
So I see no problerm.
Osamu
