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

Exploring the possibility of an l10n upload of cwidget to fix pending l10n bugs



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

Dear Debian maintainer,

(“oh no, not another one”…)

The cwidget 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 655689 (and
maybe other similar bugs like #561147, #655849 or #660944).

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:

 Thursday, April 26, 2012     :	send this notice
 Thursday, May 03, 2012       :	post an NMU announcement to debian-i18n
				with you (maintainer) CC'ed
 Sunday, May 13, 2012	      :	deadline for receiving translation
				updates
 Monday, May 14, 2012	      :	build the package and upload it to
			DELAYED/15-day, send the NMU patch to the BTS.
 Tuesday, May 29, 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)

iQIcBAEBCAAGBQJPmaZQAAoJELgqIXr9/gnyKLoP/2/laxvXUVlaZBIkTbabvMrw
/xGrp3fvUuCWzg2HUwZWny+KbcS+v5xSc2oBXbE/+PsUQJecDf0Ve3B0afnx0XDI
MGMzJzWsOxDgZ3IWgBtFMgnMW6Oqv1GoGCjWgKk5dv2NscXElRKT3yxq6xZhgmBz
Zpsx2oERHZbfPiZ2Tseug6P5JBz0TwOjHHuh8J5z7suoRbRIYL8seNGRUXBk3GEg
eA8q0wDBzUytwGU/16qW697TZFpNGWL2jLC8JWX1avVolKpp1x6zTdkhDxwVsIoD
9K/ILM0sys0MTmKjzc6PBSLuJwNClgycyjMWGMJeFlCeB5POXcmrg+xZL//2eqol
2iayk1gzTFiGixLJWysPgq1Y6CWVN8vLpkjwh8G7223r2vf+nFtjtcgHhkYtae6V
R2CnhjNAAQ4HhhW6qkj/goCZHjdbtGd/x+ko0TeDH+slsFVjK/qh3PPiaTb+H8Rz
G7FSYQY/MQc3oVBvJpqfr4bLEpnaMfXcGd/gqS8WVnt14QLHViKiWpi60QVyEPUr
6YRpDkDjstAszXCz50/p3X+0JdwqwHaLs/NUkVD7c1Y0UlVgz0RIr7S383BNSSs+
OfLDQiJQhdm4hSZhTvg+wPu8oiWL91tg7y/uuBFvkexeNuyKChekV7bZfzpoRlC7
XTuZbD86AfWAPVz0yl/U
=OWvc
-----END PGP SIGNATURE-----


Reply to: