[07:39] <elfy> infinity: keyboard stage working, still seeing no option to remove installation media, which davmor2 appears to see as an issue bug 1432285
[07:48] <flexiondotorg> Morning. Looks like the Ubuntu MATE image rebuilds have stalled.
[07:48] <oSoMoN> hi all, could someone ack the webbrowser-app sync to unblock it from the unapproved queue?
[07:49] <elfy> flexiondotorg: looks like 32and 64bit both failed to build - at ~7am
[07:50] <flexiondotorg> elfy, How do you know this?
[07:50] <elfy> http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-mate/vivid/
[07:50] <flexiondotorg> Thanks.
[07:51] <flexiondotorg> elfy, That is yesterday morning I think.
[07:52] <elfy> oh sorry - too early to read dates properly
[07:52] <flexiondotorg> http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-mate/vivid/daily-live-20150324.4.log
[07:52] <flexiondotorg> cjwatson, PLease take a look at ^^^^^^^^
[07:52] <flexiondotorg> cjwatson, Looks like something died.
[09:45] <cjwatson> flexiondotorg: it's not in any interesting way, it just got unlucky and the load on that machine was temporarily too high or something.  just retry the build when you see taht
[09:45] <cjwatson> *that
[09:46] <flexiondotorg> cjwatson, So, I did cancel and then request a build before I left for work.
[09:46] <infinity> Except that wedged the world a bit, so retrying won't work.
[09:46] <flexiondotorg> The POwerPC build has completed. The i386 and amd64 still report as building.
[09:46] <ogra_> infinity, can i have the livecd-rootfs above ? touch only ...
[09:46]  * infinity cancels a bunch harder.
[09:47] <flexiondotorg> infinity, Thanks.
[09:47] <infinity> ogra_: Yeah, I saw.  And WTF? :P
[09:47] <infinity> ogra_: Why do you need to explicitly install ubuntu-system-settings-online-accounts?
[09:47] <ogra_> infinity, there is an "or" dependency that gets resolved reverse ...
[09:47] <ogra_> thats a desparate try to fix this
[09:47] <infinity> And you can't just seed ubuntu-system-settings-online-accounts?
[09:48] <jamespage> bdmurray (or another SRU team member): please could the nova SRU for trusty be accepted into proposed? waiting on that to start verification testing.
[09:49] <Odd_Bloke> If an AA could take a look at promoting the cloud-inits waiting in {precise,trusty,utopic}-proposed, it would be much appreciated.
[09:53] <infinity> Odd_Bloke: Done.
[09:54] <Odd_Bloke> infinity: <3
[09:54] <ogra_> hmpf, if you said anything ... i had a reconnect ...
[09:55] <infinity> 03:47 < ogra_> infinity, there is an "or" dependency that gets resolved reverse ...
[09:55] <infinity> 03:47 < ogra_> thats a desparate try to fix this
[09:55] <infinity> 03:47 < infinity> And you can't just seed ubuntu-system-settings-online-accounts?
[09:55] <ogra_> infinity, it is seeded
 thats a desparate try to fix this
 Depends: libaccount-plugin-google | ubuntu-system-settings-online-accounts
 from account-plugin-google
[09:55] <infinity> adam_g: Have you considered being more consistent with who you commit as? :P
 we dont want the lib
 if you have any better suggestion i'm all ears :)
[09:56] <infinity>  Adam Gandelman <adam.gandelman@canonical.com>
[09:56] <infinity>  Adam Gandelman <adamg@canonical.com>
[09:56] <infinity> +Adam Gandelman <adamg@ubuntu.com>
[09:56] <infinity> ogra_: Find the seed where account-plugin-google is being pulled in, add ubuntu-system-settings-online-accounts to same seed, run germinate, see what happens?
[09:57] <infinity> ogra_: If the alternate dep is already satisfied, you shouldn't get both.
[10:00] <infinity> jamespage: I'm not sure to what level of scrutiny bdmurray has been reviewing these openstack point release uploads, so I might leave nova to him (plus, it's 4am, and my brain is wheeee), but if you can't get him to sort it for you tomorrow, lemme know.
[10:00] <jamespage> infinity, thanks
[10:03] <flexiondotorg> infinity, Please can you confirm if I should request Ubuntu MATE rebuilds?
[10:10] <infinity> flexiondotorg: They should be building.
[10:10] <flexiondotorg> infinity, Thank you.
[10:11] <infinity> flexiondotorg: Seems like "network hiccups after I rebuild the world and go to bed" is going to be a thing this week. :P
[10:11] <infinity> At least, it happened two nights in a row.  Less than pleased.
[10:11]  * flexiondotorg sends infinity sleep wishes
[11:27] <davmor2> jibel: vivid desktop if you open nautilus does it open a new icon in the launcher rather than the main icon?
[11:28] <jibel> davmor2, it does
[11:44] <jamespage> if any of the release team have time I've added another NEW package requirement to https://bugs.launchpad.net/ubuntu/+bug/1434526 that needs a review
[11:45] <jamespage> I also need an AA to review the NEW packages associated with that bug if there is anyone available that has some cycles; once those are in archive, I can upload the kilo-3 milestone release for openstack projects
[12:44] <ogra_> infinity, well, both packages are in the same seed since forever ...
[13:05] <infinity> ogra_: Bleh.  Well, try to find a better solution for it at some point, livecd-rootfs hacks suck.  But I'll let it in for now.
[13:05] <ogra_> infinity, it is only a test anyway
[13:05] <ogra_> i'm not sure it will fix it at all
[13:06] <ogra_> seb128, ^^^
[13:06] <seb128> ogra_, infinity, thanks
[13:08] <Riddell> kubuntu respin seems to have broken, can anyone diagnose? http://people.canonical.com/~ubuntu-archive/cd-build-logs/kubuntu/vivid/daily-live-20150325.log
[13:10] <cjwatson> Riddell: there was some work being done on the LP master database server, which seems to have caused slightly-odder-than-usual failure modes for things that caught it at the wrong time
[13:10] <cjwatson> Riddell: just retry
[13:11]  * Riddell retries
[14:08] <sil2100> Hello release team!
[14:09] <sil2100> We have published a new mir through the train just now
[14:10] <sil2100> The upstream developers have assured us that it's a bugfix only release
[14:11] <sil2100> Mir is also not really used on desktop images (besides desktop-next), so this should be a relatively safe upload - QA has signed it off and confirmed it's at least not causing any regressions on ubuntu-touch
[14:18] <cyphermox> have they also tested it wasn't regressing desktop-next?
[14:18] <cyphermox> (am not release team, just curious)
[14:23] <infinity> sil2100: It's on all the images, it's going to have to wait.
[14:25] <seb128> cyphermox, desktop-next doesn't do milestones or release so it doesn't matter much
[14:25] <seb128> it's a rolling testing image, not a production ready product
[14:28] <cyphermox> seb128: it would still be nice not avoid breaking it a bit, or to break it less :)
[14:28] <seb128> right, but that's freeze specific
[14:29] <seb128> +not
[14:29] <cyphermox> nope
[14:29] <cyphermox> seb128: since you're here, any news on the B word? :)
[14:29] <seb128> cyphermox, no, not for this cycle :-/
[14:30] <cyphermox> boo :(
[14:30] <ogra_> if you mean the same B word i would mean, ChickenCutlass is just playing woth the PPA
[14:30] <ogra_> *with
[14:30] <ogra_> trying to get it to work on the phone
[14:30] <cyphermox> ok, cool
[14:31] <cyphermox> he's building his own custom kernel?
[14:31] <seb128> cyphermox, speaking of which, I've a bug related which would be nice to look at
[14:31] <cyphermox> seb128: ok
[14:31] <infinity> Riddell: You around?
[14:33] <ogra_> cyphermox, ask him, i think he wanted to talk to you anyway about cmdline tools to use for testing
[14:33] <Riddell> hi infinity
[14:34] <cyphermox> ogra_: got it
[14:34] <infinity> Riddell: Hey.  Your images are marked "re-building" on the tracker, but I don't see them actually rebuilding.  Did you trigger rebuilds?
[14:34] <infinity> Riddell: If you did, the infra might have gotten wedged, I can fix that for you.
[14:34] <Riddell> infinity: yep, then cjwatson said there was a problem and I should try it again so I did
[14:35] <Riddell> infinity: fixes welcome :)
[14:35] <infinity> Riddell: I'll smack it around a bit.
[14:35] <infinity> Riddell: Smack in progress.
[15:10] <jibel> cyphermox, bug 1432285 is high importance and something to fix ASAP. The user cannot eject the CD is trapped in an install loop
[15:12] <cyphermox> jibel: I know, working on it
[15:12] <infinity> jibel: He's on it.
[15:12] <infinity> See? :P
[15:12] <infinity> jibel: The tracker seems pretty devoid of other interesting looking bugs.  Have you found any other showstoppers that I'm not seeing?
[15:18] <jibel> infinity, that's the only one if we don't count the fact that I cannot do any successful installation in a VM. Tried qemu and vbox.
[15:18] <jibel> but HW is ok
[15:19] <infinity> jibel: Really?
[15:19] <infinity> jibel: desktop, server, or both?
[15:19] <infinity> jibel: I did a server install in a VM just last night.
[15:19] <jibel> infinity, desktop
[15:19] <infinity> Fun. :/
[15:19] <infinity> Lemme kvm up a desktop install and see WTF.
[15:19] <cyphermox> it was working for me yesterday in qemu
[15:20] <jibel> there is no live session on i386 qemu bios mode
[15:20] <cyphermox> ok
[15:20] <jibel> and amd64 doesn't boot after installation in bios and uefi
[15:20] <infinity> That all sounds rather sketchy.
[15:21] <infinity> I did have an issue where my server VM hung on reboot once or twice, but it was happening so early that I blamed qemu, not the image.
[15:21] <infinity> After I killed it, it booted fine.
[15:22]  * infinity grabs fresh ISOs to give them all a once-over in a bit.
[15:29]  * infinity grabs fresh ISOs veeeeeery slowly.
[15:46] <infinity> seb128: Ahh, does that fix the lack of icon reuse?
[15:47] <seb128> infinity, for upgraders yes, for new install we need https://code.launchpad.net/~seb128/unity/nautilus-desktop-rename/+merge/254103
[15:48] <cyphermox> ah, perhaps the jenkins issues got current to not get updated
[15:48] <infinity> seb128: Ahh, kay, so can't be entirely fixed for beta, that's fine.  If it'll be fixed later, that works for me. :)
[15:48] <seb128> right
[15:48] <seb128> sorry about that
[15:48] <infinity> seb128: Sorry for fixing bugs?  Have you turned Canadian when I wasn't looking?
[15:48] <seb128> lol
[15:48] <cyphermox> lol
[15:49] <cyphermox> french canadian is teh worst.
[15:49] <infinity> No argument here.
[15:49] <cyphermox> ;)
[15:49] <infinity> Quebec and Vermont need to split off and form some logging and maple syrup powerhouse.
[15:50] <jibel> infinity, what is the difference between ubuntu desktop 20150325 and 20150324?
[15:50] <infinity> Nothing but flannel and bad accents as far as the eye can see.
[15:50] <infinity> jibel: 20150325 sucks less.
[15:50] <cyphermox> infinity: only if there are no huge maple syrup heists again.
[15:50] <jibel> infinity, sucks less but didn't migrate from pending to current :/
[15:50] <infinity> Riddell: ^ There you go.
[15:50] <Riddell> thanks infinity
[15:50] <infinity> jibel: Yeah, the pending/current thing may have broken due to network hiccups and such.
[15:51] <infinity> That machinery is mostly a black box to me.
[15:52] <infinity> stgraber: Do you know how the pending/current stuff on cdimage works, and how to make it happy (or check why it's not)?
[15:55] <cyphermox> it depends on smoketests in jenkins, no?
[15:55]  * cyphermox looks
[15:57] <cyphermox> brb
[15:57] <jibel> yeah, jenkins job broke because of some networking issue and the node it runs on is offline
[16:00] <jibel> cyphermox, discussing with CI
[16:02] <cyphermox> ok
[16:25] <jamespage> slangasek, would you have archive-admin time to review three new oslo packages to unblock openstack kilo-3 entry into the archive?
[16:27] <jibel> infinity, cyphermox desktop amd64 migrated from pending to current, but i386 didn't. re-re-retrying
[16:28] <infinity> jamespage: He's on vacation this week.
[16:29] <infinity> jamespage: That said, if any openstack stuff is on ISOs, it'll have to wait until after tomorrow anyway.
[16:29] <jamespage> infinity, its not
[16:30] <infinity> None at all?
[16:31] <jamespage> infinity, none of the 29 I need to touch for kilo-3
[16:31] <infinity> Heh.
[16:31] <jamespage> that's not what I said :-)
[16:31] <infinity> jamespage: I'll look at these two when I get a chance.
[16:31] <jamespage> infinity, am I OK to upload the third to the NEW queue as well please?
[16:31] <infinity> jamespage: What's the deal with the "openstack" package?  Just some convenience metapackages?
[16:32] <jamespage> infinity, I honestly don't know
[16:32] <jamespage> I should but I don't
[16:32] <infinity> confidence++
[16:32] <jamespage> I think its the 'openstack installer' - lemme check to stokachu
[16:32] <jamespage> infinity, its not something that comes from my team at least
[16:32] <stokachu> it's the installer
[16:32] <infinity> jamespage: And yes, upload the other NEW thing you have.  I'd rather do them all at once if they're similar, since the bugs will likely also be similar.
[16:33] <jamespage> infinity, indeed
[16:34] <jamespage> infinity, OK - uploaded - they all prefix 'python-oslo.'
[16:34] <jamespage> infinity, thankyou
[16:35] <infinity> jamespage: Are any of these renames of existing things, or are they all entirely new?
[16:35] <jamespage> infinity, entirely new packages, but refactoring of shared common openstack code into python modules
[16:36] <infinity> jamespage: Righto.
[16:36] <infinity> jamespage: Grabbing an early lunch, then I'll review those while I'm playing with beta ISOs.
[16:36] <jamespage> ta
[16:52] <jibel> desktop i386 migrated too, finally
[17:11] <flexiondotorg> Anyone seen an issue when try to install 15.05 on a system that already has btrfs partitions?
[17:12] <ianorlin> flexiondotorg: are you trying to resize them
[17:12] <ianorlin> I found an issue that you couldn't back in utopic
[17:12] <flexiondotorg> ianorlin, Nope. Ubiquity hangs before you see any user prompts. Timeout while kernel waits.
[17:12] <ianorlin> arhg that isn't good
[17:13] <flexiondotorg> ianorlin, http://i.imgur.com/NERrzov.png
[17:13] <flexiondotorg> Trying to create a reproducible test.
[18:00] <ianorlin> flexiondotorg: what kind of graphics do you have in that machine ?
[18:00] <stgraber> infinity: I vaguely remember jenkins having a restricted ssh access to nusakan and calling some bin/ script to flip the switch, but that's about as much as I know
[18:02] <infinity> stgraber: Kay, I think you know about as much as I do about it.
[18:03] <infinity> stgraber: :)
[20:46] <infinity> cyphermox: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1436497 sound less than ideal.
[20:48] <cyphermox> yuck
[20:51] <infinity> cyphermox: Still not seeing any particularly dire bugs reported, though, which is nice.  A few that are definitely RC for final, but nothing really beta-critical.
[20:51] <cyphermox> yep
[20:51] <infinity> Except maybe the CD eject bug, if people get stuck in a loop and have to go look for a paperclip. :P
[20:51] <elfy> infinity: is anything likely to happen re the eject bug? that is - rebuilds?
[20:51] <cyphermox> well, not really
[20:52] <cyphermox> while you boot you can eject the CD
[20:52] <cyphermox> and I bet when you're at the grub menu you also could
[20:52] <infinity> elfy: If it can be fixed by cyphermox soon (very soon), I'd consider a respin for it, but time's running out on it being worth caring about, I think.
[20:52] <cyphermox> it's trickier and not super friendly, but still
[20:52] <cyphermox> nah, still just tracking it down
[20:53] <cyphermox> I think it's because we now call some systemd restart magic so it happily skips everything else.
[20:53] <infinity> elfy: Definitely an RC bug for final, but not sure it's worth holding the beta up for.
[20:53] <elfy> infinity: thanks - just needed to know what was likely to happen between now and tomorrow PM
[20:54] <infinity> cyphermox: Oh, indeed.  The whole shutdown sequence has been mangled.
[20:55] <infinity> cyphermox: Not sure if casper/ubiquity/misc has changed at all to take any of that into account.
[20:55] <cyphermox> nope
[20:55] <infinity> I suspect the answer is "no".
[20:55] <infinity> Yeah.
[20:55] <infinity> So, this might be intractable for beta, cause it might be a rewrite of some bits, not a quick fix.
[20:55] <infinity> Unless there's just somewhere we can poop a .service file that papers over it for now.
[20:56] <cyphermox> well, I'm going to see. When do you give me until?
[20:56] <cyphermox> I was going to try to fit in a .service just now
[20:56] <cyphermox> (or you know, at least start with trying that out on my system)
[20:57] <infinity> cyphermox: Well, I'm comfy with releasing up to midnight my time tomorrow.  Which probably means respins, if we have any, would need to happen overnight our time, so there's enough time to smoketest, push to mirrors, etc during the day tomorrow.
[20:57] <infinity> cyphermox: So, if you can some up with something workable in the next 5 or 6 hours?  If you're keen on fixing this.
[20:57] <cyphermox> yeah
[20:57] <infinity> s/some/come/
[20:57] <cyphermox> I'll give you an answer of whether it's an easy fix or not within the next two hours?
[20:58] <cyphermox> I bet the kubuntu inhibit-polkit issue is also something similar
[20:58] <infinity> cyphermox: Works for me.
[20:59] <infinity> The kubuntu thing looks like systemd mounting new things that weren't mounted before, yeah.  And ubiquity being entirely unsure how to deal with that.
[20:59] <ianorlin> I think fixing bug  1424362 may fix bug 1429531 as well and the to get it to work is just starting libpolkit-backend-1-0
[20:59] <infinity> I miss upstart.  I never thought I'd say that.
[21:00] <cyphermox> haha
[21:04] <infinity> ianorlin: Absolutely agree that should be fixed.  Not sure today's the right day to fix it, when it's been known about for a month, but if the Lubuntu folks want to push a fix and retest, they're welcome to.
[21:49] <doko> infinity, accepted the gccgo-5 package dancing with sagari. will be blocked anyway
[21:49] <infinity> doko: Mmkay.
[23:11] <ianorlin> bdmurray: for lubuntu gnome-settings-daemon would be correct package for no pointer showing up but you said it should have its own bug but I reported wrong place but can fix that
[23:13] <bdmurray> ianorlin: I said an issue with the pointer not appearing after an upgrade is different than one after a fresh install or on a live CD.
[23:14] <ianorlin> bdmurray I know I reported bug 1436509 and think I might have misfiled it at first which seems to be the same issue