[08:30] <dpm> good morning all
[13:12] <kelemengabor> dpm: hi, what should I do, if I'd like to request new langpacks to be generated for Natty?
[13:13] <kelemengabor> The ones in -proposed contain some nice fixes and some ugly mistakes
[13:14] <kelemengabor> I just corrected the latter, and it would be great to push all of them out now
[13:24] <kelemengabor> hm, bug 795844 is interesting too - I think if we push the new langpacks before FF5 is in -updates, FF4 translations will break
[13:24] <ubot4> Launchpad bug 795844 in language-pack-en (Ubuntu) (and 2 other projects) "en_GB Firefox appears untranslated (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/795844
[13:26] <dpm> hi kelemengabor, since we've started the testing period, the PPA updates have been stopped (so that the testers who are testing in natty-proposed and are subscribed to the PPA don't get those updates overwritten by newer ones from the PPA). This means that to get new langpacks you'll have to first wait until the testing period has finished and the PPA is reenabled. Then wait again until the next langpack is generated on the PPA (should be on the n
[13:26] <dpm> ext Wednesday for Natty https://dev.launchpad.net/Translations/LanguagePackSchedule). Then you can either ping pitti to upload it to -proposed or to file a bug in ubuntu-translations and assign it to pitti. I think for now the quickest way is to ping pitti, and if he needs a bug for that, he'll tell you to file that first
[13:27] <kelemengabor> okay, thanks :)
[13:30] <dpm> kelemengabor, it's the first time there's the request from translators for a language pack update, so you'll help defining the process while you're doing it ;)
[13:31] <kelemengabor> :)
[13:48] <kelemengabor> and... what will happen, when FF5 is pushed to -updates, but the updated langpacks (for most languages, who do not QA approve it) not, and current the langpacks do not recommend firefox-locale-xx packages?
[14:56] <dpm> kelemengabor, yeah, that's a good question. I thought about it and I don't have a good answer. That's something the Mozilla team should give some input on. One option is: since now translations are only coming from upstream and we can consider them being tested there so they can be pushed to -updates. In any case, on every FF upload there should be an upload of all the firefox-locale-xx packages
[15:31] <kelemengabor> dpm: sure, that's a must. but how will the firefox-locale-xx get installed? the new langpacks recommend it, the old ones however not
[15:33] <kelemengabor> so I think we need either rebuild the old packs with the new recommendation (if this is possible) and push that to -updates, or push the currently -proposed packages regardless to the QA result
[15:34] <kelemengabor> and in any case, we should not push the QA'd packages before FF5 is out in -updates
[15:35] <kelemengabor> if I get things right
[18:10] <dpm> kelemengabor, that's a good point. I think the "push all to -proposed at least the first time" option will most likely be the approach. I've sent an e-mail to pitti and chrisccoulson about it
[18:11] <kelemengabor> dpm: you mean to -updates?
[18:11] <dpm> kelemengabor, exactly, sorry for the confusion, s/proposed/updates/
[18:12] <kelemengabor> okay :)
[18:16] <dpm> lol, I'm "the big chief"!
[18:16] <dpm> https://lists.launchpad.net/ubuntu-l10n-bem/msg00035.html
[20:41] <trijntje> Hi all, after enabling -proposed for natty firefox is no longer localised to dutch (nl)