[01:09] <ripps> why hasn't the chromium-daily/dev ppa been updated yet?
[01:12] <micahg> ripps: it updates in about 3 hrs
[01:12] <ripps> :)
[01:40] <chrisccoulson> micahg - seamonkey is updated in the PPA for lucid now
[01:40] <chrisccoulson> and i've uploaded to maverick too
[01:41] <micahg> chrisccoulson: to 2.0.5, right?
[01:41] <chrisccoulson> micahg - yeah
[01:41] <micahg> chrisccoulson: great, thanks
[01:43] <micahg> chrisccoulson: what do we do about uploading to the devel release before the MFSAs are released (Seamonkey)?
[01:44] <chrisccoulson> micahg - i've not been doing that yet. i wanted to be sure that we're allowed to do that before i uploaded it
[01:45] <micahg> chrisccoulson: well, I know for Firefox/Thunderbird asac was in favor of it after the build went through basic QA upstream
[01:45] <chrisccoulson> but before the MFSA's are released?
[01:45] <micahg> chrisccoulson: tomorrow :)
[01:46] <micahg> chrisccoulson: we use USNs for those, so we don't publish any info until after it's released upstream
[01:46] <chrisccoulson> if there are no problems from mozilla's POV with us doing that, then i'm happy to do that
[01:46] <micahg> chrisccoulson: oops, meant to say DMB meeting is tomorrow and I'm #3
[01:46] <chrisccoulson> cool!
[01:48] <micahg> chrisccoulson: it's extended beta testing for them, I think it's ok
[01:49] <chrisccoulson> yeah, it makes sense for us to do that
[01:49] <micahg> chrisccoulson: I only have one question, do we create a new changelog entry in .head for each build released to the archive
[01:49] <chrisccoulson> yeah, we'd probably have to do that
[01:50] <micahg> chrisccoulson: k
[01:52] <micahg> chrisccoulson: we also seem to be getting a lot of these flash crash reports, a lot of times, they have multiple versions installed
[01:53] <chrisccoulson> micahg - yeah, i've been watching those. i'm not sure if the multiple versions is a red herring or not, or whether they're experiencing the same crash i submitted with apport earlier
[01:54] <micahg> chrisccoulson: someone else also managed to submit a plugin crash that was retraced, but it's in Lucid
[01:54] <chrisccoulson> i don't think i've seen that one yet
[01:55]  * micahg needs to report a malone bug about CVEs now :(
[01:55] <micahg> bug 600816 for you chrisccoulson :)
[01:55] <ubot2> Launchpad bug 600816 in firefox (Ubuntu) "Firefox crashes periodically (plugin-container crashed with SIGSEGV in ft_corner_orientation()) (affects: 1) (heat: 10)" [Medium,New] https://launchpad.net/bugs/600816
[01:55] <chrisccoulson> thanks
[03:50] <bobby_> Hey, have there been any issues with Javascript in the most recent build of 3.7a6pre? I can't open Newegg...
[03:52] <micahg> bobby_: broke until I merge 4.0 and fta updates the bot
[03:52] <bobby_> And when will 4.0 be, any idea (This week pl0x?)
[03:55] <micahg> bobby_: I thought I was going to have time this weekend, but I've got a lot that needs to be done ASAP
[03:55] <bobby_> Lol, I know how that feels :D, well take your time, I
[03:55] <micahg> bobby_: I'll try :0
[03:55] <bobby_> Can't wait for the Jaegar JS engine (or whatever it is called)... Sounds epic
[07:30] <fta2> mdeslaur, jdstrand: hi, how long will chromium stay in lucid-proposed?
[07:42] <fta2> chrisccoulson, any idea what could be done for bug 529242?
[07:42] <ubot2> Launchpad bug 529242 in chromium-browser (Mandriva) (and 3 other projects) "chromium doesn't recognize icedtea6-plugin (affects: 13) (dups: 1) (heat: 106)" [Unknown,Won't fix] https://launchpad.net/bugs/529242
[08:40] <BUGabundo_remote> bom dia
[09:54] <chrisccoulson> hi fta2 - i will take a look at that once i've finished with firefox stuff
[13:57] <mdeslaur> fta2: the SRU process says it needs to stay in -proposed for a minimum of a week, and positive testing feedback needs to be left in the bug, which no one did yet
[13:59] <mdeslaur> chrisccoulson: can you confirm I can publish tb 3.0.5 to lucid?
[13:59] <fta2> mdeslaur, well, the thing is the next security update has already been published (~4d ago)
[13:59] <fta2> so we're too slow
[14:00] <chrisccoulson> mdeslaur, yeah, that's ready to go
[14:00] <mdeslaur> fta2: I have no control over the SRU process. It's something that needs to get discussed with the tech board.
[14:00] <mdeslaur> fta2: I agree the SRU process doesn't work for chromium's rapid updates
[14:00] <mdeslaur> chrisccoulson: ok, cool, thanks
[14:04] <mdeslaur> fta2: from the tech board 2010-06-01 meeting: "The board discussed a standing Feature Freeze Exception for Chromium, however since the package has not yet had any SRUs, it was decided that this should be deferred until a reasonable (Kees suggested 3) number had been completed. Martin Pitt will re-raise this once he feels it has proven it's worth an exception."
[14:05] <chrisccoulson> how is this going to work with chromium as default on UNE? shouldn't these updates be going through -security rather than -proposed?
[14:05] <chrisccoulson> or have i missed something?
[14:05] <fta2> mdeslaur, bug 602142
[14:05] <ubot2> Launchpad bug 602142 in chromium-browser (Ubuntu) "Update to latest stable version (5.0.375.99) (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/602142
[14:06] <mdeslaur> chrisccoulson: chromium-browser isn't in main yet
[14:06] <mdeslaur> chrisccoulson: I don't know how it could ship by default if it's in universe
[14:06] <fta2> mdeslaur, the bot should auto-close rsn, i've just uploaded .99 to maverick
[14:07] <chrisccoulson> mdeslaur, yeah, it will eventually be in main. but even if it's in universe, do we still not release through -security?
[14:07] <chrisccoulson> (that is what we were planning with seamonkey updates)
[14:07] <chrisccoulson> (just without a USN)
[14:07] <fta2> mdeslaur, http://paste.ubuntu.com/459819/   it's just a security update this time
[14:08] <mdeslaur> chrisccoulson: oh, right, sorry....so if it's a minimal patch that fixes a security issue, it gets pushed to -security. When it's a whole version update, it needs to go through -proposed, or it needs to get added to the list of exceptions approved by the tech board
[14:09] <mdeslaur> chrisccoulson: there already is an exception for the mozilla stuff
[14:09] <chrisccoulson> mdeslaur, will we have to get it approved by the tech board once it's in main?
[14:09] <chrisccoulson> we basically want to adopt a similar process to what we already do with mozilla really
[14:09] <mdeslaur> fta2: cool
[14:11] <mdeslaur> chrisccoulson: the tech board is already looking at getting it approved as an exception. They just decided to wait until we've done a reasonable number of SRUs to see how smoothly it works. (See tech board notes I pasted above...)
[14:12] <mdeslaur> chrisccoulson: they have been going smoothly thanks to fta2, so I don't see a problem with it being accepted as an exception
[14:12] <chrisccoulson> mdeslaur, that's good then :)
[14:12] <mdeslaur> it just needs to go through the normal process
[14:19] <fta2>   * RELEASE 5.0.375.86~r49890-0ubuntu0.10.04.1 to Ubuntu/lucid-proposed
[14:19] <fta2>   * RELEASE 5.0.375.70~r48679-0ubuntu0.10.04.1 to Ubuntu/lucid-proposed
[14:19] <fta2>   * RELEASE 5.0.375.55~r47796-0ubuntu0.10.04.1 to Ubuntu/lucid-proposed
[14:19] <fta2>   * RELEASE 5.0.375.38~r46659-0ubuntu0.10.04.1 to lucid-security
[14:19] <fta2> mdeslaur, ^^ so it's more than 3 already
[14:20] <mdeslaur> fta2: well, I guess that means they'll re-evaluate it during the next tech board meeting
[14:29] <fta2> mdeslaur, http://people.ubuntu.com/~fta/chromium/5.0.375.99~r51029-0ubuntu0.10.04.1/
[14:30] <mdeslaur> fta2: ok, let me test the one in -proposed today so they get the comment needed to release it first
[14:33] <fta2> mdeslaur, sure. i just hand it to you so you can process it once you feel it's time :)
[14:34] <mdeslaur> fta2: as soon as the one in -proposed is released, I'll upload that one. Thanks for all your work! :)
[14:49] <philinux> chrisccoulson: Are you here?
[14:54] <chrisccoulson> philinux, sort of
[14:54] <chrisccoulson> i'm here, but quite busy ;)
[14:55] <philinux> Ok I raised that bug re bookmarks. https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/602265
[14:55] <ubot2> Launchpad bug 602265 in firefox (Ubuntu) "Maverick: The defaut livecd and installed firefox bookmarks could do with updating. (affects: 1) (heat: 6)" [Undecided,New]
[14:55] <philinux> ubot2 that's clever
[14:55] <ubot2> Factoid "that's clever" not found
[14:55] <philinux> not that clever then
[14:56] <chrisccoulson> philinux, ok, thanks
[14:57] <philinux> Righto
[14:57] <chrisccoulson> ah yes, it's in my inbox now ;)
[14:58] <philinux> One other quicky, is it possible to increase the default width of FF on the livecd
[14:58] <philinux> To like normal website width
[14:59] <chrisccoulson> good question, i'm not too sure how to change that
[15:00] <philinux> When I was raising the bug I realised how small the FF window is width wise
[15:00] <philinux> Does it need a bug rainsing
[15:00] <chrisccoulson> yeah, can do
[15:00] <philinux> ok
[15:01] <philinux> I'll leave you in peace now well relative I suppose
[15:04] <chrisccoulson> philinux, ah, the width comes from the document width
[15:04] <chrisccoulson> which is the size of the home page
[15:04] <chrisccoulson> i think
[15:05] <philinux> Oh so if you don't resize it and visit another page it will resize?
[15:05] <chrisccoulson> i'm not too sure, i could be wrong
[15:05] <philinux> I'll load up my livecd again later this aft
[15:06] <chrisccoulson> it only does that for new profiles. once the profile has been created, the window size persists between sessions
[15:08] <philinux> Ok, I was trying to think how to improve the livecd experience
[15:11] <chrisccoulson> philinux, what is the default window size if you uninstall ubufox before opening firefox for the first time on the live CD?
[15:12] <philinux> I'd have to give that a whirl
[15:12] <philinux> Get back to you after the reboot to livecd
[15:14] <philinux> rebooting
[15:26] <philinux> chriscccoulson: I purged ubufox then I got a screenshot of FF
[15:51] <philinux> chrisccoulsson: Need to send you a screen pic
[16:02] <chrisccoulson> philinux, what happened with it then?
[16:02] <chrisccoulson> wb jdstrand
[16:02] <philinux> Hang on
[16:02] <chrisccoulson> (assuming you've returned from vacation now)
[16:02] <jdstrand> ?
[16:02] <jdstrand> oh 'w'elcome 'b'ack
[16:02] <jdstrand> chrisccoulson: thanks!
[16:03] <chrisccoulson> jdstrand, there's an issue with openjdk on jaunty
[16:03] <chrisccoulson> it needs cacao-source, which is in universe :(
[16:03] <mdeslaur> ugh
[16:03] <philinux> chrisccoulson: screenshot shows it better than words
[16:03] <micahg> chrisccoulson: let me check that
[16:03] <jdstrand> chrisccoulson: I am not caught up on email. was ant uploaded, then openjdk rebuilt?
[16:03] <chrisccoulson> thanks micahg
[16:04] <chrisccoulson> jdstrand, yeah, i've got ant uploaded, then doko wanted me to apply a patch to openjdk to fix another issue before i uploaded
[16:04] <jdstrand> chrisccoulson: k
[16:04]  * jdstrand waits for micahg
[16:04] <chrisccoulson> i've got it uploaded now, but it's waiting on cacao-source in jaunty
[16:05] <jdstrand> cacao-source does not exist in jaunty...
[16:05] <philinux> chrisccoulson: you need to accept the file transfer
[16:05] <jdstrand> oh, yes it does
[16:06] <chrisccoulson> philinux, i don't see anywhere to accept. might be better to mail me it ;)
[16:06] <chrisccoulson> jdstrand, yeah, it's a different source name in jaunty
[16:06] <philinux> Ok what's address
[16:06] <chrisccoulson> philinux, chris.coulson@canonical.com
[16:08] <philinux> chrisccoulson: Ok sent
[16:09] <chrisccoulson> interesting ;)
[16:10] <jdstrand> chrisccoulson: why is it pulling in cacao? I see this on lucid:
[16:10] <jdstrand> icedtea-6-jre-cacao - Alternative JVM for OpenJDK, using Cacao
[16:10] <micahg> chrisccoulson: it looks like there should be some logic to exclude it from jaunty
[16:10] <jdstrand> can we just get rid of that?
[16:10] <micahg> jdstrand: it's a build-depends
[16:11] <jdstrand> micahg: I mean adjust the packaging to remove the build-depends and the created binary for icedtea-6-jre-cacao
[16:11] <micahg> jdstrand: I'm going to pull down the version in the PPA and have a look
[16:11] <jdstrand> micahg: actually, we can't-- icedtea-6-jre-cacao does exist in jaunty
[16:12] <jdstrand> micahg: I'm fine with bringing in the source for cacao into main if I demote all the binaries
[16:12] <jdstrand> micahg: support doesn't change in that case
[16:12]  * micahg is wondering how it built in the PPA w/cacao-source
[16:13] <chrisccoulson> micahg, the PPA's don;t normally enforce the policy of not allowing things in main to pull in from universe
[16:14] <chrisccoulson> but the security PPA does
[16:15] <jdstrand> I think if I move just the source to main in the archive, then the ppa will fall in line
[16:15] <chrisccoulson> jdstrand, hopefully. i'm not sure if doko has any suggestions
[16:15] <jdstrand> mdeslaur: do you have an opinion on promoting cacao source to main, but demoting all binaries to universe?
[16:16] <chrisccoulson> we'd still need the cacao-source binary in main wouldn't we?
[16:16] <chrisccoulson> or is that what you meant?
[16:16] <jdstrand> mdeslaur: it should not change our support status
[16:16] <chrisccoulson> it's confusing having a binary package that ships source code ;)
[16:17] <jdstrand> chrisccoulson: well, the cacao-source package is just source code, right? no executables? presumably meant for building icedtea-6-jre-cacao which is in universe?
[16:17] <mdeslaur> jdstrand: you could also simply upload it to the PPA but never release it
[16:18] <jdstrand> mdeslaur: that would make the next openjdk security update ftbfs, no?
[16:18] <chrisccoulson> hopefully there won't be another update ;)
[16:18] <chrisccoulson> this is jaunty, so there's not much life left
[16:18] <mdeslaur> oh, right, as next time it won't go through the mozilla PPA...
[16:19] <jdstrand> chrisccoulson: maybe not from you guys, but we have them fairly regularly for openjdk
[16:19] <chrisccoulson> ah, ok
[16:19] <jdstrand> let me look at the cacao-source
[16:19] <mdeslaur> jdstrand: I don't mind it being copied to main with binaries in universe, if you can do it
[16:20] <mdeslaur> actually
[16:21] <jdstrand> mdeslaur: I can do it, I sort mis-asked though. there is a package, cacao-source, that is needed in main to build
[16:21] <jdstrand> mdeslaur: if that is only source code (eg, a tarball in /usr/src or something), I think we are fine on support (ie, it doesn't change)
[16:21] <jdstrand> mdeslaur: but if it ships binaries, we'll need to look more closely
[16:21] <mdeslaur> jdstrand: there are no binaries, so just move it to main
[16:21] <mdeslaur> it just installs a source tarball, what a crappy package :)
[16:21] <jdstrand> mdeslaur: confirmed, just ships /usr/src/cacao-0.99.4.tar.bz2 and some stuff in /usr/share/doc
[16:23] <jdstrand> chrisccoulson: ok, cacao is the same version in jaunty as lucid. I will promote cacao-source and its source package in the archive, and be sure to demote everything else. after the publisher run completes (it starts at :05), the dep wait should be gone
[16:23] <jdstrand> mdeslaur: ^
[16:24] <chrisccoulson> jdstrand, thanks
[16:24] <chrisccoulson> i don't need to give the PPA a poke at all?
[16:24] <jdstrand> chrisccoulson: you might, but lets see what happens
[16:24] <jdstrand> it'll be at least an hour before it is in main
[16:25] <mdeslaur> jdstrand: cool
[16:29] <jdstrand> chrisccoulson, mdeslaur: done
[16:29] <chrisccoulson> jdstrand, thanks
[16:56] <micahg> chrisccoulson: I made it :)
[16:57] <chrisccoulson> micahg - yeah, i saw. congratulations!
[16:57] <micahg> chrisccoulson: thanks, now I can do my merges :)
[16:58] <micahg> chrisccoulson: unfortunately, this week I'm very limited with time :(, but will make sure to get them in before alpha3
[16:58] <chrisccoulson> heh, no worries. i might finally be able to start on maverick by the end of the week
[16:59] <chrisccoulson> i'm hoping to have karmic pretty much finished tonight (with the exception of openjdk)
[16:59] <chrisccoulson> i might rest for a bit then ;)
[16:59] <micahg> chrisccoulson: probably a good idea :)
[17:00] <micahg> chrisccoulson: is there anything urgent that I need to get done this week?
[17:01] <chrisccoulson> micahg - i don't think so. did you make any progress on kazehakase?
[17:01] <micahg> chrisccoulson: not yet
[17:01] <micahg> chrisccoulson: haven't had time to look at it
[17:01] <chrisccoulson> ah, ok. i think that's the only app left to port now which breaks when xulrunner 1.9.2 is installed
[17:01] <chrisccoulson> i can maybe look at it later if you don't get a chance to
[17:02] <micahg> chrisccoulson: k, I was going to try backporting the version that was in karmic
[17:03] <micahg> chrisccoulson: they did most of the xul192 transition if not all of it
[17:03] <chrisccoulson> ah, ok. i haven't tried the version in karmic yet actually
[17:03] <chrisccoulson> only in jaunty and hardy
[17:04] <micahg> chrisccoulson: well, I got through about 20 code changes for the hardy version and just decided it might be easier to just backport the karmic version if it works (originally I decided against it since it required GTK 2.16, but fixing that might be easier than all the code changes for xul192)
[17:04] <chrisccoulson> do you know what features from gtk it needs?
[17:04] <chrisccoulson> that can get quite messy ;)
[17:04] <micahg> chrisccoulson: not offhand
[17:05] <micahg> I wanted to see where it failed
[17:05] <chrisccoulson> if it's simple things like gtk_show_uri to show help pages, then it's easy to revert those calls back to their libgnome equivalents
[17:06] <micahg> chrisccoulson: I'll let you know as soon as I find the issue
[17:06]  * micahg doesn't know GTK from anything
[19:48] <chrisccoulson> jdstrand, karmic is looking pretty good now. i've got almost everything ported
[19:55] <jdstrand> chrisccoulson: awesome. wrt jaunty I adjusted the overrides, but the ppa hasn't picked them up yet. I'm not sure why
[19:56] <jdstrand> chrisccoulson: figure we can wait a bit longer
[19:56] <jdstrand> chrisccoulson: actually, lp still shows it as 'universe' so maybe the publisher is offline
[19:56] <chrisccoulson> jdstrand, yeah, i'd noticed it was still waiting too
[21:07] <ddecator> micahg, chrisccoulson: anything i can help you guys out with?