Hi Mike, thanks for your bug report. On Thu, Jan 7, 2010 at 17:41, Mike Hommey <[email protected]> wrote: > Package: reportbug > Version: 4.9 > Severity: wishlist > > In the package-specific info, there dependencies, recommends and suggests > are listed. This is precious information for maintainers. But sometimes, > the package the bug is reported upon isn't the one that has most useful > dependency information. You may have guessed here, I'm mostly talking about > iceweasel, but I'm pretty sure we could find some other package where this > could be useful. > > While I'm not requesting that *all* dependencies be recursively listed,
even because, on a general view, it would increase the bug length to a point the maintainer has difficulty to find the information he needss. > I'd like, as a maintainer, to tell reportbug, "hey, whenever you report a > bug for iceweasel, give me the information for xulrunner-1.9.1 at the same > time". The package list for which the maintainer of $package requests such > additional information could be put in a file in /usr/share/bug/$package/. "reportbug --template <pkg>" prints the bug template that would be used if reporting the bug for real: would it be possible for you to use it in a bug script, with the support of sed/awk/grep/whatever to extract the information you need? they will be included into the bug report, only for the package you decide, with teh advantage of not increasing reportbug complexity :) Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
