[00:11] [reed] - ok, i'm testing a much smaller patch using MOZ_APP_LAUNCHER, but unfortunately, make has decided it's going to rebuild the whole tree :( [00:11] so it might take a little while for me to tell you how well it works ;) [00:40] <[reed]> chrisccoulson: oke === TannerF is now known as Pilif12p [02:26] fta: I just uploaded 0.6+svn20100904r58574+58998-0ubuntu0.2~ucd1 to https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+packages with your patch, to see what would happen [02:26] fta: it hasn't shown up yet, but should soon [02:26] * jdstrand wanders off [02:27] fta: actually, there it is -> https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+build/1954812 === Pilif12p is now known as NeverForget [03:45] my faith in mozilla has been restored. [03:47] http://hacks.mozilla.org/2010/09/hardware-acceleration/ [03:47] until i read that, i was almost positive that 4.0 would treat linux like a second-class citizen. [03:48] this also made me happy: http://brasstacks.mozilla.com/resultserv/data/results/bc854382-c9cd-409e-b083-14a53a13f22d [13:06] jdstrand, hi, if you have time, could you please test build this on arm: https://edge.launchpad.net/~chromium-daily/+archive/ppa/+files/chromium-codecs-ffmpeg_0.6%2Bsvn20100904r58574%2B58998-0ubuntu1~ucd2.dsc (thanks) [14:10] fta: https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+build/1955299 [14:37] jdstrand, i will prepare the chromium minor update asap, which path should i follow? bug + lucid-proposed? [14:38] grrr, lp keeps saying "Start in 1 minute", even after 30min [14:38] yes [14:39] not sure why that is [14:39] it has a high build score... [14:40] fta: I think we should build it in ubuntu-security-proposed like we have been, and I'll copy it to -proposed and we can update the bug accordingly [14:40] fta: with luck, we can get it and the chromium-browser update to users before the 7 days [14:40] jdstrand, it has no security fixes but it's fine for me. [14:41] fta: yes, but I think the chromium update is being held up on this [14:42] even it it wasn't, a regression introduced by -security should be fixed in -security [14:42] jdstrand, i'm talking about ch 6.0.472.55~r58392 (you have 6.0.472.53~r57914 still waiting) [14:42] ok [14:43] https://launchpad.net/builders/ shows what armel is busy with [14:43] a few of those shouldn't take too much longer (hopefully) [14:45] i see there are 2 armel ppa builders, so maybe there's hope [14:51] well, all the packages currently building on arm takes hours, and the q is ~18h :( [14:51] -s [15:15] i wonder how it's possible for a package to be in LOUISVILLE, KY, US at 5:15am, and in PARIS, FR at 7:07am the same day.. [15:25] fta: we're building natively so we have 7 builders. It started a few minutes ago === yofel_ is now known as yofel [17:58] jdstrand, the arm build is fine. i'll release the new ch and those codecs at the same time later today, then push to maverick and hand over the lucid-security debs to you [17:59] jdstrand, also, would be nice to test those builds on arm, not something i can do :( === NeverForget is now known as Pilif12p [19:10] fta: sounds good, though I don't have arm hardware myself :( [19:46] jdstrand, bug 635949 [19:46] fta: Bug 635949 on http://launchpad.net/bugs/635949 is private [19:46] eh?? no it's not [19:47] bug 635949 [19:47] Launchpad bug 635949 in chromium-browser (Ubuntu) "6.0.472.53~r57914 -> 6.0.472.55~r58392 upgrade (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/635949 === Pilif12p is now known as GoHawks [20:43] jdstrand, all done. http://people.ubuntu.com/~fta/chromium/6.0.472.55~r58392-0ubuntu0.10.04.1/ [22:11] fta: I think I misunderstood what you were doing. I thought we were just getting the codecs into proposed to fix arm [22:12] fta: i can get the codecs into -proposed and then we can get the previous chromium out the door, and then SRU the chromium you just gave me [22:12] fta: that will hopefully get the security fixes out on monday without people having to wait longer for the security fixes [22:13] that was a weird sentence... [22:13] but you get the idea [22:20] but you get the idea [22:20] jdstrand, the codecs are worth uploading both for ch .53 and .55 [22:20] * Disconnected (). [22:20] did i miss anything? [22:20] jdstrand, ^^, which part don't you like/want? [22:20] 16:11 < jdstrand> fta: I think I misunderstood what you were doing. I thought we were just getting the codecs into proposed to fix arm [22:20] 16:12 < jdstrand> fta: i can get the codecs into -proposed and then we can get the previous chromium out the door, and then SRU the chromium you just gave me [22:20] 16:12 < jdstrand> fta: that will hopefully get the security fixes out on monday without people having to wait longer for the security fixes [22:21] 16:13 < jdstrand> that was a weird sentence... [22:21] got that [22:21] fta: it isn't that I don't like it-- I just know the SRU process isn't going to like .55 without a wait [22:21] fta: so I want codecs in -proposed now with .53. we release asap (ie monday), then get .55 into -proposed [22:22] since .53 is tested and the only thing holding it back is codecs [22:22] jdstrand, well, nothing i can do for that, right? ;) my job is to provide the bits in a timely manner, if the process makes than unwanted, too bad [22:22] -than+that [22:23] fta: you don't need to do anything. I've uploaded codecs to security-proposed and will get them over to -proposed when they build [22:23] ok [22:23] fta: thanks for your work on it. I'll get chromium-browser building after, so I can get it into -proposed quickly [22:23] (after we publish .53 that is) [22:23] fta: thanks for your work on this :) [22:24] jdstrand, sure, thanks for your work too [22:24] sure, np [22:25] i've also updated all the ppas to have them all in sync and built with PIE: http://people.ubuntu.com/~fta/ppa-dashboard/chromium-daily.html [22:26] fta: nice! that is fantastic :) [22:26] kees: ^ [22:27] ~50 commits in a dozen branches :P [22:28] wow [22:28] with merges in all directions, should be fun to graph that ;) [22:28] heh === GoHawks is now known as HawksWin