Hi!
Long storry short: A couple of days ago, I noticed the e-mails send to
one address of a maintainer could not be delivered. As that e-mail
address was used in several other packages (about 12 IIRC), I opened RC
bugs against these packages.
Some got fixed by the maintainer, some got fixed by o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Alexander!
Am 2012-06-17 11:30, schrieb Alexander Reichle-Schmehl:
> Some got fixed by the maintainer, some got fixed by orphaning the
> respective package, some however got closed in NMUs, like the
> following:
>
>> * Non-maintainer upload. *
Willi Mann writes ("Re: NMUing "maintainer address bounces" bugs"):
> Am 2012-06-17 11:30, schrieb Alexander Reichle-Schmehl:
> >> * Non-maintainer upload. * debian/control: - Maintainer email
> >> address was invalid and bounced. Update it to use a va
Hi,
Alexander Reichle-Schmehl wrote:
> Long storry short: A couple of days ago, I noticed the e-mails send to
> one address of a maintainer could not be delivered. As that e-mail
> address was used in several other packages (about 12 IIRC), I opened RC
> bugs against these packages.
>
> Please d
Hi!
On 17.06.2012 13:50, Willi Mann wrote:
>> Please don't do that! IMHO the proper way to handle these bugs is
>> to see, if the maintainer[1] is fixing them himselve. If (s)he
>> doesn't, then orphan it. But NMUing to fix the mainteiner address
>> of a maintainer who apparently doesn't care
Ian Jackson writes:
> [ Resent with Gurkan's name mangled because of this:
> 550 5.6.0 improper use of 8-bit data in message header
> And yes I know that the RFC says that everyone must mangle
> everything into quoted-unprintable but that's absurd. And
> why start enforcinng it now, de
Russ Allbery writes ("RFC 2047 message header encoding (was: NMUing "maintainer
address bounces" bugs)"):
> It used to be a great way to catch spam in KOI-8 and various Asian
> character sets, although I see from my spam folder that spammers have
> caught on and pr
7 matches
Mail list logo
