Control: reopen -1!

Hi,

http://www.debian.org/Bugs/Developer#closing states:
»Debian bug reports should be closed when the problem is fixed.«
There is no indication that the problem is fixed, so the bug should not
be closed.

http://www.debian.org/Bugs/Developer#tags also states:
»moreinfo
This bug can't be addressed until more information is provided by the
submitter. The bug will be closed if the submitter doesn't provide more
information in a reasonable (few months) timeframe. This is for bugs
like It doesn't work. What doesn't work?«

I don’t think my bugreport fits that category.
I also do not think that asking "does it work in a newer version?" can
be considered 'moreinfo', but rather 'followupinfo'. Furthermore one
should take a second to see where this might be going. Should every bug
report be re-examined for every new version released and closed if no
one specifically does say "yes, it happens in the new version"?

I cannot provide the information asked for but don’t consider that fact
reason enough to close the bug. If there is actually any indication that
the bug might be fixed in a certain version and no one can confirm then
that the bug still exists, I’d be ok with it being closed. Simply
saying "there is a new version, I’ll just assume this fixes all bugs
from previous version" seems highly naive and counterproductive to me.

Thanks for considering

Hendrik Jaeger


On Fri, 28 Jun 2013 22:39:17 +0000
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the password-gorilla package:
> 
> #522275: password-gorilla: crashes while loading passwordsafe v3
> database
> 
> It has been closed by Alexandre Raymond
> <alexandre.j.raym...@gmail.com>.
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Alexandre
> Raymond <alexandre.j.raym...@gmail.com> by replying to this email.
> 
> 

Attachment: signature.asc
Description: PGP signature

Reply via email to