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

[Osamu Aoki]

control: tags 822649 moreinfo 

Hi,

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 ?

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.

There have been fixes for the type of problems in 2.16.1 and 2.16.2.

In 2.16.1:
 Fix regressions of the verbosety. (Closes: #809541, #809554)

In 2.16.2:
 Reactivate --no-verbose mode.  Closes: #815645
 Always use uscan_warn and uscan_die.
 Die if the action script fails.  Closes: #810976

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.

Also, there have been several important bug fixes in 2.16.3 and 2.16.4.

Please point out where you see problem in 2.16.4.

Also, the title of this bug report is a bit cryptic.
 output if upstream == debian and no errors

What exactly you mean?

Regards,

Osamu