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

Intent to NMU or help for an l10n upload of drivel to fix pending l10n bugs



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

Dear Debian maintainer,

(“oh no, not another one”…)

The drivel Debian package, which you are the maintainer of, has
pending bug reports which include translation updates or fixes
for translation handled by gettext, namely bug number 661439 (and
maybe other similar bugs).

	http://i18n.debian.net/l10n-pkg-status/d/drivel.html

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 a week) is roughly the following:

 Wednesday, April 25, 2012    :	send this notice
 Wednesday, May 02, 2012      :	post a NMU announcement to debian-i18n
				with you (maintainer) CC'ed
 Saturday, May 12, 2012	      :	deadline for receiving translation
				updates
 Sunday, May 13, 2012	      :	build the package andupload it to
			DELAYED/15-day, send the NMU patch to the BTS.
 Monday, May 28, 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)

iQIcBAEBCAAGBQJPmGzJAAoJELgqIXr9/gnyZXEP/jAKlWA6pcoLZGM9yzKWiFRT
b3Q98yodx3GibXehxYmUSiWcxVcMVb0MSWeyCFmfk8xnckDEDnZ/S2ylz5WKIyPN
qPzeP2iPWRoi5A2u+19PGfPfn75cyrvV1a6DDnpRhgSc50ezQprnX/IGTL/U4w/M
mMLFTy/k+5Kcj658TKtRH2XUtqyIYoXAQGw78BiAcHuHo2psTwZ1CD0Hrui16JAz
H0qwo7tbSztoiyrBUSEmpPyEnOwBU6sNpN5bH3hvkQpEoYldWiAhXwl/rZZIKbOV
JbPSXyeUfrHEXfRA1KjycGiSqZ3p8sO95P11dtDdO9aSK/8QIj4/K5CJ9EBtg6En
+kjkNGSJAkFZ0G4XcowHN5ZcRDoVHVCaC8RRNsACoRqGQH+p0pTFAwATC3VP6tGm
w+hW86SzWLLosgH78bNkB56aZJ64JTmyUdOlL7sfQggVI4rVBZ/t1VTqtByePnj0
3e0S3ljqcf8vYMtOG8iber6xZMYZtQsgoTYZiHc2HOfmW27uaciD2oX0QNVyFTsT
hrHVg4ltZ9X9iAQPwz9DjsmHxSqbhmFyd18C5TZRW7PuZHxgZw989CnEm25sTOo/
nZ1Mk8bq3K2MM3Jum7iOhf5T+spIePDosDI8dIcqgUoq4pWguHLxbOTuRzN3fg9v
fXlVwccGhWLOgtoMKfdR
=0EYK
-----END PGP SIGNATURE-----


Reply to: