Bug#575920: reportbug: ask for the version of the package to be reported as buggy

2010-04-01 Thread Łukasz Stelmach
Sandro Tosi mo...@debian.org writes:

 2010/3/30 Łukasz Stelmach lukasz.stelm...@iem.pw.edu.pl:
 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.

First write your reply then maybe read what it is about?

 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.

Such a report might make this happen sooner which might be... convenient
for other, maybe less skilled, users who (they should die and go to
hell) happen to use Debian testing. You know, even noobs sometimes use
google which quite oftne points to bugreports. How about having one with
a workaround?

 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

Great option, I'd like to have yet another one. Dou you like Perl? I do.

 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.

Thank gods there are people who don't alway to stick to peculiarities
and we don't need to program computers with a magnetised needle. If it's
too hard for you to name things properly I ask for a change in the
user's interface. Making the bugreporting interface comfortable is the
first step to get better reports.

 That said, I'm closing this report.
Wonderful feeling isn't it?

-- 
Miłego dnia,
Łukasz Stelmach



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#575920: reportbug: ask for the version of the package to be reported as buggy

2010-04-01 Thread Sandro Tosi
2010/4/1 Łukasz Stelmach lukasz.stelm...@iem.pw.edu.pl:
 Sandro Tosi mo...@debian.org writes:

 2010/3/30 Łukasz Stelmach lukasz.stelm...@iem.pw.edu.pl:
 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.

 First write your reply then maybe read what it is about?

your rule should apply to you to...and you failed.

Ah, you didn't reply to those questions, maybe because you can't;
also, you saved some time, because I don't care.

 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.

 Such a report might make this happen sooner which might be... convenient
 for other, maybe less skilled, users who (they should die and go to
 hell) happen to use Debian testing. You know, even noobs sometimes use
 google which quite oftne points to bugreports. How about having one with
 a workaround?

WTH are you talking about? you don't even know (from what you wrote
above) how packages and bugs fixing are managed in Debian that you can
also take the freedom to be sarcastic?

 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

 Great option, I'd like to have yet another one. Dou you like Perl? I do.

Use that option, stop.

 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.

 Thank gods there are people who don't alway to stick to peculiarities
 and we don't need to program computers with a magnetised needle. If it's
 too hard for you to name things properly I ask for a change in the
 user's interface. Making the bugreporting interface comfortable is the
 first step to get better reports.

No, there's nothing to make more comfortable: read the manpage, pass
the correct option, report the bug. You can also send an email to
sub...@bugs.debian.org if you feel the MUA interface is comfortable
enough to you.

 That said, I'm closing this report.
 Wonderful feeling isn't it?

Yeah, the sound of you going away: priceless.

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#575920: reportbug: ask for the version of the package to be reported as buggy

2010-03-30 Thread Łukasz Stelmach
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 lukasz.stelm...@iem.pw.edu.pl

-- 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  python2.5.4-9An 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-utilsnone  (no description available)
pn  debsums  none  (no description available)
pn  dlocate  none  (no description available)
ii  emacs23-bin-common   23.1+1-5The GNU Emacs editor's shared, arc
ii  exim44.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  gnupg1.4.10-2GNU privacy guard - a free PGP rep
ii  python-gtk2  2.16.0-2Python 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-utils1.0.2+cvs20100307-1 desktop integration utilities from

-- no debconf information



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org