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

Exploring the possibility of an l10n upload of efingerd to fix pending po-debconf l10n bugs



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear Debian maintainer,

(“oh no, not another one”…)

The efingerd Debian package, which you are the maintainer of, has
pending bug reports which include translation updates or fixes for
po-debconf, namely bug number 658342 (and maybe other similar bugs).

The i18n team is now hunting the very last bits of missing localization
and your package went on our radar. You may have uploaded recently but,
unfortunately for you, you then got *another* l10n bug report. We
really should prevent translators from translating...:-)

So, sorry for this, but the radar beeped at your package and here am I
with an NMU intent...:-)

In case you can't update your package, I hereby propose, as part of
a more general action of the Debian i18n Task Force to build and
possibly upload a non-maintainer upload for this package in order to
fix this as well as all pending translations for the documentation
and debconf templates.

Of course, an upload made by you would even be better...:-)

Such changes are always harmless, which explains why I safely consider
building NMU's for such issues even though they're obviously non critical.

The schedule for the NMU (in case it happens, that is if you agree with
it or if I don't receive any answer in 3 days) is roughly the following:

 Sunday, August 19, 2012      :	send this notice
 Wedesday, August 22, 2012    :	post an NMU announcement to debian-i18n
				with you (maintainer) CC'ed
 Monday, August 27, 2012      :	deadline for receiving translation
				updates
 Tuesday, August 28, 2012     : build the package and upload it to
			DELAYED/3-day, send the NMU patch to the BTS.
 Thursday, August 31, 2012   :	NMU reaches incoming

If you intent to upload yourself, please discuss with me. I propose
handling a translation update round and I can handle it myself for you.
That will just require a few days.

In case I upload an NMU, I will subscribe to the Package Tracking System
for this package and follow its life for 60 days after my NMU in order
to fix any issue potentially introduced by my upload.

Let me know, as soon as possible, if you have any kind of objection to
this process.

If you'd rather do the fix yourself, I will of course leave the package
alone. Same if you have reasons not to do the update now.

Regards

David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQMPqvAAoJELgqIXr9/gnyG7QP/ReNkugzzqISfOFulEOwjqjG
t0I6yfL+5BPj0/vq8uhivmY83FEaa+q/zRf3iykC6qbqJSy7YCzCZJwS565ZFa1f
1HOyCDme5mps4+c2nJfk/Sj3+4S5WenRPVxSdyt039NkwgDqlY6ko8LCT/2VcJN5
wo5LlYfOf2IIaS5hyy4sho+wH19GuPglxY/xhgFjRCXosxB/ElqLxj8jP1DTo008
8lSOseMfSYsP+mgFdJrHChsTxIAZnsz5ssuXrrL2lGCiJyKX8rPFiursySO0jRBk
KgARXwk2HK8z2HGyKgw3pC5dhsFzgK+hAvZzPTcsFc4E11PxtX8TXGXXcJmRwGIP
XoqUQ4RzzijQsmfghCvoFvrYEGDuryIxL0uZnEbbuxuwlYfDG3LfRbBQPH9r/UYD
Hx0LltJKrN81YgOI22rd7O1GRYCOU+U2FqxhLR+Ys3Ev8U1MqJ/Vl0Vbzk1PNmEP
5KWRkcFRymH7sG0WLhQsaJ2VShLgS1Nweo6bIrgJU6vSIQiyd5CCOgMHqWOuIqv3
c+LiMcTVADG/5DUrdQK+ilQYdM7zq752PUuTktzZYsavv3xUC8voL34APFJdOELh
BeEfTaiIlo2xsdFrVvfqKx8PbZUx/xeQGT+odbJ0F0fuZoGjCN7fPBS7QbIxW9xR
xKMw6ZVBw+ks0jnFESpQ
=HqPa
-----END PGP SIGNATURE-----


Reply to: