[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Why was Bug#40360 not closed automatically?

I just noticed that the BTS lists 2 outstanding important bugs
(#40360,#40459) against mutt, although they have been closed by mutt_0.95.7-1:

In /usr/doc/mutt/changelog.Debian.gz I read:

mutt (0.95.7-1) unstable; urgency=low

  * New upstream release (closes: #40459, #40360, #39793, #37843, #38005).
 -- Marco d'Itri <md@linux.it>  Sat, 21 Aug 1999 01:33:23 +0200

And http://www.debian.org/Bugs/db/40/40459.html lists three automatically
generated messages, received at 40459-submitter@bugs.debian.org, at
40459-close@bugs.debian.org and at 40360-close@bugs.debian.org.

Especially this last message seems to have gone completly wrong, as the BTS
page for Bug#40360 doesn't show _any_ of those close messages including
that one to 40360-close@bugs.debian.org!

Somehow this automatic bug closing failed, but why?

PGP public key available (KeyID 2EA7BBBD) | Echelon is watching you.
http://www.in.tum.de/~schoepf/pgpkey.txt  |

Attachment: pgpWey3G23HRQ.pgp
Description: PGP signature

Reply to: