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

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



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

Dear Debian maintainer,

(“oh no, not another one”…)

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

iQIcBAEBCAAGBQJQLn+SAAoJELgqIXr9/gny2CEP/iX4Cz3Yx57LVwsBWPYQ8wK0
IyuL3ZeIKRke7ZpWKAYMPQ4sIzyLz+A1fvFwLQvOMG1zJvlTbyld4oEsuqqJDzVH
P2Vs7qmJdaPnDlxXuOQ1/yrTvlXuVQN9KxoHOhTXnSEe+rFYVJIv9SFhru5h28Hz
8PxIShUnACD3WscIB/F3nVtKtm9JHsmXD2xt6YGhQidXFvc1oFfBIQ9yT8tK7onX
8udoJ5KC/wx0HcOjqbZ3ahK+eTfZJvE7qwJKf5p2+GGo3MqQNYCVkJIT8OsXobHD
GeWe0oagipszjmaXI085+1x3y21ws6MqEPlXoJ+uHMRRC+N5l/MH8vDM1iYoiKoQ
P4wCwoUD6NjFaZiqFP05StpHFH6yCVX+GH96E4P6AZyoFimMKtiJquH4QC2x931+
cp0pyAR0Xvu/DLJGFAfUNWqOT2w1G2fn76WXxIy97PZ05ys8ykBBdY4g0KewpIMq
CmFXlKzg/aRp8sMjbso+NPYTUZmZ8VfR9GcDbEbt+nXrvNEOQZjP2iHx1r5iDZa0
0PMbjvTn3326AccSI8FhJKf3rMomchpo0BEHfmLbBteqQFLqK3IK5/b/V7R4sMlJ
2acjkE7l+WnjtiT6HOSZKnbnCvdayPHOn8AB27vNwOqm5Dr7kofie5aE1StdhA/S
OACO2+kIH1bMaHBTGT4R
=9Ry9
-----END PGP SIGNATURE-----


Reply to: