[02:04] <slangasek> infinity: ok - not really in a position to add the hint for bash now, could you add it when you get a chance?  (or else I'll try to get it later)
[02:18] <infinity> slangasek: Unless I get a lightdm fix, I'm not seeing massive arguments to respin anyway (respinning for security fixes that we can just release 5m after the images publish isn't worth it)
[02:19] <infinity> slangasek: So, we'll see what people come up with for lightdm later tonight.
[05:52] <slangasek> infinity: is that an argument for not accepting them in?  I don't follow
[05:57] <mdeslaur> there's going to be another bash update in the next few hours, FWIW
[06:04] <infinity> slangasek: No, more just an "if you were accepting it to get it on the images, it might not do so".
[06:05] <slangasek> right, I don't care about the images which are always out of date the instant they arrive :)
[07:23] <mlankhorst> infinity: hey should mesa be moved to main?
[07:23] <infinity> mlankhorst: By "main", do you mean release?
[07:23] <mlankhorst> yeah
[07:24] <infinity> At some point, yes.
[07:24] <mlankhorst> ok
[07:57] <jamespage> Laney: morning
[07:58] <jamespage> Laney: going back to our xstatic conversation last week, would it be more paletable for horizon to re-bundle the xstatic dependencies its split out for this cycle? thus avoiding lots of delta with Debian and minimizing the security footprint of Horizon JS dependencies in Ubuntu main
[08:09] <jibel> jodh, good morning, seb128 assigned bug 1371651 to you. Are you actively looking at it? Is there more information I can provide?
[08:09] <ubot2> bug 1371651 in lightdm (Ubuntu) "Daily does not boot into graphical interface after installation" [Critical,Triaged] https://launchpad.net/bugs/1371651
[08:44] <Riddell> kubuntu plasma 5 isn't on the iso tracker for beta 2, can someone remind me how to add it?
[08:53] <Riddell> syslinux still has no option for OEM and a random "back" entry
[10:29] <jodh> jibel: Just updated the bug. I'm not seeing the issue with 20140923. Do you?
[10:31] <jibel> jodh, I reproduced with 20140923. It's easier to reproduce with vbox than qemu. On qemu it happens once every 5 boots or so
[10:31] <jodh> jibel: sounds like a kernel issue then. I don't believe it's upstart that's the problem here.
[10:32] <jodh> jibel: can you reproduce on amd64?
[10:33] <jodh> jibel: the bug has been tagged amd64 but nobody seems to have seen the problem on amd64 right?
[10:33] <cjwatson> Riddell: yeah, I see I've just been handed a critical bug for that, I've been meaning to poke at that :-/
[10:33] <jodh> jibel: oh I see, elfy presumably has seen it on amd64.
[10:33] <jibel> jodh, let me try on amd64
[10:44] <jibel> jodh, same problem on amd64
[10:45] <jodh> jibel: can we get a list of packages that have changed between the 2014-09-19 image and the previous one?
[10:46] <jodh> jibel: doing a reboot loop to try to recreate atm...
[10:57] <jodh> jibel: just updated the bug. can you recreate if "quiet splash" is not specified in /etc/default/grub ?
[11:01] <jibel> jodh, without "quiet splash" lightdm always starts. tried on 5 boots
[11:02] <jodh> jibel: that's what I'm seeing. I tried a lot more boots too. So that suggests it's a kernel issue.
[11:11] <Laney> jamespage: It might be - would that avoid the need for all of the xstatic deltas?
[11:11] <Laney> Sorry for the slow reply
[11:11] <Laney> I'd still prefer a second opinion. :)
[11:11] <jamespage> Laney: yes it would
[11:12] <jibel> apw, can you help on bug 1371651 ?
[11:12] <ubot2> bug 1371651 in lightdm (Ubuntu) "Daily does not boot into graphical interface after installation" [Critical,Triaged] https://launchpad.net/bugs/1371651
[11:12] <Laney> I find the "re-bundle because we don't want to offer full security support" to be a bit uncomfortable
[11:13] <Laney> like we've got your back if you use the libraries through xstatic but not directly
[11:13] <Laney> but I could be out of whack on this hence asking for someone else to think
[11:18] <jamespage> Laney: did you see jdstrand's comment last week?
[11:19] <Laney> Yeah
[11:20] <jamespage> Laney: so essential what we're doing by bundling all of the xstatic bits in horizon is maintaining the status-quo
[11:20] <jamespage> as in that's exactly what horizon upstream where doing last cycle
[11:36] <rtg> can someone please approve linux 3.16.0-18.25 in the Utopic queue ?
[11:45] <cyphermox> could someone please review and release wpa? it's an important fix for roaming issues
[12:13] <elfy> jodh: yea - definitely seen it on both 32 and 64 bit assuming you're talking about 137165, one of the xubuntu testers first found it on the 19th October Daily
[12:14] <elfy> and without quiet splash I still had the same issue
[12:20] <elfy> jodh: to confirm that last - in vb 64bit without quiet splash - it drops to tty1 on boot
[12:21] <elfy> service lightdm status = stop/waiting
[12:31] <jodh> elfy: ok, please could you capture that detail on the bug?
[12:34] <elfy> added the stop/waiting - but I did say I was landing at tty1 in comment at the beginning of the week
[12:34] <elfy> bbl
[12:50] <jdstrand> Laney: fyi, I looked at the new horizon approach from jamespage. security team is ok with it (since, as mentioned, it is the status quo wrt support)
[13:39] <Laney> jdstrand: Seems okay to me if you guys are happy with that
[13:40] <jdstrand> Laney: well, it is hard to be happy about embedded code copies, however, it is maintaining the status quo and we already had this discussion in the horizon MIR several cycles ago
[13:44] <Laney> Well, indeed, embedded code copies was my original unhappiness
[13:44] <Laney> It's relative... :)
[13:46] <jodh> jibel: any news from the kernel team?
[13:47] <jibel> jodh, no.
[13:47] <jibel> apw, around?
[13:47] <jodh> jibel: how about trying a problematic image with an older kernel to see if it's recreatable?
[13:51] <arges> cjwatson: the bash security update (4.3-9ubuntu2) seems to be stuck in proposed.
[14:07] <cjwatson> arges: up to infinity whether to unblock it, as he's driving the final beta
[14:14] <ogra_> infinity, drive faster !
[14:14]  * ogra_ needs the hud from unapproved :P
[14:14] <zequence2> In case anyone wonders, Ubuntu Studio testing for the i386 will be finished no later than about 2h from. Hope that's cool with everyone.
[14:15] <zequence2> 2h from now, that is
[14:16] <apw> jibel, i am looking at that now, do i see you saying that after install on reboot (on kvm) it will occur one in 5 as well?
[14:18] <jibel> jibel, yes approximately on kvm it's reproducible 20% of the time, on vbox it's 100%.
[14:19] <apw> jibel, that seems likley to turn out to be two different issues; but we shall see
[14:20] <jibel> apw, ok, for the moment i'd like to understand the scope and impact of the problem to know if it's a ship-stopper for beta 2 or not
[14:20] <apw> jibel, yep, working on that, when you have it in vbox what is the frambuffer normally called for that
[14:24] <jibel> apw, how do I know?
[14:24] <apw> lsmod | grep fb perhaps
[14:27] <jibel> apw, this command returns nothing, but dmesg tells, vesafb and it uses fb0
[14:30] <apw> vesafb that seems reasonable, and available as far as i can see... odd
[14:32] <infinity> jibel: If it's only happening in VMs, I'm inclined to not call it a ship-stopper.
[14:33] <infinity> jibel: (I was hoping a fix would be sorted out by now, but I don't see it worth delaying the beta by a day or more)
[14:43] <infinity> apw: The lack of vesa in lsmod would be because of CONFIG_FB_VESA=y
[14:43] <infinity> (Was that always true?  I could have sworn it used to be a module)
[14:45] <ogra_> yeah, it used to be
[14:51] <cjwatson> we've gone back and forward on that iirc
[15:04] <infinity> jibel: Can we generally confirm that this lightdm/fb/plymouth/whatever issue doesn't seem to happen on real hardware?
[15:04] <infinity> jibel: If it's limited to VMs, I'm inclined to not care for B2, and then hunt people down to make sure it's fixed ASAP afterward, since it affects testing.
[15:06] <jibel> infinity, I didn't see any report on HW and didn't reproduce on HW either, nor omer. So it seems limited to VMs and affecting vbox more than others.
[15:07] <jibel> infinity, the workaround is simple, press esc on boot to display the boot menu or remove "quiet splash" or start lightdm manually
[15:07] <infinity> jibel: Right, I care about virtualbox very little, free desktop VMs a bit more (because of testers), and server VMs a lot more, who aren't affected.
[15:08] <infinity> jibel: elfy claimed he could reproduce even without quite/splash, which seemed a bit sketchy.
[15:08] <infinity> jibel: But either way, if it's only VMs, it's not a blocker for me.
[15:08] <arges> infinity: according to the bug report it also affects KVM VMs
[15:09] <jibel> infinity, on another topic, what's your opinion on the lack of OEM option in the boot menu?
[15:09] <jibel> infinity, bug 1334189
[15:09] <ubot2> bug 1334189 in gfxboot-theme-ubuntu (Ubuntu) "pre-boot menu offers no OEM mode on Utopic live images" [Critical,Confirmed] https://launchpad.net/bugs/1334189
[15:10] <infinity> jibel: Again not a beta blocker, but seems like a regression we should want fixed.
[15:10] <cjwatson> I intend to fix that, there's just only one of me :)
[15:11] <infinity> cjwatson: Hire that Evan guy.
[15:14] <jamespage> Laney, jdstrand: ^^ horizon as we discussed; I'll deal with the sync request FFe's now
[15:15] <Laney> Ta
[15:15] <jdstrand> nice!
[15:15] <Laney> I'll leave it to be flushed out after beta if you don't mind
[15:16] <jdstrand> fyi, apparmor upload is to fix a small policy bug and more importantly updates the lxc Breaks version
[15:38] <jamespage> Laney: fine - its not on any of the images...
[15:39] <Laney> ah, even better, then the auto accept script should do it
[15:40]  * Laney looks suspiciously at it
[15:47] <elfy> infinity: it doesn't matter what I do - unless I'm either booting with systemd or manually starting lightdm - it doesn't work here
[15:47] <Laney> Oh
[15:47] <Laney> It's doing an 'is this in any packageset?' check too
[15:48] <Laney> Is that useful in addition to seeded-in-ubuntu?
[15:50] <elfy> infinity: and what did you mean by sketchy?
[15:59] <jamespage> Laney: its seeded in the server-supported seed
[15:59] <jamespage> so won't auto-accept
[16:00] <Laney> I thought auto-accept was accepting everything not on images
[16:01] <jamespage> Laney: that would be nice :-) but I don't think that's the case
[16:01] <jamespage> Laney: have neutron in the queue as well - same situation
[16:04] <infinity> Laney: No.
[16:04] <infinity> Laney: auto-accept is meant to be "the stuff people probably don't care about specifically", hence !packagesets.
[16:07] <Laney> Why does the release team care that I care about pinta?
[16:09] <infinity> Laney: It's a rough guess, erring on the side of caution.
[16:09] <infinity> Laney: Generally, if someone cared enough to add something to a packageset, they should care enough to give it an extra level of review before release.
[16:13] <arges> infinity: hey. can you approve the bash update 4.3-9ubuntu2 ? it has that security fix and seems to be held in -proposed
[16:13] <Riddell> infinity: do you know how I can get Kubuntu Plasma 5 on the beta2 iso testing page?
[16:14] <infinity> Riddell: Ask stgraber nicely, the ISO tracker is a mystery to me.
[16:14]  * Riddell bats eyelids at stgraber 
[16:14] <infinity> arges: There's another upload coming anyway, but we can let it through if people are panicking about their unsupported development system having a security bug for a day.
[16:14] <Riddell> anyway, beta 2 is good for kubuntu and kubuntu-plasma5
[16:15] <infinity> Riddell: Oh, hrm, I never built plasma5 images, I guess you were testing the previous day's dailies.
[16:15] <infinity> Riddell: I suppose the only major change there was a kernel bump, if you're happy with what you tested, meh.
[16:16] <Riddell> I didn't notice any problems, anything specific in that kernel bump?
[16:16] <infinity> Riddell: Just your usual march of kernel uploady progress.
[16:16] <stgraber> Riddell: I suspect it's just not on the manifest, let me check
[16:17] <stgraber> hmm, no, it is...
[16:17] <infinity> stgraber: It could be on the manifest, but since I never rebuilt the images, it never would have landed.
[16:17] <infinity> ie: All my fault.
[16:17] <stgraber> infinity: ah, yeah, that'd certainly explain it :)
[16:17] <infinity> (I didn't realise plasma5 was in the releasy set)
[16:17] <stgraber> Riddell: blame infinity :)
[16:18]  * infinity feels adequately blamed.
[16:18]  * Riddell finds himself in a maze of twisty blame corridors all alike
[16:18] <infinity> Riddell: So I'm well-informed for next month, do you intend to *release* -plasma5 as well, or were you just doing milestones to keep tabs on progress?
[16:20] <Riddell> infinity: yes we'd like a release
[16:20] <infinity> Riddell: Alright, good to know. :)
[16:20] <Riddell> we will but appropriately large "tech preview, don't expect any suport" labels all over it
[16:23] <wxl> infinity arges is this for 14.10?
[16:23] <infinity> wxl: "this"?
[16:23] <infinity> wxl: Oh, bash?  Yeah.
[16:24] <wxl> infinity: yep, cool, thx. :)
[16:24] <stgraber> Riddell: do you want to release the current image (September 22)? if so, I can copy that over to beta-2
[16:25] <Riddell> stgraber: yeah
[16:25] <stgraber> infinity: note that the naming of the plasma 5 image makes publish-image-set very unhappy (either it'll refuse to print you anything or it'll just crash)
[16:25] <infinity> stgraber: You didn't fix that when doing B1?
[16:26] <infinity> stgraber: I'll fix it when it explodes, then.
[16:26] <arges> wxl: yea
[16:27] <wxl> infinity arges is there a bug related to this that i can watch?
[16:29] <infinity> Oddly enough, I don't see one.
[16:29] <wxl> arges: sounds like you got a job to do :) ^
[16:29] <infinity> Oh, but this is the bug for the new upload that hasn't happened: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1373781
[16:29] <ubot2> Launchpad bug 1373781 in bash (Ubuntu) "bash incomplete fix for CVE-2014-6271" [Undecided,Confirmed]
[16:30] <infinity> wxl: Not sure how that would be arges's job.
[16:30]  * arges is googling for the CVE it exists somewhere
[16:30] <wxl> infinity: he brought attentiopn to it, so ;)
[16:31] <arges> https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1373688
[16:31] <ubot2> Launchpad bug 1373688 in bash (Ubuntu) "Bash Code Injection Vulnerability via Specially Crafted Environment Variables" [Undecided,Fix released]
[16:31] <infinity> wxl: Yeah, I think mdeslaur must have slipped him something under the table.
[16:31] <arges> wxl: ^^
[16:31] <wxl> heheheh
[16:31] <wxl> thanks guys!
[16:32] <stgraber> infinity: no, I just did things manually for beta-1
[16:32] <stgraber> infinity: I didn't find a good way to fix the script because the problem is that the product name is just wrong :)
[16:33] <infinity> stgraber: Which?  kubuntu-plasma5, or some pretty name?
[16:33] <stgraber> infinity: I can quickly fix it now though. We need to rename the product on the tracker from "Kubuntu Plasma 5 <arch>" to "Kubuntu Plasma 5 Desktop <arch>" so it matches our regexp a bit better, then update the list on cdimage to match and then add it to the regexp in the script
[16:34] <infinity> stgraber: Ahh, so the silly pretty names.  Check.
[16:34] <stgraber> yeah
[16:34] <infinity> stgraber: If you know what needs fixing, please fix so it's not a panick in a month.
[16:34] <infinity> Or a panic.
[16:35] <stgraber> doing
[16:39] <stgraber> Riddell: go file some results :)
[16:40] <stgraber> tracker and nusakan updated for the name fix, now looking at ubuntu-archive-tools
[16:41] <stgraber> Riddell: I'm going to mark plasma-5 ready for a few minutes so I can test my fix
[16:41] <Riddell> stgraber: it's ready, I'm done testing
[16:42] <Riddell> so just keep it marked ready
[16:42] <stgraber> ok
[16:43] <stgraber> infinity: publish-image-set fixed and tested
[16:44] <infinity> Shiny.
[16:45] <stgraber> infinity: oh, and one thing I've been working on lately is making sure we've got two contacts for each product on http://iso.qa.ubuntu.com/qatracker/series/43/manifest, I suspect there are a bunch more (Canonical flavors) that need updating, let me know if you see some of those and know who should be the right sign-off contacts
[16:45] <stgraber> that should save us some time on release week too
[16:46] <stgraber> looking at it, I think we need some updates to netboot, desktop, core and server
[16:46] <infinity> stgraber: Well, netboot/armhf has a contact that no longer works for us, nor is involved in the community. ;)
[16:46] <stgraber> zequence: do you have any fallback contact for ubuntu studio sign-off when you're not around?
[16:47] <infinity> stgraber: core is a joke, and I can always test and sign off on all of them.
[16:47] <infinity> stgraber: And netboot, despite being in the "manifest" isn't something we'd ever not ship.
[16:47] <stgraber> infinity: yeah, netboot is basically, we need someone to confirm that d-i isn't busted in the archive (out of sync with kernels or the like)
[16:47] <infinity> stgraber: (ie: it's a mistake based on misunderstanding of other people that it was ever in a go/no-go ship manifest)
[16:48] <infinity> stgraber: Anyhow, I think it's realistic to make the responsible parties for netboot be the usual d-i upload suspects.
[16:48] <stgraber> but yeah, we can't not release it, but it's something we need to confirm is good before we release, so might as well be on the checklist
[16:49] <infinity> stgraber: We can hunt down QA people for answers on what they've tested, but ultimately it'd be me, Colin, et al who make the call if it's busted or not.
[16:49] <infinity> stgraber: It was always a complete fiction that the other people listed there were in any way signing off on it. :P
[16:49] <stgraber> infinity: ok, so I'll update all of core to be you and Steve as a fallback and all of the netboot to be you and Colin as fallback
[16:50] <infinity> stgraber: For bonus points, can those names be hyperlinks to LP accounts, in case someone's not on IRC and I want to throw email at them?
[16:51] <infinity> A hypothetical me, there, I think *I* know how to email everyone on that list, but I doubt that's universally true.
[16:51] <stgraber> infinity: maybe, I don't know if I do any kind of html stripping in that field :)
[16:52] <zequence> stgraber: Not currently, no
[16:54] <stgraber> zequence: is that something you think you can change or do you really want to be the only one in control of studio sign-off for release?
[16:55] <stgraber> willcooke: hey there, I assume you're the new sign-off for Ubuntu Desktop, can you nominate a fallback too?
[16:55] <willcooke> stgraber, seb128 is the natural choice
[16:55] <stgraber> willcooke: ok, thanks
[16:55] <willcooke> np
[16:56] <stgraber> jamespage: heya, you're the current sign-off for Ubuntu Server. Is that still accurate? if so, I'd need the name for a fallback, if that's not accurate, I'll need two names :)
[16:57] <infinity> Dangit, have we still not killed amd64+mac server images?
[16:57] <jamespage> stgraber, smoser, gaughen or me
[16:57] <infinity> We should do that.
[16:57] <jamespage> stgraber, that covers most timezones
[16:57] <jamespage> apart from apac
[16:58] <infinity> jamespage: We're civilised people who would never release at, say, midnight Hawaii time, so you're safe.
[16:58]  * infinity whistles.
[16:58] <stgraber> jamespage: ok, I'll like gaughen / smoser / jamespage for the contact order, that matches what we do for the other Canonical flavors (manager / techlead / timezone fallback) :)
[16:58] <Laney> TZ=Pacific/Johnston mutt
[16:58] <stgraber> hmm, not sure what my brain was doing there :)
[16:58] <stgraber> s/like/put/
[16:58] <Laney> that was my mutt invocation for alpha 2
[16:59] <gaughen> works for me stgraber
[17:00] <stgraber> infinity: there we go, the manifest is now all shiny. The only SPOF we have there is zequence, hopefully he'll find a fallback soon or will make sure to stay awake for the whole release day :)
[17:01] <infinity> Laney: I did one on Honolulu time, which is the same thing, apparently. ;)
[17:01] <infinity> stgraber: I have every confidence in zequence not letting us down.
[17:02] <infinity> zequence: Please avoid crossing streets anywhere near busses.
[17:12] <zequence> I'm probably too crazy in traffic to be trusted with this responsibility
[17:22] <jdstrand> where are the release notes for utopic? I looked here https://wiki.ubuntu.com/UtopicUnicorn/ReleaseNotes (doesn't exist) and https://wiki.ubuntu.com/Releases (no link)
[17:23] <stgraber> beta 2 is usually the first milestone to ship using the central release notes page, so my guess is that nobody created it yet
[17:24] <jdstrand> i see
[17:27] <infinity> jdstrand: did you just volunteer?
[17:27] <jdstrand> I can
[17:28] <infinity> jdstrand: (Not astually as hard as it sounds, copy and paste from Trusty, empty 99% of it out, add the two things you cared about, done)
[17:28] <jdstrand> yeah, that is what I figured
[17:28] <infinity> jdstrand: I'd love the help, if you'd like to be helpful. :)
[17:28] <jdstrand> sure, I'll do it
[17:28] <infinity> \o/
[17:28] <jdstrand> it is almost the least I could do
[17:29] <infinity> I shall go find breakfast, or whatever meal it is when you haven't slept since yesterday morning.
[17:34] <mdeslaur> infinity: crack an egg into a red bull
[17:35] <infinity> mdeslaur: That sounds like death in a cup.
[17:37] <mdeslaur> infinity: make sure your will is up-to-date
[17:38]  * ogra_ wonders when ben collins managed to conquer mdeslaur's IRC nick
[17:38] <ogra_> ah, wait, that would be an egg in redbull inside a beer
[17:39] <mdeslaur> oh wow, people actually do that?
[17:39] <mdeslaur> without having a heart attack?
[17:39] <ogra_> ben does the most dangerous combos, yeah
[17:40] <ogra_> you might get a heart attack, but since you also get a blackout you wont remember ... so no worries
[17:41] <mdeslaur> lol
[17:57] <jdstrand> infinity: ok, https://wiki.ubuntu.com/UtopicUnicorn/ReleaseNotes and https://wiki.ubuntu.com/UtopicUnicorn/ReleaseNotes points to it
[17:57] <jdstrand> meh
[17:57] <jdstrand> infinity: https://wiki.ubuntu.com/Releases points to it
[17:57] <infinity> \o/
[17:59] <infinity> I'm going to watch some breakfast while I eat my TV, and then give that a once-over while I wait for a bit more testing to roll in, then we should be releasy soonish.
[18:03] <zequence> Had a corrupted iso before, which held me back a  bit. I should be ready within an hour with the last Studio testing
[18:04] <elfy> zequence: you want me to do anything?
[18:05] <elfy> not doing anymore xubuntu stuff at this stage
[18:08] <zequence> elfy: That's ok. I'm just about to test the final iso
[18:12] <elfy> ok
[18:17] <elfy> infinity: so I assume Mark as Ready - even though the lightdm/or whatever in vm issue
[18:25] <infinity> elfy: Yeah, we're going to ignore that issue and fix it ASAP after the beta.
[18:29] <elfy> infinity: okey doke
[18:48] <zequence> stgraber: No one else is currently both active and even faintly knowledgable, but I do agree that it would be good if there were someone who could step in
[18:49] <zequence> Anyway, I'm finally done testing.
[19:20] <bdmurray> Could an SRU team member look at releasing aptdaemon in trusty - bug 1324833?
[19:20] <ubot2> bug 1324833 in aptdaemon (Ubuntu Trusty) "crash handler does not include package version" [High,Fix committed] https://launchpad.net/bugs/1324833
[19:29] <bdmurray> arges: maybe you could look at releasing aptdaemon to trusty-updates?
[19:29] <arges> bdmurray: sure one second
[19:35] <arges> bdmurray: ok done.
[19:37] <jibel> infinity, apart the broken boot menu, the plymouth issue and a network driver issue, ubuntu desktop looks okay-ish.
[19:37] <jibel> network driver on mac only
[19:44] <infinity> Network driver issue?  I missed that one.
[19:49] <jibel> infinity, dave had problems installing bcmwl
[19:51] <infinity> wxl: How's lubuntu looking?
[19:51] <davmor2> infinity: on mac I select 3rd party drivers but get no wifi post install
[19:52] <infinity> davmor2: Fun.  Kay.  Didn't see a bug linked from the tracker for that.  I assume you filed one, though?
[19:52] <wxl> infinity: gimme a sec it's been a busy day :/
[19:52] <davmor2> infinity: no was confirming it with another install filing it now, I'm assuming it is ubiquity right?
[19:54] <infinity> davmor2: Probably not, but that'll do for a placeholder while we try to decide who's really at fault.
[19:54] <infinity> davmor2: Please grab installer logs, etc, since we might be debugging blind.
[19:56] <wxl> infinity: are we calling things confirmed despite https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1371651 ? :)
[19:56] <ubot2> Launchpad bug 1371651 in plymouth (Ubuntu) "Daily does not boot into graphical interface after installation" [Critical,Triaged]
[19:56] <wxl> s/confirmed/ready/
[19:57] <jibel> wxl, yes, we'll ignore it this time and fix ASAP after beta
[19:57] <elfy> apw: just tried the ppa for that - not working for me here - commented in bug
[20:01] <wxl> so i'd like to ask someone's advice on this: i have a couple partially tested images that worked fine for beta 1. should i call them good? apparently we had plenty of ppc testers but not so much elsewhere :( speaking of ppc, it doesn't boot on 32 and is untested from what i know on 64, so i'm not calling it ready
[20:01] <infinity> wxl: If it was untested on 64-bit entirely then yeah, it shouldn't be released.
[20:02] <infinity> wxl: We'll have it fixed on 32-bit tomorrow, so people can test on their G4s again.
[20:02] <wxl> infinity: but like amd64 and i386 are not fully tested for all testcases. i'm inclined to call it good, since beta1 was fine, but that may be an error of judgement. that's really waht i need some advice on.
[20:03] <infinity> wxl: As for "partially tested", the bare minimum that I figure a flavour needs to do is "boot, install, reboot -- computer didn't explode".  I'll release anything in that state, if you ask me to, the rest of the bugs are yours.
[20:03] <elfy> lol
[20:04] <wxl> yeah :/
[20:04] <knome> pretty much agree with that.
[20:04] <elfy> from my point of view I am happy that the bugs we've got aren't ours to fix :)
[20:04] <infinity> wxl: Basically, beyond "it boots and installs stuff and doesn't actively harm users", I leave further discretion to the flavour leads about the quality they want or care about in their releases.
[20:04] <wxl> someone is running a testcase on amd64 now
[20:04]  * wxl facepalms
[20:05] <wxl> amd64 is the real bummer since there is no alternate testing of any kind and the only passed testcase is the for live session
[20:05] <wxl> i guess i can't call it ready
[20:06] <wxl> so i guess i'm done infinity :(
[20:06] <infinity> wxl: You've got time, I'm still wrangling paperwork and source CDs.
[20:06] <wxl> infinity: how much time?
[20:06] <infinity> wxl: Find a guinea pig to smoketest your amd64 alternate in the next hour. ;)
[20:07] <infinity> (or two)
[20:07] <cjwatson> That's loads of time, for the warty preview I smoketested amd64/i386/powerpc in I think 30 minutes end to end :)
[20:07] <cjwatson> From end of image production
[20:08] <wxl> cjwatson: hey we can't ALL be cool as you :)
[20:09] <jibel> wxl, what do you want to test, lubuntu alternate amd64?
[20:09] <cjwatson> that was ten years ago, I was just a guy with too many computers in his bedroom
[20:09] <cjwatson> not the international man of mystery I am now
[20:10] <wxl> jibel: yes that would be a great start thank you
[20:10] <knome> you mean you are still the same guy, but covered in the fog of mystery? ;)
[20:10] <jibel> wxl, okay, syncing
[20:11] <wxl> thank you
[20:11] <cjwatson> knome: some kind of fog anyway
[20:11] <knome> hehe :)
[20:15] <davmor2> infinity: bug #1374126 do you need anything else? I added the installer syslog
[20:15] <ubot2> bug 1374126 in ubiquity (Ubuntu) "mac is not installing bcmwl even though 3rd party drivers is selected" [Undecided,New] https://launchpad.net/bugs/1374126
[20:17] <davmor2> battery dying no charger nearby arrrggghhh I hate having to pack my office
[20:18] <knome> davmor2, let me fix that for you... s/having to pack//
[20:18] <knome> :]
[20:20] <davmor2> knome: the council is our landlord they are rewiring our property as well as ripping out and refitting the bathroom and kitchen, we've been packing for the lst 2 weeks they start tomorrow my office is last cause I still need to work tomorrow, not fun :)
[20:21] <knome> yeah... i work from home too, and i know moving isn't fun
[20:23] <knome> or any kind of thing that stops you from working
[20:36] <jibel> wxl, I tried a default installation and lvm/encrypted both went fine but the password I set it not recognized after installation which is really weird. also the plymouth issue is really annoying for the user don't see the password field in the boot screen
[20:37] <jibel> wxl, digging why it rejects my password
[20:37] <wxl> hm
[20:41] <balloons> jibel, are you running through the server tests atm?
[20:41] <balloons> if so, MAAS shouldn't be in there
[20:42] <balloons> let me remove it
[20:42] <jibel> balloons, I'm doing some smoketests of lubuntu
[20:48] <jibel> wxl, lubuntu alternate amd64 guided and encryption tests case are okay. I don't know why it didn't work with a French keyboard layout though.
[20:48] <jibel> *test cases
[20:48] <jibel> and entire disk passed too
[20:49] <wxl> jibel: thanks i'll call them good
[20:50] <wxl> also it looks like someone finished the desktop testcase
[20:50] <wxl> admittedly for manual paritioning :/ but i think i'll call it good
[22:02] <wxl> ok release notes done, email ready to be sent; i await your command infinity
[23:32] <wxl> are we ready to release yet?
[23:55] <bdmurray> slangasek: Could you fully phased aptdaemon in trusty-updates?
[23:56] <bdmurray> slangasek: there were regressions detected because aptdaemon crashes didn't used to include the version number...
[23:57] <slangasek> bdmurray: done