Hi, On Sat, Oct 03, 2015 at 05:12:02PM +0000, Mattia Rizzolo wrote: > On Sun, Oct 04, 2015 at 01:20:17AM +0900, Osamu Aoki wrote: ... > Anyway, I'm not sure about what you're talking here. I've yet to read > the rewritten manpage, and even if I "stalk" you I'm somewhat lost in > your work.
Since it is in POD, I made html and posted: https://people.debian.org/~osamu/uscan.html You can build it as: $ git clone https://anonscm.debian.org/git/collab-maint/devscripts.git $ git checkout multitar $ debuild > Assured that this use case is now addressed too, I'll patiently wait for > the new uscan to reach unstable to test, and jessie-bpo to apply to the > affected package (so that qa.d.o stuff won't explode...) I am curious how uscan is used in qa.d.o. uscan's output messages has lots of legacy complication which makes confusing --verbose and --dehs mutual exclusion etc. Also --no-download /--report is now also --no-sigdownload and --no-sigcheck (neither option are implemented yet). So far I see usage as: * git-buildpackage: uses --dehs and only use stdout this needs to be updated for multiple upstream tarball (No way to track component) uscan log may be better way to pass list of packages * svn-buildpackage: uses --report and use stdout+stderr with tee_merged * dehs on web: uses --dehs and "2>/dev/null 2>&1" with shell_exec https://wiki.debian.org/DEHS -> http://anonscm.debian.org/viewvc/dehs/trunk/ Basically, I want to make --dehs compatible with --verbose. If --dehs is used, --verbose output should go to stderr. DEHS may be problematic. Osamu _______________________________________________ devscripts-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/devscripts-devel
