Re: Bug#660042: Exploring the possibility of an l10n upload of drizzle to fix pending po-debconf l10n bugs
Hallo Christian,
I'm aware of the current translation bugs. But please do not a NMU at
this time.
Well I wanted to bring the current version to drizzle first avoiding
"resetting" the clock again by the po inclusion.
Today I managed to make an NMU for gearman-interface, which is currently
in DELAY/2. When I understood it correctly, it is the package currently
blocking gearmand, (as it has a dependency on an old version of
libgearman), and the only thing missing is the aging of tokyocabinet,
which I NMU'ed March 1st... So I hope drizzle will be entering testing
around March 11.
My plans are to have either (preferred option) the new upstream version
ready at this date or as a second option a package which includes all
available translations.
If you have any comments or questions, please let me know.
coldtobi
Am Sonntag, den 04.03.2012, 17:36 +0100 schrieb Christian PERRIER:
> Dear Debian maintainer,
>
> ("oh no, not him again"...)
>
> The drizzle Debian package, which you are the maintainer of, has
> pending bug report(s) which include translation updates or fixes
> for po-debconf, namely bug number 660042 (and maybe other similar bugs).
>
> So, sorry for this, but the radar beeped at your package and here am I
> with what I usually call an "NMU intent"...:-). Please take this as a "very
> soft" NMU intent. Of course, there is no hurry or deadline...just
> "old" bugs we think are easy to get rid of.
>
> 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 drizzle in order to fix
> this as well as all pending translations for the debconf templates.
>
> Of course, as you're probably pretty active on that package, an upload
> by you would also be OK...as long as it allows a round of translation
> updates.
>
> Such changes are always harmless, which explains why I safely consider
> building NMUs 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 4 days) is roughly the following:
>
> Sunday, March 04, 2012 : send this notice
> Thursday, March 08, 2012 : post a NMU announcement to debian-i18n with you
> (maintainer) CC'ed
> Friday, March 16, 2012 : deadline for receiving translation updates
> Saturday, March 17, 2012 : build the package and upload it to DELAYED/7-day
> send the NMU patch to the BTS
> Saturday, March 24, 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. That could maybe save you from
> seeing me coming back again in a few months.
>
> In case I upload an NMU, I will subscribe to the Package Tracking System for
> drizzle 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.
>
Reply to: