[17:18] <Omega> When Firefox 5 is released, will the Natty version of firefox be upgraded to it, or will we stick with 4 all cycle?
[18:15] <micahg> fta: ping re chromium
[18:33] <JanC> Omega: depends on what's easiest for security support I suppose (which probably will require upgrading...)
[18:37] <micahg> what was the question?
[18:39] <micahg> Omega: we'll be upgrading when security support ends on the upstream branch for each of the stable releases
[20:52] <asac> help :)
[20:52] <asac> i upgraded to natty and now this xulprofilemigrator hangs :/
[20:52] <asac> whats that?
[20:52] <asac> seems the old simple copy was rewritten somewhat
[20:52] <asac> with something pythonish
[21:07] <micahg> asac: yeah, it was rewritten to not be version specific, but occasionally, it seems to hang, do you have where it hangs?
[21:10] <fta> micahg, http://people.ubuntu.com/~fta/chromium/10.0.648.205~r81283/
[21:11]  * micahg hugs fta
[21:11] <micahg> fta: thanks
[21:13] <fta> micahg, but with your rule of not accepting simple merges, it's making my life way more difficult, i loose hours cherry picking stuff in all directions. the branches are diverging more and more, for no real benefit. I have a unique branch for the -stable ppa for natty down to hardy.
[21:14] <fta> that's the part that really makes me want to give up
[21:15] <micahg> fta: it's not me, it's SRU rules, an MRE is for the upstream code changes, not packaging
[21:17] <micahg> fta: does the packaging break that much on stable?
[21:19] <fta> micahg, the packaging is made to build everywhere, even with dist patches and everything, yet, i have to undo all that to please those stupid SRU
[21:20] <micahg> fta: so, if we did a one time catchup merge for the next major version bump, would that solve the issue?
[21:20] <fta> in fact, i don't really understand what SRUs are for, i thought it would make my life easier, but it's exactly the same, for the packaging, the workflow and even the delay
[21:22] <micahg> fta: well, for the mozilla stuff, I have the various release specific branches that I update individually for each upload, the packaging is frozen for the duration of the major version, we'll probably have to revisit this when every upload is a new major version
[21:24] <micahg> I guess I'm wondering why it's not bump version, refresh any patches necessary, and "upload"
[21:25]  * micahg thought most of the breakage happens on the dev branch
[21:28] <fta> well, read the commit logs, you'll see why
[21:29] <fta> i'm out, enough for today.
[21:30] <micahg> fta: thanks, I'll get it uploaded tonight
[21:31] <micahg> fta: I'll check the commit logs and see if there's anything we can do to make it easier for you
[21:31] <micahg> fta: but I can't get back to you on that until later in the week
[21:50] <asac> micahg: it hangs after i click the "OK" button
[21:51] <asac> didnt do a backtrace or so
[22:01] <micahg> asac: Chris wrote that, so I'd have to dig into it, I can mention it to him in the morning
[22:01] <micahg> asac: straight upgrade from maverick?  was it ARM?
[22:03]  * micahg will be back in 15-20 minutes
[23:26] <micahg> fta: so, lucid and maverick differ, lucid installs NaCL in .install, maverick doesn't, which is correct?
[23:26] <fta> uh?
[23:27] <fta> drop both, i'll check tomorrow
[23:27] <fta> stupid merges
[23:27] <fta> grrr
[23:30] <micahg> fta: should I upload maverick then so it can go out tomorrow (hopefully) and lucid we'll get out on thursday?
[23:32] <fta> ok for maverick