[07:40] <cjwatson> Image build errors: #is has fixed up iso.qa.ubuntu.com and I've re-posted the affected images
[07:44] <cjwatson> Wow, thanks to whomever almost cleared out component-mismatches
[07:55] <slangasek> y/w - they were all demotions, so it didn't require much thought ;)
[08:06] <slangasek> cjwatson: hey, I saw you landed support for UbuntuKylin in livecd-rootfs; what else is needed before we can turn on dailies?  Does it just need a properly-crafted cron entry?
[08:14] <cjwatson> slangasek: general cdimage support; I'll be working on that today
[08:14] <slangasek> ok
[08:52] <infinity> slangasek / cjwatson: Yeah, I've been shy about c-m, since it doesn't report on proposed, but I suspect most of the stuff in there was rather old and known-wrong by now.
[10:17] <xnox> slangasek: i was hoping to keep clvm in main, until we have an HA available solution without clvm.
[10:17] <xnox> and filed a seed change to that affect, but didn't get it mergerd.
[10:17] <xnox> will I need a M.I.R. now?
[10:29] <jpds> xnox: No, you can't use mir for HA.
[10:30] <jpds> ;-)
[10:30] <xnox> M.I.R.  - main inclusion reports != Mir display server
[10:31] <jpds> I was pulling your leg.
[10:31] <xnox> =) evil
[10:32] <xnox> this is a second unfortunate name clash. Mir vs M.I.R. and UDD vs UDD
[11:07] <Laney> Other RT members: Has anyone had thoughts on the logind FFe?
[11:16] <tumbleweed> I was avoiding thinking about it. My gut feeling was: "as decided at the last UDS", you mean "as decided at the UDS 2 days before FF" (although I know it's been in progress for longer than that)
[11:18] <Laney> there were some WIs about it from Copenhagen but the detailed implementation plan was decided last week I believe
[11:18] <Laney> I'll write down what I understand to be the steps in the bug but I'm not confident enough to take the decision
[12:32] <cjohnston> The upgrade of VirtualBox to 4.2 in raring broke vagrant. Vagrant has a new upstream release that isn't yet in debian. Would you guys rather just have a patch to fix what is broken, or the upstream release? I am assuming due to FF just a patch?
[13:00] <xnox> cjohnston: patch, please =)
[13:01] <cjohnston> ack
[13:01] <tumbleweed> cjohnston: if you have a simple patch, sure. But it's still early days of the FF, and vagrant is a leaf package, so your FFe would almost certainly be accepted
[13:04] <cjohnston> either way, debian does not have the 4.2 fix or the new upstream version, and there is nothing else that's released that we need to my knowledge, so I'll do a patch to make it quicker.. we already have one patch in from upstream
[13:05] <cjohnston> thanks guys
[14:21] <jbicha> does goffice need to be manually kicked to migrate out of -proposed? now that we have goffice0.8 there shouldn't be anything keeping it back, right?
[14:23] <stgraber> jbicha: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt shows that migrating goffice would break a whole bunch of stuff
[14:23] <jbicha> stgraber: but it's lying, right?
[14:23] <ScottK> jbicha: Why do you think that?
[14:24] <jbicha> goffice0.8 should be providing everything that gnucash & gnome-chemistry-utils needs
[14:25] <jbicha> do we need a no-change rebuild to unconfuse britney?
[14:25] <ScottK> Do they need rebuilding for the new version?
[14:25] <ScottK> Britney is rarely actually confused.  It's more commonly unclear about what is upsetting it.
[14:28] <cjwatson> Let me check
[14:28] <cjwatson> I suspect goffice and goffice0.8 need to be hinted in together.  I'll try that
[14:29] <cjwatson> A no-change rebuild will not help
[14:32] <cjwatson> Hinted.  Let's see how that works.
[14:45] <stgraber> smoser,utlemming: are you planning on doing a beta1 release for the cloud images (just wondering as you've done alpha2)?
[14:45]  * smartboyhw wonders about Xubuntu too
[14:45] <stgraber> smartboyhw: xubuntu is participating
[14:46] <smartboyhw> stgraber, /me doesn't see email
[14:46]  * smartboyhw throws his GMail
[14:46] <stgraber> smartboyhw: it wasn't a public e-mail
[14:46] <smartboyhw> stgraber, weird:P
[14:46] <smartboyhw> sorry then
[14:46]  * smartboyhw thinks almost everyone is in (except Desktop) 
[14:55] <cjwatson> jbicha: That worked
[14:56] <stgraber> JackYu: ok, I marked both you and ypwong as contact for UbuntuKylin beta1
[14:57] <jbicha> cjwatson: great!
[14:57] <stgraber> JackYu: starting today at 21:00 UTC, images will start showing up under the beta1 milestone on iso.qa.ubuntu.com, you can test them there and report your results. Once you're happy with the images, let me know and I'll mark them ready for you.
[14:57] <stgraber> JackYu: for the announcement, I'll also need an URL to include pointing to some kind of announcement and release notes for UbuntuKylin
[14:58] <cjwatson> Well.  Hopefully
[14:58] <cjwatson> If I can make the builds work
[15:01] <cjwatson> I'm currently waiting for ubuntu-meta 1.296 to reach raring before I try again
[15:02] <JackYu> stgraber: thanks.
[15:03] <ScottK> cjwatson: Is there any chance of Ubuntu Gnome images today or is that the next iteration post-beta 1?
[15:04] <stgraber> cjwatson: I created the product on the iso tracker and updated the python branch to know where to push it. So hopefully the first succesful build should get properly published the whole way through
[15:04] <cjwatson> ScottK: I have to wait for https://code.launchpad.net/~cjwatson/launchpad/add-ubuntu-gnome/+merge/152548 to be reviewed/landed/tested/deployed
[15:04] <cjwatson> I plan to bug the Australians about it as soon as I see them online
[15:04] <ScottK> OK.  So later.  Thanks.
[15:06] <cjwatson> stgraber: Thanks.  I added a test case to match
[15:08] <JackYu> stgraber: any requirement of the URL? is the Wiki page OK? https://wiki.ubuntu.com/UbuntuKylin or the forum website: http://www.ubuntukylin.com/ ?
[15:10] <rtg_> why is linux (3.8.0-12.21) still in -proposed ? shouldn't britenny have kicked it loose ?
[15:11] <rtg_> or is it spelled brittany ?
[15:11] <rtg_> doesn't look right either
[15:12] <stgraber> JackYu: most flavours give a URL to a specifc announcement, something like http://www.ubuntukylin.com/news/ubuntukylin-13.04-beta-1-announcement
[15:13] <stgraber> JackYu: that way the page remains relevant in the future and covers specifically what was done for the milestone
[15:13] <stgraber> JackYu: but that's up to you ;) if you prefer to simply point to the website or wiki, I'll just do that
[15:15] <cjwatson> rtg_: it's spelled "proposed-migration" :-)
[15:15] <cjwatson> (The tool on disk is spelled "britney")
[15:15] <rtg_> hmm
[15:15] <cjwatson> d-i hasn't been updated, for one thing.  I'll do that now
[15:16] <rtg_> cjwatson, is promotion dependent on d-i ?
[15:16] <cjwatson> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt has a list of packages broken
[15:16] <cjwatson> Yes
[15:16] <rtg_> ok
[15:16] <JackYu> stgraber: Sure. please use the website first. I will create a page soon and update the URL.
[15:17] <cjwatson> Yeah, it's just d-i.  Scroll down to the end of update_output.txt where it tries all of linux, linux-meta, and linux-signed at once
[15:17] <stgraber> JackYu: ok, let me know when you have the final URL. I don't technically need this until Thursday.
[15:17] <JackYu> stgraber: ok:)
[15:18] <rtg_> cjwatson, ok, guess I should learn how to update d-i
[15:19] <rtg_> I think apw has done it as well
[15:19] <cjwatson> meh, Adam and I are both fine with doing it, and it often needs to go along with archive admin too
[15:19] <rtg_> wfm
[15:21] <apw> rtg_, yeah it all goes wrong cause you need the aa to new things anyhow
[15:21] <cjwatson> d-i's on its way now
[15:36] <slangasek> xnox: binaries don't require an MIR
[15:38] <xnox> slangasek: ack.
[15:38] <xnox> slangasek: now the question is, how do I seed clvm into server-supported, without it appearing on the server.iso?
[15:38] <xnox> or shall I simply seed it into supported.
[15:39] <slangasek> xnox: "*supported" is unrelated to what goes on the ISO
[15:39] <stgraber> xnox: just use supported-misc-servers
[15:40] <stgraber> xnox: or one of the other supported-* if it's not server-specific
[15:40] <stgraber> supported-server is based on: supported-misc-servers supported-hardware-common supported-installer-common supported-network-common supported-sysadmin-common build-essential supported-development-common supported-kernel-common
[15:41] <xnox> awesome thanks.
[15:43] <xnox> that should do it, I hope.
[15:56] <stgraber> utlemming, smoser: so I'm going to remove the cloud images from the beta1 manifest for now. Let me know if you want to participate and I'll add you back in.
[16:06] <xnox> it worked =)
[16:10]  * slangasek promotes
[16:20] <infinity> rtg_, apw, cjwatson: FWIW, I'm not against the kernel team learning to do d-i ABI bumps after the override/promotion bugfix is landed, but right now d-i promotions (well, more precisely: kernel promotions) explode the whole world and need an AA to babysit, so not much point.
[16:21] <rtg_> infinity, ack
[16:21] <infinity> cjwatson: Speaking of, I'll get this override race.  Thanks for the upload.
[16:22] <cjwatson> infinity: you might not have to
[16:22] <infinity> cjwatson: Oh, did your fix land?  In that case, I'll check and see if I have to, and do a happy dance if I don't. :)
[16:22] <cjwatson> infinity: yeah, deployed this afternoon, but please do check
[16:22]  * infinity nods.
[16:23] <cjwatson> (maybe we should do that d-i meta-udeb magic before encouraging more people to do d-i bumps, too)
[16:23] <infinity> Yeah.  I'll do that this week and upload it after stgraber's beta to avoid being disruptive.
[16:24] <infinity> Oh, the other minor gotcha is the part where amd64 builds silently ignore linux-signed if it's out of sync.
[16:24] <infinity> I think maybe we should just make that a hard failure instead of a WTF.
[16:24] <infinity> Otherwise, people will get caught by signed being unbuilt or NEW again and again.
[16:25] <cjwatson> infinity: There was a tedious syntactic problem in pkg-list
[16:25] <cjwatson> It's optional because otherwise other architectures break ...
[16:26] <cjwatson> So I need to fix that properly
[16:26] <infinity> cjwatson: Sure, but one could just do a test in Makefile and error out.
[16:26] <infinity> cjwatson: Since there's already a part where we copy signed if it's there.
[16:26] <cjwatson> I guess, but that sucks when we have all this fancy pkg-list stuff.
[16:26]  * infinity shrugs.
[16:26] <cjwatson> But be my guest :)
[16:26] <infinity> If you want to make pkg-list do something fancy, go nuts, I just want the build to not silently succeed and be broken. :)
[17:13]  * cjwatson fixes the cause of that Lubuntu image build failure
[17:13] <cjwatson> Kylin looking more promising ...
[17:14] <phillw> cjwatson: thanks :)
[17:28] <ScottK> stgraber: I think we're about at the time where migration freezes should go in place.  Since you volunteered to take care of that ....  If you look in the bzr history for the block I put up for Alpha 1/2, please just use that one again.
[17:28] <stgraber> ScottK: ok, will do
[17:28] <ScottK> Riddell: ^^^
[17:29] <ScottK> Thanks.
[17:29] <Riddell> aww I wanted to upload one last thing
[17:30]  * Riddell hurries
[17:32] <ScottK> Riddell: We can still force stuff through as needed.
[17:33] <Laney> unblock overrides block afaik
[17:37] <stgraber> damn lillypilly is really slow today... I've been waiting for rmadison results for the past 3min ;)
[17:38] <cjwatson>  17:38:15 up 93 days, 19:56,  9 users,  load average: 21.35, 24.57, 19.35
[17:38] <stgraber> Riddell: what's up with your qtwebkit-source force hint? it's been there for a while now and the package is still in proposed
[17:38] <ogra_> cjwatson, oh, a pandaboard compiling webkit ?
[17:39] <ogra_> (on SD card)
[17:39] <cjwatson> no, lillypilly, I fear
[17:39] <ogra_> ouch
[17:39] <Riddell> stgraber: dunno, I've not looked into it alas
[17:39]  * ogra_ hopes they didnt secretly replace lillypilly with a panda then 
[17:40] <cjwatson> Oho!  http://cdimage.ubuntu.com/ubuntukylin/daily-live/current/
[17:40] <ogra_> whee
[17:41] <stgraber> and it published to the tracker, success!
[17:41] <ogra_> oversized though ... better drop all the asian langpacks :P
[17:42] <xnox> ogra_: more like german, french and spanish.
[17:42] <ogra_> pfft, you cant install without having german, french and spanish installed :)
[17:44] <ogra_> Riddell, so somehow that nexus7 kubuntu image fell under the radar due to everyone being busy with blogposts ... should we start digging back in during this week ? or do you prefer to wait until after your beta
[17:44] <stgraber> Riddell: hmm, can't find anything obviously wrong with it or reference to the source/binaries in the britney output. I'm pretty new at that stuff though so may be worth having cjwatson take a look to see what's wrong.
[17:44] <stgraber> anyway, not really beta1 related ;)
[17:45] <cjwatson> Hmm
[17:45] <Riddell> ogra_: I still haven't got my nexus to wake from the dead, I just ordered another one but that'll take a few days to arrive so I can't see it happening for beta 1
[17:46] <ogra_> Riddell, ok, i'll keep it on my todo
[17:46] <Riddell> stgraber: yes nothing in excuses or update_output.txt
[17:46] <cjwatson> Riddell: 16:22 <cjwatson> Oh, and if you're adding a new file there you need to edit britney.conf in lp:~ubuntu-release/britney/britney2-ubuntu/
[17:46] <cjwatson> you didn't do that
[17:47] <Riddell> aah
[17:47] <cjwatson> see e.g. r324 in that branch
[17:48]  * Riddell makes it so
[17:49] <stgraber> ScottK: the block is now in place
[17:49] <stgraber> will be extended if any other flavour sends me a list, though the current one appears to cover most of the core bits
[17:51] <bdmurray> slangasek: I'm inclined to release the fix for bug 780602 to precise although there is not fix for Q yet.  cyphermox is working on it though last I heard.
[17:51] <ubot2`> Launchpad bug 780602 in OEM Priority Project precise "nm-applet leaks memory and stops functioning after a while" [High,In progress] https://launchpad.net/bugs/780602
[17:53] <slangasek> bdmurray: yeah, seems reasonable to me
[18:01] <ScottK> stgraber: Thanks.  To the extent it doesn't cover all the core bits, I messed up.  Please feel free to extend it.
[18:03] <phillw> stgraber: I'm not sure what you require - do you want a list of what is on lubuntu iso's ?
[18:04] <ScottK> phillw: By source package.
[18:04] <phillw> I know Julien has the list somewhere... I'll go dig :)
[18:07] <stgraber> phillw: if there are source packages you want to make sure won't change between now and the release of beta1, send me a list and I'll update the hints. If those are packages that only you guys maintain, it's probably fine just not to upload them
[18:09] <phillw> stgraber: on my last chat with Julien over the weekend, he assured me that he was finished with any updates pertaining to 'LX' stuff and was 'good to go' for Beta 1.
[18:10] <phillw> whilst I am a 'release' manager, I'm there only for when he isn't available :)
[18:30] <stgraber> slangasek: do you think introducing the 3 missing user jobs to make upstart user sessions usable requires a FFe? (they wouldn't be used by default, it's only for those who want to turn on user sessions by modifying /etc/upstart-xsessions)
[18:32] <xnox> imho, we agreed that it's fine =)
[18:32] <xnox> but I am expecting all those packages blocked by beta1 now.
[18:32] <xnox> (although shouldn't affect them at all...)
[18:33] <stgraber> xnox: yeah, they are, but I'd still upload to -proposed just so I don't have to remember to do it later ;)
[18:33] <xnox> stgraber: I'd say "got for it", but I don't have the appropriate hat to say that.
[19:12] <tkamppeter> Due to the Rolling Release discussion and the UDS last week I did not succeed to do all version updates in time for FF last Thu. Especially Ghostscript 9.07 is missing as it depends on the fix of bug 1126427 which RAOF will work on tomorrow (today is a holiday in AU). Can I update Ghostscript after this fix without a formal FFe, probably tomorrow (Tue) or Wed?
[19:12] <ubot2`> Launchpad bug 1126427 in lcms2 (Ubuntu) "LCMS2 needs multi-threading fixes to work with the new Ghostscript 9.07" [High,New] https://launchpad.net/bugs/1126427
[19:22] <xnox> Files a new FFe bug 1153731
[19:22] <ubot2`> Launchpad bug 1153731 in ubiquity (Ubuntu Raring) "[FFe] Ubuntu One sing in or up or skip plugin" [High,New] https://launchpad.net/bugs/1153731
[19:32] <seb128> tkamppeter, it's better to file a FFe bug I think, that shouldn't take too much time and will make review easier, just state the content of the update and the rational
[19:40] <infinity> tkamppeter: Do you have a quick summary of changes from 9.06 to 9.07?
[19:43] <infinity> tkamppeter: New libgs, for instance?  API changes, or just ABI?  Massive new untested features?
[19:47] <stgraber> infinity: oh, since you're around :) do you have an opinion (FFe or not) on those 3 upstart user session jobs I'd like to push (dbus, gnome-session and gnome-settings-daemon)? they don't cause any change to the default user, they just make it possible for those who want to test user sessions (after they enabled them in /etc/upstart-xsessions)
[19:48] <seb128> hum
[19:48] <seb128> speaking of which
[19:48] <seb128> is there any chance we change the ubuntu session to be an upstart user session in raring? ;-)
[19:48] <infinity> stgraber: I'd rather you get vorlon's opinion on that, as he's been closer to the development and testing of those features.
[19:48] <infinity> seb128: See above.
[19:48] <stgraber> seb128: not sure, that change would definitely need a FFe though :)
[19:49] <seb128> infinity, do you avoid using slangasek on purpose or just old debian habit? ;-)
[19:49] <seb128> stgraber, ok, do you plan to file a ffe then?
[19:49] <infinity> seb128: He's still vorlon on OFTC, I don't context switch well.
[19:50] <infinity> seb128: I don't still call cjwatson Kamion because he isn't Kamion anywhere anymore.
[19:50] <stgraber> seb128: it mostly depends on the state of the user jobs for the other gnome bits. The upstart feature is in and with the jobs I have here (dbus, gnome-session and gnome-settings-daemon) it makes it all usable.
[19:50] <seb128> stgraber, well, a few desktopers have been running it for some weeks without issue
[19:50] <seb128> so I would +1 changing the unity session
[19:51] <seb128> it = whatever was in your ppa when you called for testing
[19:51] <seb128> does that include those jobs?
[19:51] <Laney> it also seems to work under shell here so perhaps the gnomers would be interested in that
[19:51] <stgraber> seb128: ok, good to know. I wasn't sure whether we actually felt like this would bring us anything for 13.04 (as in, actual advantage vs standard gnome-session since we don't have packages shipping jobs yet)
[19:51] <phillw> cjwatson: I'm sorry for repeating, as you could already have answered when my link was down (it is dying regularly today), is there any news on the lubuntu alternates.. can you repeat an answer to balloons in case I disappear again.
[19:51] <seb128> well, it's a chicken-egg thing
[19:52] <seb128> if you don't enable it we can't start shipping jobs
[19:52] <stgraber> Laney: yeah and I remember testing with fallback too and it worked. I guess anything using gnome-session should be fine
[19:52] <cjwatson> phillw: Dinner intervened
[19:53] <Laney> Hmm, actually there was something
[19:53] <phillw> cjwatson: I have no issues at all with dinner... glad that I'm able to use the microwave for mine after the earlier power cuts :D
[19:53] <cjwatson> phillw,balloons: Lubuntu alternates building again now
[19:53] <Laney> Replacing or otherwise using the other Xsession.d snippets - here {ssh,gpg}-agent and im-config
[19:53] <stgraber> seb128: ok, so I'll try to get the missing bits (dbus, gnome-session, gnome-settings-daemon) in today (with or without FFe, depending on how slangasek feels). Then I'll send another e-mail to ubuntu-devel saying that people can test using what's in the archive by just changing /etc/upstart-xsessions and if it all looks good, we'll do the switch post-beta1 (Friday-ish). Sounds good?
[19:53] <Laney> I didn't check if the final package brings those back
[19:54] <cjwatson> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[19:54] <cjwatson> 19:52 <cjwatson> phillw: Dinner intervened
[19:54] <cjwatson> damn, sorry
[19:54] <cjwatson> 19:53 <Laney> Hmm, actually there was something
[19:54] <cjwatson> 19:53 <phillw> cjwatson: I have no issues at all with dinner... glad that I'm able to use the microwave for mine after the earlier power cuts :D
[19:54] <cjwatson> touchy touchpad
[19:54] <Laney> stgraber: ^
[19:55] <stgraber> Laney: nope, I haven't dealt with those yet. Those should be converted to upstart jobs in their respective package + add a '[ -n "$UPSTART" ] && return' statement to their Xsession scripts
[19:56] <stgraber> Laney: do we have a list of those?
[19:56] <Laney> Then you'll have to move the script back to 59upstart?
[19:56] <seb128> stgraber, Laney: sounds good to me
[19:56] <Laney> you should be able to use apt-file or whatever to see what puts scripts in Xsession.d
[19:56] <stgraber> Laney: nope, we have 00upstart that sets UPSTART in the environment and 99upstart that sets STARTUP
[19:58] <Laney> But currently upstart wipes $STARTUP out anyway so there's not much point making them conditional
[19:58] <stgraber> Laney: hmm, indeed :) so we just need matching user jobs for them
[19:59] <Laney> It appears to make sense to me to support them in $STARTUP up until they get converted to jobs and then [ -n ... ] them out once that happens
[20:01] <stgraber> Laney: well, yes and no, the problem at least with the IM stuff is that they have a tendency to start a dbus session bus, which creates a bit of a mess as upstart spawns dbus-daemon too. So while in theory we could simply append to STARTUP, it was far safer to just override it, thereby ensuring we at least get a working session everytime (even if some bits are missing)
[20:02] <Laney> so we have to make sure to get a job for that one ;-)
[20:03] <Laney> It seemed hard to me in my ignorant poke though - spawns three processes IIRC
[20:03] <stgraber> since we're talking about a bit more than just the 3 missing user jobs, I'm going to file a generic FFe for that stuff, so I don't need to nag people for every affected package (as I'm guessing we'll find a few more as we go)
[20:04] <Laney> I think doing the basic three jobs is fine for now
[20:06] <slangasek> stgraber: 3 missing user jobs> I don't think that warrants FFe paperwork, it's obviously low-risk
[20:06] <stgraber> slangasek: ok, good. I'll finish testing then and just push those to the archive
[20:13] <cjwatson> phillw,balloons: Lubuntu alternate build succeeded
[20:14] <phillw> cjwatson: thanks :)
[20:40] <utlemming> stgraber: cloud images are going for B1 for raring
[20:40] <utlemming> also, does anyone know when Hardy Server EOL's?
[20:41] <stgraber> utlemming: ok, adding them back to the manifest then
[20:41] <utlemming> stgraber: did someone tell you otherwise, or no ack?
[20:42] <stgraber> utlemming: nope, I just dropped it earlier today as I wasn't explicitly told you'd do beta1. (Those milestones are opt-in, so I need to be told who participates ;))
[20:43] <utlemming> stgraber: right, okay, good to know. Please opt in the cloud images for Beta-2 and RC as well then.
[20:43] <stgraber> utlemming: ok
[20:55] <infinity> utlemming: hardy EOL is around raring release, give or take a week or two.
[20:55] <utlemming> infinity: ack, thanks...and that's what I thought :)
[20:56] <infinity> utlemming: From a support perspective, it's effectively EOL already except for critical security issues.
[20:56] <Daviey> infinity: hey, can you weigh in on - bug 633109.  I see you commented on it before.  Can you follow up further.  It's in the queue, and would be nice to either reject or process it.
[20:56] <ubot2> Launchpad bug 633109 in dput (Ubuntu Precise) "No progress bar for sftp uploads" [Undecided,New] https://launchpad.net/bugs/633109
[20:56] <infinity> utlemming: (Not that we wouldn't take paid support for it, of course, but you know what I mean, developers gave up a while ago on SRUs)
[20:56] <utlemming> infinity: right. I'm just looking forward to turning hardy off
[20:56] <utlemming> infiinity: for cloud image builds
[20:57] <infinity> Daviey: Running out the door for a doctor's appointment, but I'll weigh in when I get back later and either reject or accept, yeah.
[20:57] <Daviey> infinity: thanks
[20:59] <stgraber> cronjobs disabled for the flavours taking part in beta1
[21:03] <stgraber> ScottK, Riddell: are you ready for your first beta1 candidate or are you waiting for some packages to finish building?
[21:04] <tkamppeter> infinity, API of libgs does not change, update is practically only bug fixes. No important new features.
[21:04] <tkamppeter> infinity, the usual every-six-months update of GS.
[21:06] <infinity> tkamppeter: If there's no ABI or API bump, and no massive new changes, I'm fine with it.  In fact, other than the version number, that doesn't sound like it has "features" worthy of an FFe in the first place.
[21:10] <Daviey> stgraber: Did we stop bzr committing cron changes?
[21:12] <stgraber> Daviey: no, but we usually don't commit the changes done temporarily during milestone testing
[21:13] <stgraber> so that on Thursday I can simply do a bzr revert and have nusakan back to normal
[21:15] <tkamppeter> infinity, see release notes on http://www.ghostscript.com/doc/current/News.htm
[21:15] <ScottK> stgraber: AFAIK we're ready.
[21:16] <stgraber> ScottK: good. I'll make sure everything is built or building before I EOD then (in 45min or so)
[21:16] <ScottK> Thanks.
[21:16] <tkamppeter> infinity, do you know about the differences of the GNU Affero General Public License (AGPL) to the GPL? Can we still ship GS?
[21:17] <Daviey> stgraber: Ok, I thought i was criticised previously for not committing a change like that before.  bzr reverting to a revision shouldn
[21:17] <Daviey> 't  be problematic. :/
[21:21] <stgraber> Daviey: ah, I don't think I ever complained when people made temporary changes during milestone testing. I usually complain when there are leftovers after a milestone is out ;)
[21:48] <jdstrand_> can someone push chromium-browser 25.0.1364.160-0ubuntu1 from raring-proposed to raring?
[21:48] <jdstrand> it is stuck in -proposed because it ftbfs on armhf. that is being worked on
[21:49] <jdstrand> (we did this last time fwiw)
[21:50] <stgraber> jdstrand: I'll do that
[21:51] <jdstrand> stgraber: cool, thanks :)
[21:53] <stgraber> jdstrand: pushed the britney hint so it should get migrated to raring with the next run
[21:53] <jdstrand> perfect, thanks again :)
[22:11] <robert_ancell> ScottK, can we remove the block from lightdm? It was a few hours late to the feature free and I asked for an exception. I'm not sure who I have to convince it's good to go, but there don't seem to be any problems coming from -proposed
[22:12] <ScottK> robert_ancell: Did you file an FFe and was it approved?
[22:12] <robert_ancell> The changes are mosly bug fixes and one major improvement (adding Qt5 support)
[22:12] <seb128> ScottK, there is no FFe material in there...
[22:12] <seb128> or nothing impact on current installs at least
[22:12] <robert_ancell> ScottK, I was going on the "we will be lenient due to the confusion around 13.04" and it was just a few hours late
[22:12] <seb128> you can consider binding fors Qt5 as a new feature, but that will not break anything existing
[22:12] <seb128> and it was only a few hours late
[22:13] <ScottK> OK.
[22:13] <robert_ancell> ScottK, ta
[22:13] <seb128> ScottK, thanks
[22:14] <ScottK> I dropped my block.  It may be caught up in the Beta 1 block though.
[22:14] <ScottK> If it isn't, it probably should be.
[22:15] <ScottK> Yes.  It is.
[22:15] <seb128> ScottK, thanks, I was surprised that you blocked it, that was not obvious
[22:16] <seb128> I had to go look at what was happening when robert_ancell pointed it didn't move to raring
[22:17] <seb128> seems a bit harsh to have blocked it this way on friday morning, there was nothing disruptive, it was not that late and we were told there would be some slack on friday to compensate for the vUDS delays
[22:17] <ScottK> I told everyone I was blocking it at the time.
[22:17] <seb128> everyone who was on IRC at the time I guess
[22:17] <ScottK> It was blocked because ogra_ said things needing FFes could be uploaded safely since the queue was frozen (which wasn't and isn't the case)
[22:18] <ScottK> So I was _TOLD_ it needed an FFe.
[22:18] <seb128> ok, blame ogra_ then:
[22:18] <seb128> !
[22:18] <seb128> not sure where he got that from
[22:18] <ScottK> He was deeply confused.
[22:18] <seb128> we never queue bloqued for FF
[22:18] <ScottK> We straightened him out.
[22:18] <ScottK> Yep.
[22:19] <ScottK> He was mixing up Beta freeze and FF.
[22:47] <cjwatson> stgraber: cron> careful of ogra's temporary phablet hack, too
[22:50] <cjwatson> stgraber: Oh, did you figure out the Edubuntu/amd64 build problem?  What was it?
[23:06] <stgraber> cjwatson: no idea, just triggered a new build :)
[23:06] <stgraber> cjwatson: oh, actually it looks like it failed and just published an old livefs. I'll have to investigate then
[23:06] <stgraber> highvoltage: or you if you have more time than I do ^
[23:06] <highvoltage> ok
[23:07] <cjwatson> *something*'s installing the kernel one phase too early, but I couldn't quite see what
[23:07] <highvoltage> I can tomorrow afternoon (well, morning EDT)
[23:08] <highvoltage> hmm, that sounds familiar
[23:22]  * cjwatson hits it with set -x
[23:26] <cjwatson> no, wait, I've misunderstood something here
[23:29] <stgraber> cjwatson: hmm, did something recently changed in grub2? I had a very quick look at the build failure for Edubuntu and this matches another failure I've been told about in upgrade testing (when running under lxc though, so really not sure if that's the same problem)
[23:30] <cjwatson> No
[23:30] <cjwatson> And linux-image-extra-blah is installed at nearly exactly the same point in the (working) Ubuntu build
[23:31] <cjwatson> I wish I could remember my analysis of a similar problem before
[23:32] <cjwatson> First failed build was 20130221; there was a grub2 upload that day but it was later
[23:33] <cjwatson> So I think even circumstantial evidence rules out grub2 being the direct cause
[23:35] <cjwatson> Matches linux 3.8.0-6.14 -> 3.8.0-7.13 but there's nothing that looks relevant in its changelog
[23:37] <cjwatson> It might just be a configure ordering problem :-(
[23:38] <cjwatson> In at least two successful cases, grub-pc is configured after linux-image-extra-blah; in at least two failing cases, vice versa
[23:39] <cjwatson> And something caused the order to flip, but that could be practically anything and there's clearly an undefinedness problem anyway
[23:42] <stgraber> hmm, so much for quickly reading through grub's postinst, that thing is massive!
[23:43] <cjwatson> stgraber: I think perhaps http://paste.ubuntu.com/5606413/
[23:43] <cjwatson> That matches the postinst
[23:45] <cjwatson> And, although I haven't proven it directly, my argument is that matching the postinst should be good enough, because the postinst succeeded a bit earlier
[23:45] <stgraber> yeah, I think that'd make sense. It's just really weird that we haven't seen that problem earlier, I guess we've been lucky with the resolver on all the other images ;)
[23:46] <cjwatson> I'd be more comfortable with a better proof ...
[23:46] <cjwatson> But I think this is correct on its own merits anyway; we shouldn't be calling update-grub if there isn't already a grub.cfg to update
[23:54] <cjwatson> stgraber: OK, uploaded.  I decided to let it ride along with a merge I had queued up; the diff is fairly substantial but the actual effective change is pretty near minimal
[23:54] <cjwatson> And our delta is almost approaching sane now
[23:55] <cjwatson> (My goal is to eradicate it - I'm bored of merges)
[23:56] <cjwatson> stgraber: So, assuming I didn't screw it up and fail to build, could you unblock it at some point and try another build?
[23:57] <cjwatson> And with any luck we'll be back to all images building cleanly again
[23:58] <stgraber> cjwatson: yep, I'll push an hint once it's done building