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

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



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

Dear Debian maintainer,

(“oh no, not another one”…)

The ez-ipupdate Debian package, which you are the maintainer of, has
pending bug reports which include translation updates or fixes for
po-debconf, namely bug number 680369 (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)

iQIcBAEBCAAGBQJQMPvsAAoJELgqIXr9/gny/fwP/jsPDQ1iiu/dK3OPRPL+aEnO
/8ccYc0ms8j9vIBEBjd7JtjlMG4Vq/PjukPKxWGVyileiUmrAk49F8+7WJ4IS7YU
OdHxWnJWbbwQHEHN+vVTS7DhBLHe1DS2Sr5veMXD2Mk1C0QBOoDEPRMoYdzCIPif
Lce+swvsBaTIzjMvq3Z0+2GI0ScKEkoWPuVj/I7HFLB+2hPBaHt3146pOc3HK6wq
rmIzXZaWRX5k5TaNFuYSlgttKEjn0Pi5XZAX8XnY/CFNqFDGQeMWzWVFQOihlffr
nLVZKpRj++lhIowSV+ZMQ5Ju5wr5+7VKT9Q9KIwm59/PRxwLJyNraEdzpjwKNIxq
1dTqEZDio5KNWMhJcSXO3N1OTLFDD9Rv5/u83oAxKwOY7qpP5LhsZIqGdALTi8Nv
qyGLuiT19q9NovKb35xBAJty67B0sqT55CJ31rhkqKX7YRa3tAHyTLiOE1GDZs23
UpkaORkRXpI6ojjkEZW4vQvkLSVKojCxaydxC6eACGW8efgq7QTLhURKkqtywVY1
wmoPtJiEvLGmj21tnQaxJo1hNbABPQ1A2xM6RDF6jqmu95fRMkQs6iTnV0eOZkOl
xXkKC4ocKBHH4NtZJUuquWkFV+P4kGEleQtx2ZSp3hrRzmQBkn/dQRv/GohPc/pH
ii16YXNEvgtiuk+Lwc0L
=JUk7
-----END PGP SIGNATURE-----


Reply to: