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

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



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

Dear Debian maintainer,

(“oh no, not another one”…)

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

 Friday, August 17, 2012      :	send this notice
 Monday, August 20, 2012      :	post an NMU announcement to debian-i18n
				with you (maintainer) CC'ed
 Saturday, August 25, 2012    :	deadline for receiving translation
				updates
 Sunday, August 26, 2012      : build the package and upload it to
			DELAYED/4-day, send the NMU patch to the BTS.
 Thursday, August 30, 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)

iQIcBAEBCAAGBQJQLoBaAAoJELgqIXr9/gnyQdoP/2/xwDM2M80W6aVTsAnUaImU
W0ThfX09sAqMWYFdwkXKgumokQ6uhr1F+//5O+NFv6+yC9iymsBb7X09lrKf4C/U
2r6OsEpOBv7uT7nbfg45GctZGdcC90nWG0QDuBvRsJkQQMss7zOzpd7eWRErNote
p6+xn489klCjRGDQ/5tZjK8UE79P1bzhtH3VBK4Jac6U0R1DOCqqcNhoneOIfJLR
p0OF1jJO9TJ61c3dy9DTJS2Gar8OflMMGHCWGoG3U/GJV0XrB3JmyN4WOVjpPKEA
+EF3Ax08pHQhlD11GutwsoNTayBConMtUWur4wI5iVyIneINY4dEiiC92q52ttYk
fvfcLIv1koVo2dOSq5JKcxZ0MwxlT8/FvMhH/BKm7BgzCi5nXpYrBZ5CHXGv1IPs
ROIZmNBgk2GL+4uFdhBHnbxuavmYmFqZ3M3zaUL1aqnnh2m2HQX/c2fJr8EbD/8y
gv94/GwQ61XhYuwxxOtqUUcTGGQIbS0iLxkTlEnVz1JOYm6mHcde9FrPv/q9s0nV
7xLup4W8ixbGcLKvFB8v/iLk72Jm/EFmJYiF5FyDlF9lxov1dbj6OsjlXcT2B7Fa
nIvXUTqrtXwbm5vA7+thttapvcE/fl7ylXKHa7u2UfWwLRaAsIBW16EH/Pp3PM42
9GkD1hq83GrMyQOgsdcL
=Isu7
-----END PGP SIGNATURE-----


Reply to: