Package: devscripts
Version: 2.16.13
Severity: wishlist
File: /usr/bin/bts
Perhaps check if the user has given extra arguments to version, and at
least return non-zero.
$ bts version 99 1.2.3; echo $?
bts version 2.16.13
Copyright (C) 2001-2003 by Joey Hess .
Modifications
Package: devscripts
Version: 2.16.8
Severity: minor
File: /usr/bin/bts
Looks scary:
$ bts -n subscribe 1 !
Use of uninitialized value $s in pattern match (m//) at /usr/bin/bts line 2562.
Use of uninitialized value $fromaddress in concatenation (.) or string at
/usr/bin/bts line 2576.
Use
Package: devscripts
Version: 2.16.1
Severity: wishlist
File: /usr/share/man/man1/debdiff.1.gz
Mention diffoscope, not debbindiff, as the latter has been renamed.
___
devscripts-devel mailing list
devscripts-devel@lists.alioth.debian.org
reassign 807810 bugs.debian.org
thanks
OK I'll reassign this bug, in the hope that on
https://www.debian.org/Bugs/server-control they will add some policy
statement about what to do when one wants to mark a bug forwarded to
more than one place, for whatever unexpected reason that might come up.
Well, think email CCs. Who would have thought only one allowed!
> "NB" == Nicholas Bamber writes:
NB> Actually the bts man page states the syntax:
NB> forwarded bug address
NB> It makes it faitly clear that only one upstream address is supported.
Package: devscripts
Version: 2.15.9
Severity: wishlist
File: /usr/share/man/man1/bts.1.gz
forwarded bug address
Mark the bug as forwarded to the given address (usually an email
address or a URL for an upstream bug tracker).
Mention what if one wants to mark the bug
Package: devscripts
Version: 2.14.10
Severity: wishlist
File: /usr/bin/checkbashisms
Could make output into a more parsible format by adding e.g.,
$ validate --help|grep -A1 emacs
--[no]emacs (don't) use an output format intended for parsing
by (X)Emacs,