Bug#822649: devscripts: uscan: Please add an option for not displaying output if upstream == debian and no errors occur

[James McCoy]

Control: tags 822649 - moreinfo

On Wed, May 04, 2016 at 05:25:40PM +0900, Osamu Aoki wrote:
> This bug report was odd ... version 2.16.2 NOW ??? We have 2.16.4 for
> all stable-bpo testing unstable.  Did you really run 2.16.2 ?

Regardless, the bug is still present in 2.16.4.

> On Mon, Apr 25, 2016 at 09:30:44PM -0400, James McCoy wrote:
> > On Mon, Apr 25, 2016 at 08:24:00PM -0400, Unit 193 wrote:
> 
> [2016-04-21] Accepted devscripts 2.16.3 (source) into unstable (James McCoy)
> 
> > > uscan has now started being much more verbose after 2.16 when checking for newer versions,
> > > this is nice I'm sure if you're only scanning a couple of packages, but if you have any number
> > > then it's hard to see the trees through the forest.
> > > 
> > > Please add an option less verbose than --no-verbose such that only errors or warnings appear if
> > > the local version of the package is the latest upstream too.
> > 
> > This shouldn't be an option.  It should be the default.  The behavior
> > should be comparable to how uscan behaved before 2.15.10.
> 
> Yes I agree that it should be the same as 2.15.9 and before.
> 
> [...]
> 
> So if something needs to be fixed even at 2.16.2, we need a bit more
> specifics where we now fail to match 2.15.9.

There shouldn't be any output from running “uscan” if the newest
available upstream version matches the version of the package and no
errors were encountered.

> Also, the title of this bug report is a bit cryptic.
>  output if upstream == debian and no errors
> 
> What exactly you mean?

What I stated above.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan at debian.org>