Your message dated Fri, 15 Jun 2007 07:55:49 -0700
with message-id <[EMAIL PROTECTED]>
and subject line NMUs now send to -done, so this is fixed
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
Version: unavailable; reported 2003-08-09
Severity: wishlist
Hi,
when a bug is fixed (here: automatically by the "Closes:" clause in the
changelog), the submitter gets an email ("done") -- fine! But when the
bug is fixed in an NMU, the BTS defers this mail to the time when the
package maintainer acknowledges the NMU-fix (with another "Closes:").
So, the bug submitter only gets the acknowledgement changelog entry.
While looking up the changelog of an upgraded package isn't hard, I get
complaints from bug reporters when I don't explicitely repeat the
changelog entry from the NMU in the new (NMU acknowledgement) entry. The
Developer's Reference (currently section 5.11.5) doesn't obligate this
kind of redundancy.
So, in my opinion it would be a good idea to automatically send an email
to the submitter not only for bugs closed by the maintainer but also for
NMU fixes. This would also be very appropriate in the (not unusual) case
of packages (not mine :) NMUed for fixes but not acknowledged
afterwards for a long time.
Thanks!
bye,
Roland
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux atari 2.4.20 #1 Fri Apr 4 11:15:24 CEST 2003 i686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]
--- End Message ---
--- Begin Message ---
NMUs now send messages to -done, so this is fixed.
Don Armstrong
--
Dropping non-free would set us back at least, what, 300 packages? It'd
take MONTHS to make up the difference, and meanwhile Debian users will
be fleeing to SLACKWARE.
And what about SHAREHOLDER VALUE?
-- Matt Zimmerman in <[EMAIL PROTECTED]>
http://www.donarmstrong.com http://rzlab.ucr.edu
--- End Message ---
