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

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



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

Dear Debian maintainer,

(“oh no, not another one”…)

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

 Monday, August 20, 2012      :	send this notice
 Thursday, August 23, 2012    :	post an NMU announcement to debian-i18n
				with you (maintainer) CC'ed
 Tuesday, August 28, 2012     :	deadline for receiving translation
				updates
 Wednesday, August 29, 2012   : build the package and upload it to
			DELAYED/2-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)

iQIcBAEBCAAGBQJQMprsAAoJELgqIXr9/gnyG+8QAItAlVI+wHGwvSXN5es0oOf9
FfmsPE4FIGZ0GGAz61SdW1koKyQ2RS52XkSocOXneTIbfIW9CFeRJffFst1C/ozm
smjPbha45qxSbk4xEovUg0EXmop6g/Mrr+igL7xEGj7j/XizBK1uTE4mLn4rVaW9
bf7oOxlDuMI/ElC6W3lYGWMGf58OYvwgxjXQv9BdXkl5rYG9reUwswS/566MRyCR
CQHalGeRiunFLnebHzQbyJukP5OVkoPHzvVlb4GI8vYY94lk4u0ZYkwonvyEVEnD
FCOZmlyeeFb5JiWDjpo9wiPmh8QsGxDeeAVvTSQ9p/zrsH7FfNTIMOnCkErml1Bo
pF9Npvn61IIM8vZROnPP9aMwZZJjMp68nIRhEYdW0sf2B4zo9IWvvJ/Zkcg852s0
SXKZKHXHVgOFImU6zyf6XSn6FS6GMjL4WcVk01gNk5hoY+UF1Z3hmgdRyZ5cU3Pp
fI3FF7xWMC3INT2MHJXSCVtKcj+BvWQuSwzC5oeNCy8Fn6OrwPzoe1mfdAn4nfCj
n7uIFvm0SRTQEzKtfhYSpqU/aH+SoSWLlXig5EgDaktVho6NtolyCUQxJHsTXQmv
qlEiUV8K4NinGaIVc1+oNU7qKQtE4lb33oHkQIJjFBvoaPkBG6ZA+f+lKd3cX6xU
4iWhp/k2ZntApoW2Qmvq
=XFOl
-----END PGP SIGNATURE-----


Reply to: