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

Re: NMUing "maintainer address bounces" bugs



-----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. * debian/control: - Maintainer email
>> address was invalid and bounced. Update it to use a valid
>> address. Patch by Nathan Handler <nhandler@ubuntu.com> Closes:
>> #675214.
> 
> 
> 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 about that package is
> just pointless.

Note that I talked to Gürkan before I did those uploads. I should have
noted that in the changelogs, but it did happen with his approval.

However, I'll follow your approach next time, particularly on packages
where the wrong maintainer address is not the only sign that the
package should really get some love by the maintainer.

Greetings from Salzburg BSP
Willi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJP3cSFAAoJEIy+IZx0V22BbmMP/3K/WLnspeBE74gE1RECWf3G
y2dy8nHjgrtZ8/I2qhkoSuLd2VhLvUpo4nB1zfsfuXIDraLzEBqfnJslrkTAYB72
emclvN4I+8Z+HQHj4XQtMPaHy/l+MpdLHP1YMSiYXFgNYOaHtOr8+XBVNVsis9sJ
4nCDJev7J5t0xOz5wzvP7OMl16qYbcVFE3MzBcZ5DJciI6uHe2Akg+GvqnL+QLwM
YBKvY0ULjdiXA5kExmzTVYSUqg91zWALk/Tkph6w6ep3M1H8aNC7AvFWAmXC+MmG
9EhZGq3aw1wEog3bmqyb21nNIJF3FchdRJP9EztQivs5bL94jqG8AgG9rVvOIfna
uLrTj6JykwlxzNWOnT7IscKifK6wBc+IoY0rvWaLwYWEMcTCmVwKTxwm25Vt0cFa
6enRctSQLqSWBgSxRb3GI81o2t+7He4g/g2zihilSdO7ZE0eTQXHXEsHnpjxHf+w
a1OrThb69pp664y+QzMaNw50eFkSpqYAVmylGJNLL7yvL9K+0dpOiqFDg1lUEq5g
PiWLmjb3TWi+eYOxblV9+aaXpNPRvAecVwNbM81KrvQEbDuCXbqG2ifkm/dXy3Ia
pq4kgNk+mB907XVFZnI6KYy8/oc2Rc497gGclwxov0rS31Gt0MRuKyflTuT5np3j
yIOdPSsrOSwwnWFJaIZT
=c2/o
-----END PGP SIGNATURE-----


Reply to: