Package: devscripts
Version: 2.9.5
Severity: normal

Hi,

for me, the fix for #313323 has made uscan worse. I run uscan in a
cron job to remind me when my upstreams have released new package
versions. Since --report now _always_ creates output, even if packages
are up to date, a mail is generated every time uscan is invoked.

Unfortunately, --no-verbose doesn't seem to be honored:

[20/[EMAIL PROTECTED]:~/devel/debian/svn$ uscan --no-verbose --report
Newest version on remote site is 4.52, local version is 4.52
 => Package is up to date
Newest version on remote site is 4.50, local version is 4.50
 => Package is up to date
Newest version on remote site is 2.2.3, local version is 2.2.3
 => Package is up to date
Newest version on remote site is 2.2, local version is 2.2
 => Package is up to date
Newest version on remote site is 2.0.1, local version is 2.0.1
 => Package is up to date
Newest version on remote site is 1.4.14, local version is 1.4.14
 => Package is up to date
[21/[EMAIL PROTECTED]:~/devel/debian/svn$

Pretty please give a possibility to have uscan be silent if there is
nothing to report.

Greetings
Marc


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.2-zgsrv
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)

Versions of packages devscripts depends on:
ii  debianutils                   2.14.2     Miscellaneous utilities specific t
ii  dpkg-dev                      1.13.11    package building tools for Debian
ii  libc6                         2.3.5-4    GNU C Library: Shared libraries an
ii  perl                          5.8.7-4    Larry Wall's Practical Extraction 
ii  sed                           4.1.4-2    The GNU sed stream editor

Versions of packages devscripts recommends:
ii  fakeroot                      1.4.3      Gives a fake root environment

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to