Your message dated Fri, 8 Jan 2010 00:11:08 +0100
with message-id <[email protected]>
and subject line Re: Bug#564090: reportbug: Allow to recurse dependencies when
listing them
has caused the Debian Bug report #564090,
regarding reportbug: Allow to recurse dependencies when listing them
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
564090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564090
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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,
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/.
Cheers,
Mike
-- Package-specific info:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages reportbug depends on:
ii apt 0.7.25 Advanced front-end for dpkg
ii python 2.5.4-5 An interactive high-level object-o
ii python-reportbug 4.9 Python modules for interacting wit
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn debconf-utils <none> (no description available)
ii debsums 2.0.48 tool for verification of installed
pn dlocate <none> (no description available)
ii exim4 4.71-3 metapackage to ease Exim MTA (v4)
ii exim4-daemon-light [mail-tran 4.71-3 lightweight Exim MTA (v4) daemon
ii file 5.03-5 Determines file type using "magic"
ii gnupg 1.4.10-2 GNU privacy guard - a free PGP rep
ii python-gtk2 2.16.0-1 Python bindings for the GTK+ widge
pn python-gtkspell <none> (no description available)
pn python-urwid <none> (no description available)
ii python-vte 1:0.22.5-1 Python bindings for the VTE widget
pn xdg-utils <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Jan 08, 2010 at 12:02:48AM +0100, Sandro Tosi wrote:
> 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 :)
Sounds good enough for me. Thanks for the hint.
Mike
PS: If you could take a look at #548415 ;)
--- End Message ---
_______________________________________________
Reportbug-maint mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
