Your message dated Thu, 17 Jun 2010 00:36:03 +0200
with message-id <aanlktinqcbyg3dvw1cpl3honuiwadm4j7_tvdrd7z...@mail.gmail.com>
and subject line Re: Bug#586159: reportbug: Show reassigned bugs and shift
report to new package if applicable
has caused the Debian Bug report #586159,
regarding reportbug: Show reassigned bugs and shift report to new package if
applicable
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 ow...@bugs.debian.org
immediately.)
--
586159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 4.10.2
Severity: wishlist
Hello there
When a bug report is moved to a different package, e.g. the actual root of the
problem was a dependency, it is no longer shown in the bugs list of the first
one. That is a problem, since that is the most probable point of entry for new
reports regarding the same bug. Since people will not see the bug, they will
create a new one for the same issue.
So, packages moved to different packages than the original should be shown.
Going further, if a field containing the packages and versions affected by a
bug is ever implemented in the bug tracking server, it would show bugs which
apply or affect the package/version the user has in the system.
For example, it'd be great if people reporting a bug in apt-listbugs could see
bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585448
as it directly affects that package, eventhough it is listed in libdpkg-ruby1.8.
I hope you find my proposal interesting,
Elideb
-- Package-specific info:
** Environment settings:
INTERFACE="gtk2"
** /home/elideb/.reportbugrc:
reportbug_version "4.8"
mode advanced
ui gtk2
email "trasuntopendie...@hotmail.com"
no-cc
header "X-Debbugs-CC: trasuntopendie...@hotmail.com"
smtphost reportbug.debian.org
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages reportbug depends on:
ii apt 0.7.25.3 Advanced front-end for dpkg
ii python 2.5.4-9 An interactive high-level object-o
ii python-reportbug 4.10.2 Python modules for interacting wit
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn debconf-utils <none> (no description available)
pn debsums <none> (no description available)
pn dlocate <none> (no description available)
pn emacs22-bin-common | <none> (no description available)
ii file 5.04-1 Determines file type using "magic"
ii gnupg 1.4.10-2 GNU privacy guard - a free PGP rep
ii python-gtk2 2.16.0-2 Python bindings for the GTK+ widge
ii python-gtkspell 2.25.3-4.1+b3 Python bindings for the GtkSpell l
pn python-urwid <none> (no description available)
ii python-vte 1:0.22.5-2 Python bindings for the VTE widget
ii ssmtp [mail-transpor 2.64-3 extremely simple MTA to get mail o
ii xdg-utils 1.0.2+cvs20100223-1 desktop integration utilities from
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello Elora,
On Thu, Jun 17, 2010 at 00:30, Elora HRanma
<trasuntopendie...@hotmail.com> wrote:
> Package: reportbug
> Version: 4.10.2
> Severity: wishlist
>
> Hello there
>
> When a bug report is moved to a different package, e.g. the actual root of
> the problem was a dependency, it is no longer shown in the bugs list of the
> first one. That is a problem, since that is the most probable point of entry
> for new reports regarding the same bug. Since people will not see the bug,
> they will create a new one for the same issue.
> So, packages moved to different packages than the original should be shown.
> Going further, if a field containing the packages and versions affected by a
> bug is ever implemented in the bug tracking server, it would show bugs which
> apply or affect the package/version the user has in the system.
> For example, it'd be great if people reporting a bug in apt-listbugs could
> see bug
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585448
> as it directly affects that package, eventhough it is listed in
> libdpkg-ruby1.8.
Please bring your idea to the BTS owner, that will decide if it's
worth implementing it or not. Reportbut is a mare interface to the
information exposed by BTS. That said, I'm closing this report.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
_______________________________________________
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
