Bug#826381: [uscan] exits non-zero if already on newest upstream version

2016-06-08 Thread James McCoy 
On Sun, Jun 05, 2016 at 08:39:27AM +0200, Daniel Baumann wrote:
> if a debian source package is already at the newest upstream version, uscan
> ends with exit code 1. Why? There's no error in that.

>From uscan(1):

  EXIT STATUS
 The exit status gives some indication of whether a newer
 version was found or not; one is advised to read the output to
 determine exactly what happened and whether there were any
 warnings to be noted.

 0   Either --help or --version was used, or for some watch file
 which was examined, a newer upstream version was located.

 1   No newer upstream versions were located for any of the
 watch files examined.

It's been like this for years.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#826381: [uscan] exits non-zero if already on newest upstream version

2016-06-05 Thread Daniel Baumann 

Package: devscripts
Version: 2.16.5

Hi,

if a debian source package is already at the newest upstream version, 
uscan ends with exit code 1. Why? There's no error in that.


I would expect that uscan exits with 0 if whatever is performed 
(including noop when local version = newest upstream version) doesn't 
lead to an error (e.g. when watch file or upstream site is broken).


Regards,
Daniel