On 20/01/15 16:00, Vincent Lefevre wrote:
> It would be great if the maintainer could *always* receive the mail
> when mailing to nnn@, and not just under obscure conditions. For
> instance, I've been told by some maintainers that if the bug is
> reassigned, the maintainer doesn't receive the mail!
In this situation "the maintainer" is not unique. The maintainer of the
package that previously had the bug does receive the mail, but the
maintainer of the package that now has the bug doesn't.
For instance suppose there's an apparent bug in hello that is actually a
symptom of an underlying bug in libc6, and I send:
To: 123...@bugs.debian.org
Subject: Re: Bug #123456: hello: doesn't work
Control: reassign 123456 libc6
This is not hello's fault because [reasons]. It's actually a
bug in libc.
The maintainer of hello gets my mail, and also the BTS' notification
that #123456 has been reassigned. All good.
The maintainer of libc6 only sees the BTS' notification that #123456 has
been reassigned to them, but doesn't get my email that explains why this
bug is now assigned to their package.
(The current solution to this is a social convention to cc
$new_pack...@packages.debian.org when reassigning to $NEW_PACKAGE.)
S
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54be9cf1.3010...@debian.org
