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

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

Control: found -1 3.0~a51-1

Dear Debian maintainer,

(“oh no, not another one”…)

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

I noticed they are actually fixed in unstable, but the 3.0~a57-1 version
contains changes that are not in line with the freeze policy, and I
couldn't find any trace of pre-approval or unblock request, thus the
intent to fix them via t-p-u.

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    :	build the package, ask the RT to
			approve a t-p-u upload and send it to
			DELAYED/7-day*, send the NMU patch to the BTS.
 Thursday, August 30, 2012   :	NMU reaches incoming

* or its equivalent, depending on how long the RT handle the t-p-u request.

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.



Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: