Your message dated Thu, 1 Apr 2010 00:35:17 +0200
with message-id <[email protected]>
and subject line Re: Bug#575920: reportbug: ask for the version of the package
to be reported as buggy
has caused the Debian Bug report #575920,
regarding reportbug: ask for the version of the package to be reported as buggy
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.)
--
575920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575920
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 4.10.2
Severity: wishlist
Yesterday I managed to fix a problem with nvidia-glx package.
I installed the version from the unstable repository. The I filed a
bug report about, as I was hoping, the older buggy version. Because
reportbug generates a template with a fat sing "Please type etc." and
I am not too interested in details of Debian bug reporting process
I don't even look above that line. I should have. The bug was filed
against the unstable version which wasn't my intention nad got closed
immediatelly.
I wish report bug explicitly asked a question
"File the report against version X.Y.Z [Y|n]:"
In most cases users hit [Enter]. It'd be closer to other bug tracking
systems wher users choose on their own the version to be reported
as buggy.
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /home/steelman/.reportbugrc:
reportbug_version "3.39"
mode standard
ui text
realname "Łukasz Stelmach"
email "[email protected]"
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
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)
ii emacs23-bin-common 23.1+1-5 The GNU Emacs editor's shared, arc
ii exim4 4.71-3 metapackage to ease Exim MTA (v4)
ii exim4-daemon-light [ 4.71-3 lightweight Exim MTA (v4) daemon
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-3 Python bindings for the VTE widget
ii xdg-utils 1.0.2+cvs20100307-1 desktop integration utilities from
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
2010/3/30 Łukasz Stelmach <[email protected]>:
> Package: reportbug
> Version: 4.10.2
> Severity: wishlist
>
> Yesterday I managed to fix a problem with nvidia-glx package.
> I installed the version from the unstable repository. The I filed a
> bug report about, as I was hoping, the older buggy version. Because
and what version would that be? how can reportbug select the correct
version? how can reportbug know the /older/ version? or you may mean
the two-versions-ago, or any other variation.
> reportbug generates a template with a fat sing "Please type etc." and
> I am not too interested in details of Debian bug reporting process
> I don't even look above that line. I should have. The bug was filed
> against the unstable version which wasn't my intention nad got closed
> immediatelly.
if you "managed to fix a bug" in a version that's already superseded
by the unstable one, then you should not in the first place report the
bug. a fix that's already in unstable will (sooner or later) transit
to testing and then to stable so "there's nothing to fix".
> I wish report bug explicitly asked a question
>
> "File the report against version X.Y.Z [Y|n]:"
Since you know what version you want to file the bugs against, you can
use the option reportbug already provides:
-V PKGVERSION, --package-version=PKGVERSION
specify the version number for the package
> In most cases users hit [Enter]. It'd be closer to other bug tracking
> systems wher users choose on their own the version to be reported
> as buggy.
this is not an argument: using debian BTS you should stick to its
peculiarities, like this one.
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 ---
