Bug#809554: uscan: verbose is always enabled

[Osamu Aoki]

Hi
n Thu, Dec 31, 2015 at 03:08:23PM -0800, Vincent Cheng wrote:
> Please consider providing an option to suppress uscan output, specifically to
> emulate the behaviour of "uscan --report" in previous versions of devscripts
> (<= 2.15.9), where only errors or new upstream releases get printed out to
> console.

On Fri, Jan 01, 2016 at 10:27:58AM +0100, Christian Marillat wrote:
> Even if USCAN_VERBOSE=no is set in ~/.devscripts uscan is always verbose :

I thought this was not "verbose" compared to what new "verbose" and
"debug" does.  But considering these immediate responses, I may
reconsider to readjust verbosity.

If s/uscan_msg/uscan_verbose/ is applied, these messages become verbose
only.  There are many more uscan_msg which reported example did not hit
but may be concern to you from "emulate the old behaviour" POV.

> uscan: uscan (version 2.15.10) See uscan(1) for help
> uscan: Scan watch files in .
> uscan: ./ffmpeg-2.8.4/debian/changelog sets package="ffmpeg-dmo" version="2.8.4"

I guess you do not want above 3 lines

> uscan: Newest version on remote site is 2.8.4, local version is 2.8.4
> uscan:    => Package is up to date

I guess you want above 2 lines

> uscan: Don't downloading upstream package: ffmpeg-2.8.4.tar.gz
> uscan: Successfully downloaded package ffmpeg-2.8.4.tar.gz
> uscan: SKIP generation of orig.tar.* and running of script/uupdate (--safe)

I guess you do not want above 3 lines
(Also "Successfully downloaded ..." should be more like "Successfully
found ...")

I am thinking to move
 old uscan_msg to uscan_msg
 new uscan_msg to uscan_verbose
 keep uscan_verbose
 keep uscan_debug

What do you all think?

Osamu
PS: Excuse me, I will be practically on vacation for 3 weeks.