[00:14] <fta> chrisccoulson, micahg: do you have a link to the ubuntu crashes forwarded to mozilla?
[00:14] <micahg> fta: about:crashes should show it
[00:15] <fta> micahg, i mean, not mine, all
[00:15] <micahg> fta: I don't think so
[00:15] <chrisccoulson> fta - not at the moment
[00:16] <chrisccoulson> we currently send distributor information with the crash reports, but they aren't exposed from the server
[00:16] <fta> oh, i see. too bad. thanks
[00:16] <chrisccoulson> i've already bought this up though, so we should be able to search for our own (as in, ubuntu) crash reports soon
[00:31] <fta> chrisccoulson, ok; spread the idea to upstream chromium, to see if it's doable/wanted
[03:08] <BUGa_29plus1> fta: http://discovermagazine.com/2007/jun/in-no-time/article_view?b_start:int=0&-C=
[07:16] <micahg> bdrung: do you have the ubuntu eclipse in git or can I just merge?
[07:56]  * micahg just saw the note about 3.5.2-8,  won't merge until I hear more about it
[07:57] <micahg> nm, it'll be a sync again \o/
[08:35] <fta> jdstrand, fyi, 7.0.517.41 expected soon (critical security update)
[09:13] <dholbach> heya
[09:13] <dholbach> what would be the best way for somebody to install FF2 and FF3 in parallel (for website testing, etc.)?
[09:14] <dholbach> micahg, fta: ^ :)
[10:05] <JanC> dholbach: people are still using unpatched(?) FF2 ?  :-/
[10:06] <dholbach> JanC, man, there's even people using IE6
[10:06] <JanC> at least IE6 still gets some security fixes
[10:06] <JanC> (or got until recently, duno)
[10:07] <dholbach> I was just asking for a web developer who wants to make sure for their projects that stuff works on FF2 too
[10:07] <dholbach> but it seems to be very hard to set it up
[10:19] <JanC> isn't it possible to use upstream builds just by unpacking them in your $HOME somewhere?  (or maybe old mozilla/seamonkey builds, to avoid profile conflicts)
[10:25] <dholbach> JanC, I have no idea - that's why I asked :)
[10:31] <JanC> it works, but if you want to run it next to an existing firefox, you need to start it with a separate profile and the '-no-remote' option
[10:31] <JanC> dholbach: ^^^
[10:32] <JanC> next to = at the same time (but the separate profile is probably needed anyway)
[10:32] <dholbach> JanC, thanks for the suggestion
[10:32] <JanC> so: ./firefox -no-remote -P profilename
[12:09] <fta> dpm, http://people.ubuntu.com/~fta/chromium/chromium-translations.png
[12:17] <dpm> fta, awesome!!! It will take me a few minutes to look at it in detail, but that looks great. Btw, what did you use to create the diagram?
[12:18] <fta> dpm, http://pencil.evolus.vn/en-US/Home.aspx
[12:18] <dpm> ah, cool, I knew pencil for mockups, but I didn't know it could create nice diagrams like that
[12:20] <dpm> fta, with the dotted line on foo.grd I understand that you need the original template for converting back to .xtb translation files, don't you?
[12:23] <fta> dpm, not really, but by the time i get the translations from lp, the upstream template may have changed, so i feed it to the converter so it only adds the translations expected by the package into the final patches
[12:24] <dpm> ok
[12:25] <fta> dpm, it could also allow me to create lang packs for the other builds (beta, stable) which most certainly have an older template, using a single set to string translations
[12:26] <dpm> I see...
[12:26] <dpm> fta, and another question on the diagram: I see that the path for translations is to end up in the Ubuntu packaging branch. I don't see a path for the translations to be committed upstream. Is it me missing something on the diagram, or has that path not yet been contemplated/accepted?
[12:28] <fta> dpm, i'm currently discussing that with upstream. landing the xtb patches in the upstream tree won't help, the strings need to be fed to their internal translations console which is creating those xtb files initially
[12:29] <fta> for completely new xtb files (for empty templates), landing the patches could work as they are not managed by their console
[12:32] <dpm> fta, interesting, thanks. Do you know what their translations console does? I cannot quite understand what it takes as a source to create xtb files
[12:38] <fta> dpm, that's called grit. in the chromium source tree, we only have the client part of grit, able to read grd+xtb and output a langpack. their console takes grd as input and spit xtb on the other side
[12:39] <dpm> fta, I've seen grit mentioned before, but I wasn't sure what it was. Is that only used for translations?
[12:39] <fta> yes
[12:40] <dpm> fta, and what's the format of a langpack. Is that an archive file containing the grd+xtb files?
[12:40] <dpm> or is there more to it?
[12:41] <fta> dpm, some binary .pak files
[12:41] <fta> dpm, some contain translations, some contain various resources
[12:43] <fta> oh, grit also generates some C++ header files
[12:43] <dpm> fta, ok, thanks.
[12:45] <dpm> fta, if there is anything I can help with in the discussion about submitting the translations upstream, please let me know. I think that's would be an important part of the new chromium translations infrastructure
[12:45] <dpm> s/that's/that/
[12:48] <fta> dpm, i 1st need to polish my converter to make sure the strings are unchanged after an export->import. then, once i have some new strings from lp, we'll see how to integrate them upstream
[12:50] <dpm> fta, cool, thanks for keeping me up to date!
[13:03] <dpm> fta, I've already had several people asking me about the chromium translations, the last ones just a couple of minutes ago. People are already getting excited. When all this is in place, translators are gonna love you :)
[13:04] <fta> good :)
[13:14] <dpm> fta, and here is some praise on doing the extra effort to display the comments on the POT template :)
 I must add that all the strings seem to be very well commented
[13:14] <dpm>  here goes nothing, I'm translating :-)
[13:16] <fta> dpm, please don't let him start. i'm thinking about simplifying the strings (hiding the unnecessary xml tags & encoding)
[13:16] <dpm> fta, I know, I know, I told everyone on the channel they shouldn't start until there is an announcement
[15:43] <micahg> chrisccoulson: are you planning to upload the mozilla builds to natty or should I do that over the weekend?
[15:44] <chrisccoulson> micahg - yeah, i'm planning to. but if i don't get around to it, then feel free to do that at the weekend
[15:45] <chrisccoulson> not sure how well that's going to go with gcc 4.5 though
[15:45] <micahg> chrisccoulson: k, well, if it breaks, I'll try to fix it
[15:47] <chrisccoulson> these PPA build hangs are really frustrating me now
[15:47] <chrisccoulson> i just can't recreate them locally
[15:47] <chrisccoulson> i'm going to upload a build today that runs the hanging parts through strace i think
[15:47] <chrisccoulson> not sure how much disk space the builders have though ;)
[15:54] <micahg> chrisccoulson: ah, just saw doko's email about gcc4.5, now I'm worried too :-/
[18:14] <fta> micahg, chrisccoulson; i just extended the dailies to natty
[18:14] <fta> ..but now that i think of it, i'm not sure the ppas are open for natty
[18:17] <micahg> fta: yeah, I"m not sure if they're open either
[21:35] <fta> micahg, now they are
[21:37] <micahg> fta: cool
[21:37] <micahg> fta: that'll let me know if I'll be able to upload the latest version to natty and have it complete :)
[23:24] <fta> chrisccoulson, do you maintain nspluginwrapper?
[23:24] <chrisccoulson> fta - no way ;)
[23:24] <chrisccoulson> how come?
[23:24] <fta> i'd like to land the patch from bug 487141
[23:24] <ubot2> Launchpad bug 487141 in nspluginwrapper (Ubuntu) (and 1 other project) "[Patch included] NPN_GetStringIdentifiers implementation is broken (affects: 1) (heat: 11)" [Undecided,New] https://launchpad.net/bugs/487141
[23:25] <micahg> I think that's one of the things fixed in 1.3
[23:25] <fta> oh? the bug says upstream is unresponsive
[23:25] <micahg> fta: have you read the upstream comments?  Seems all is fine with a 1.3.0 patched version
[23:26] <micahg> fta: oh, wait, upstream is dead :)
[23:26] <fta> yeah
[23:27] <chrisccoulson> yeah, it's just been added to fedora's version of 1.3. it's definately dead otherwise
[23:27] <chrisccoulson> fta - feel free to just upload it
[23:28] <fta> not sure i can upload to multiverse
[23:28] <chrisccoulson> fta - -yeah, you can
[23:28] <chrisccoulson> (as long as you're a MOTU)
[23:28] <fta> ok, will do in natty, too bad for maverick
[23:29] <chrisccoulson> thanks
[23:29] <micahg> I'll give merging 1.3.0 another go later in teh cycle
[23:43] <chrisccoulson> right, hopefully strace will tell me why the firefox builds hang in the PPA now :)
[23:43] <micahg> chrisccoulson: k
[23:55] <chrisccoulson> heh, i don't think this is working: https://edge.launchpad.net/~ubuntu-desktop/+archive/gnome3-builds/+build/1996029
[23:56] <chrisccoulson> "Started 2010-10-13"