Your message dated Wed, 8 Nov 2006 02:24:05 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#395054: Puzzle: my reopening a closed bug results in
closing BTS reply, reportedly from me.
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: bugs.debian.org
Severity: important
A bug gets closed. I reopen it, or attempt to. The BTS replies with a
message claiming that it was closed by me. For full details, see:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=394813
This is doubly confusing:
1) I did not close it.
2) It should be impossible for a bug that's closed to be
closed again.
Hope this helps...
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.16-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
--- End Message ---
--- Begin Message ---
On Wed, 08 Nov 2006, A. Costa wrote:
> On Fri, 3 Nov 2006 22:05:22 -0800
> Don Armstrong <[EMAIL PROTECTED]> wrote:
>
> > > ...It's a question of how much logging and recording
> > > is enough, too much, or too little. I don't know if there's a
> > > general answer, but I know how to scratch where it itches...
> >
> > Again, the bug log keeps the original message, and the record of what
> > it did when it parsed the message. The only thing that isn't kept is
> > the output of parsing the entire message to control, because that can
> > affect multiple bugs, and generally isn't terribly informative anyway.
>
> Pardon, I couldn't quite follow your second sentence above. Were you saying:
>
> That certain output is not publicly recorded because...
>
> 1) ...KEEPING it might "affect multiple bugs".
No, because the output itself involves multiple bugs, and would be
duplicated everywhere.
> As to whether a public html copy of a reopen confirmation email sent
> to the reopener is tremendously informative, I agree it's not. The
> data would only needed once in blue moon, but when needed could be a
> little bit useful. It's like a 'typo' bug. Most of the time nothing
> very bad happens if a typo remains, yet things are slightly better
> when it's fixed.
There's no information contained in the ack sent back that isn't
otherwise available; the only thing that you'd see is the full output
of all of the effects of a single control mail instead of having to
look at the different bug logs to see the same.
Since the original issue behind this report has been resolved, and the
secondary issue isn't one I think is a bug (or am interested in fixing
if it is), I'm closing this bug.
Don Armstrong
--
Our days are precious, but we gladly see them going
If in their place we find a thing more precious growing
A rare, exotic plant, our gardener's heart delighting
A child whom we are teaching, a booklet we are writing
-- Frederick Rükert _Wisdom of the Brahmans_
[Hermann Hesse _Glass Bead Game_]
http://www.donarmstrong.com http://rzlab.ucr.edu
--- End Message ---
