Hi Andreas, Thanks for your quick and positive answer!
Le 21/11/2014 17:49, Andreas Henriksson a écrit :
> On Fri, Nov 21, 2014 at 04:39:36PM -0400, David Prévot wrote:
>> Package: util-linux-locales
>> If you wish, I can also coordinate a short call for translation update
>> in order to gather more up to date translations for Jessie life time.
>> Since this process will take some time (about two weeks), please, let me
>> know as soon as possible if you wish me to go this road.
>
> The more translations the better, right? So if you want to volunteer
> to coordinate the effort, then that's welcome.
Thanks, I should be able to start it tomorrow.
> I'd just like to stress that please be super clear in your call which
> particular deadline people will have to meet to get included
Of course. I’ll base my call using podebconf-report-po where the
deadline wording is pretty clear.
>> I’ll follow up with a proposed Git patch series […]
> I'm still missing 3/3.... maybe it's in-flight
Since the package is in collab-maint, I can push them in a temporary
branch that will ease for your review, comments, etc. I intend to use
the l10n and patch-queue/l10n branches that I’d use and update during
the translation update (and eventually rebase to keep it clean and
incorporate fixes if you don’t mind, but if rebasing of temporary
branches is not welcome, I won’t). I’ll follow this path tomorrow if I
don’t get a NACK.
> The best way to make sure the changes doesn't get lost is to get
> them merged upstream. Please submit your patches upstream ASAP!
Actually, translations are handled via the translation project:
http://translationproject.org/domain/util-linux.html
Since upstream will include translations from there, the translation
patches will only need to be kept in stable, since upstream will update
them in their next release.
> If your patches stops applying in the future I won't really have much
> choice but to drop them anyway.....
Please, do drop them in the next upstream upgrade: only stable is to be
patched (due to the little time between the upstream translation call
for update, and the actual release, it’s hard for translators to keep
up, but our freeze will allow to fix that).
> (If you push things, please poke me to pull from collab-maint.)
As proposed, I may use patch-queue/l10n to push the (gbp pq) actual
patches, and l10n to include them in debian/patches. See for example
what is currently done in the gnupg, gnupg2 and libgpg-error VCSes.
> I'll ack your patches when I have them all and had a chance to look
> at them.
If the proposed workflow suits you, I’ll start pushing tomorrow, and
will ping you back when the translation call is finished and the master
branch ready to be fast-forwarded to l10n.
> (or if you think a debdiff won't be needed, then please go ahead and just
> tell me when we have an pre-approval from release-team on the upload).
I’m confident a pre-approval is not needed here, and I’m already on my
way to coordinate a similar update for gnupg/gnupg2/libgpg-error (and I
did an l10n NMU for util-linux too during the previous Wheezy freeze),
but I don’t mind going forward with a pre-approval if that put you at ease.
Regards
David
signature.asc
Description: OpenPGP digital signature
