[00:08] flexiondotorg_: Sorry, ended up somewhat (very) sick today. [00:54] infinity, Sorry to hear. I'll "annoy" you another day :-) Rest up. [01:10] Oh, launchpad is down/broken for some reason! why such things happen during before a milestone release?! [01:11] infinity, I'm testing Ubuntu GNOME images and these are true mess :( [01:11] amjjawad: Security updates, it's only temporary. [01:11] amjjawad: for more info on that, see #canonical-sysadmin. [01:11] infinity, the installation is broken and I just can't install anything. [01:13] wxl, "Technically, this is a 503 error and has been caused by our database being temporarily offline. " but thanks for your advice :) [01:13] amjjawad: have you read the topic at #canonical-sysadmin? [01:13] infinity, http://iso.qa.ubuntu.com/qatracker/milestones/357/builds/113126/testcases [01:13] amjjawad: I'm staying far away from this milestone. [01:14] amjjawad: you can see who is involved in this milestone here https://wiki.ubuntu.com/XenialXerus/ReleaseTaskSignup [01:14] suffice it to say, flocculant is asleep [01:14] i believe stgraber is handling the canonical side of things, right, infinity ? [01:15] Thanks infinity and wxl then guess I have to wait as there is nothing I can do except confirming bugs. [01:16] amjjawad: you do know you can get around the upower bug by running off ac power only, right? [01:16] The upower bug was fixed, it just needs a respin. [01:16] wxl, I'm testing on Oracle VB. Not sure if that applies to that as well?! [01:16] (which stgraber left up to the flavours to do themselves) [01:17] infinity: not true. flocculant triggered a respin and doesn't work. [01:17] how can I know if I have access to do a re-spin or not? can I try? [01:18] to be more accurate: a re-spin for Ubuntu GNOME images only. [01:18] amjjawad: if you have an SSO login to the tracker and you have an LP membership that allows you to, for example, mark images as ready, you can select a rebuild in the same area there [01:18] amjjawad: just click the right images, and click rebuild. bvut again, i don't think it will help [01:18] wxl, indeed, I have access to mark them as ready but never touched "re-spin" as of now. [01:18] lftp cdimage.ubuntu.com:/ubuntu-gnome/daily-live/20160222.2> cat xenial-desktop-amd64.manifest | grep upower [01:18] amjjawad: and yes, if your host has a battery, remove the battery and run off of AC power and your vm will work. [01:18] gir1.2-upowerglib-1.0 0.99.4-1 [01:18] The latest version isn't in those images. [01:18] libupower-glib3:amd64 0.99.4-1 [01:18] upower 0.99.4-1 [01:18] wxl: It'll help. [01:18] infinity: it isn't in the xubuntu images? [01:19] darkxst, I'll give it a go! [01:19] wxl: The newest xubuntu images have -2. [01:20] infinity: jibel asked me to do a respin earlier too, but I have no access to do that [01:20] infinity: --which is supposedly the fix, right? [01:20] wxl: Yes. [01:20] infinity: and what i'm telling you is dear flocculant already tested it and no dice. [01:20] infinity: i know the bug is fix released. i know pitti worked on it. it didn't fix it. [01:21] is there any harm if one does a re-spin?! [01:21] Or the testing methodology was lacking. I'm happy to believe both. [01:21] amjjawad: No. [01:21] amjjawad: no harm. go for it. [01:21] perfect :D [01:21] amjjawad: if you DO get success, let me know. [01:21] wxl, sure ;) [01:21] amjjawad: but the battery removal WILL work. [01:22] request a rebuild, right? [01:22] do it [01:22] wxl, yes, will remember the battery thing. [01:27] Done. I must leave my home now. Will keep you posted wxl in case the new build is okay. [01:28] Launchpad is back. === maclin1 is now known as maclin [04:29] fwiw i'm sure when amjjawad comes back he's going to complain about the gnome images having failed :) https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/xenial/ubuntu-gnome [05:23] wxl, I retried them, i386 worked, amd64 is MIA! [05:29] darkxst: and logs aren't very telling either http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-gnome/xenial/daily-live-20160224.log [05:29] darkxst: did you get a chance to test the ubiquity/upower bug on that i386? or does your hardware not have a battery? [05:30] wxl, trying to find my usb stick so can test on my laptop [05:30] might have to go buy another one! [05:31] darkxst: you can do it in a vm, too [05:35] wxl, will try once it downloads [05:50] infinity, amd64 ubuntu-gnome build seems to be stuck in a black hole [06:26] wxl, what crashes exactly? the installer or live session? [06:31] my VM cannot see the battery === ochosi_ is now known as ochosi [07:25] darkxst: not having a laptop to physically look myself relying on bug report, but I know the guy tested my respun image is honest :) he says "Yes, the crash dialog appears whether I start the install process from the main menu or from the desktop icon." which implies to me that he sees live session [07:26] Yeah, the crash is in ubiquity, so live session would work fine. [07:26] hi infinity :) [07:27] flocculant: But also not entirely sure if your tester definitely tested a fixed image, unless it's a different crash, since the one reported literally can't happen in the new version pitti uploaded (the function call isn't there anymore :P) [07:27] infinity: well I have to assume that he did use the respun image - he's not new to testing :) [07:28] flocculant: Sure, but lots of people not new to testing mess that one up several times a year, me included. ;) [07:28] yea [07:28] darkxst: Lemme go find your lost image. [07:29] darkxst: (You want stgraber for future complaints about this milestone, I'm supposedly not helping) [07:30] darkxst: Cancelled and re-requested, should be happier. [07:35] infinity, ok noted, thanks! [07:37] flocculant, I will test on a real laptop after dinner [07:40] hopefully it crashed before the repartitioning bit, since I can't really do that unless I can find an old hdd [07:41] darkxst: afaik it doesn't get anywhere but starting up [07:41] k [07:41] I'll try and breathe life back in to a really moribund laptop after work [07:43] its hot here, my laptop is trying its best not to melt ;) [07:44] :) [07:44] 72C basically idle [07:45] I don't think the sensors on any of my hardware ever see that :D [07:45] UK - it's a bit warm - oooh best rain for a few days then ... [07:45] Ive not since that since the prescott P4 days, wonder if the fan is gone [08:04] darkxst: ok - got this old laptop working enough - it doesn't even start the installer dialogue [08:11] flocculant, can you get a backtrace? [08:12] probably if someone tells me how ... [08:12] but not now - got 15 minutes to get ready for work now :) [08:13] flocculant, if it crashed, you should get crash popup? [08:18] I did [08:22] flocculant: I've got pitti looking into it again, perhaps he only fixed one of two bugs. :P [08:22] infinity: ack [08:23] flocculant: pitti, pitti, flocculant [08:24] ha ha ha - no need for introductions :) [08:24] infinity: I tried plain ubuntu for now [08:24] and in the live session [08:24] flocculant, pitti, its crashing here also, but I am too hungry to look just yet! [08:24] :) [08:24] does that happne in the live session or in ubiquity-only, or in the "choose between those" dialog (ubiquity-dm)? [08:25] pitti ubiquity-dm crashed here [08:25] darkxst: Are you too hungry to get pitti some basic "dpkg -l" and backtrace info? :) [08:25] ah, dm [08:25] we are talking about bug 1548362, right? [08:25] bug 1548362 in ubiquity (Ubuntu) "ubiquity crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.InvalidArgs: No such interface '/org/freedesktop/UPower'" [Medium,New] https://launchpad.net/bugs/1548362 [08:25] just to avoid doubt [08:25] pitti: I was told it happens either in ubiquity-dm, or live+ubiquity. [08:25] infinity, I have food on the bbq, gotta run, be back in 20mins [08:25] Heh. [08:25] pitti: I leave you with the wolves, I shouldn't be active right now. [08:26] Or, at least, I shouldn't be admitting to it. [08:26] pitti: I have enough time to boot before leaving - I'll just double check [08:27] ubiquity-dm also doesn't crash here [08:27] flocculant: is that with an actual battery? I only tried in qemu so far [08:27] or is that somehow flavor specific? [08:27] pitti: Oh, it does require having a battery, yes. [08:27] well, perhaps it's easier if you could describe your precise situation in that bug [08:27] pitti, no dm doesnt crash its ubiquity greeter and yes its that dbus error [08:28] other than "requires a MacBook Pro" [08:28] pitti: yea battery [08:28] and my food is burning [08:28] pitti: Though, apparently vbox passes through enough fake batteryness on a laptop to also trigger it. :P [08:28] pitti, thinkpad t400 here [08:29] pitti: Crashes on startup, so entirely safe to abuse your own laptop for this, it never gets to the destructive bits. [08:30] ok, I'll try in vbox and on my laptop [08:30] pitti: ok - I am seeing the No such interface /org/freedesktop/upower bug [08:30] flocculant: do you get an upower crash? [08:30] what does "upower -d" show? [08:30] in laptop with battery [08:31] I really have to go now - late already ... [08:31] meh, installing vbox insists on virtualbox-dkms which breaks secure boot [08:32] pitti: shows a whole bunch of stuff - but no net on it atm - just got it working enough to test this [08:32] and now really really off :p [08:40] pitti, this bug only happens on laptops with batteries. I didn't have a chance to reproduce it myself but davmor2 could with the new upower. [08:42] jibel: I'm currently testing on my laptop [08:45] pitti, I can't get wifi working, not able to install enough to get a backtrace [08:48] meh, this whole test was a waste of time [08:49] at least the current ubuntu desktop image still has 0.99.4-1 [08:49] I did get the crash, and only checked the version afterwards [08:49] http://cdimage.ubuntu.com/cdimage/daily-live/current/xenial-desktop-amd64.manifest [08:49] upower0.99.4-1 [08:49] ah, /current is from yesterday, /pending is from today [08:51] infinity: ^ [08:51] * pitti rsyncs /pending and retries with that [09:07] pitti, right, that's why I asked a respin. I am not sure people tested the right version and side loading upower is not trivial [09:07] jibel: got it; let's move to #u-release to keep it all in one place [09:08] it's already u-release? [09:08] pitti, It is possible this bug is related to upower? https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1549045 [09:08] Launchpad bug 1549045 in ubiquity (Ubuntu) "Ubiquity drive space and connectivity checks are missing" [Undecided,New] [09:08] Because I think I'm right is saying that those checks also include a battery connectivity test? [09:08] flexiondotorg_, unlikely [09:09] morning all [09:09] morning davmor2 [09:10] cyphermox: ubiquity commit 6376> please never ever use a blank "except:" statement [09:10] cyphermox: this is always wrong, it hides stupid things like SyntaxError and the like [09:11] yep, should always be "except Exception:" if you specifically want a catch-all [09:11] I'm reverting that, and put in the proper fix for bug 1547956 [09:11] bug 1547956 in ubiquity (Ubuntu Xenial) "ubiquity crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.InvalidArgs: No such interface '/org/freedesktop/UPower'" [Critical,In progress] https://launchpad.net/bugs/1547956 [09:13] pitti: I commented on https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1547793 with the steps I'd take, I can reproduce it really quickly and force an ssh channel onto it if that will help, at all? [09:13] Launchpad bug 1547793 in Upower "upowerd crashed with SIGSEGV in g_variant_is_trusted()" [Critical,In progress] [09:13] davmor2: nevermind, it's all figured out [09:13] davmor2: see #u-release [09:13] pitti: awesome [09:14] pitti: we're in u-release aren't we [09:14] davmor2: argh, sorry, so we are [09:14] davmor2: I have my IRC windows the wrong way around [09:14] ah u-quality [09:16] pitti: ok so I grab the latest pending iso and then boot the live session enable proposed and install what package to confirm it is fixed? [09:16] davmor2: it's not yet [09:16] davmor2: ubiquity with the fix is FTBFS [09:16] so, no debs to test [09:16] pitti: ah right [09:17] infinity, cyphermox: proper fix for ubiquity crash committed to bzr [09:17] pitti: okay well I'm all yours for testing when it's ready, just give me a ping with what to install from where and I'll jump on it :) [09:18] but the FTBFS due to all these test failures in https://launchpadlibrarian.net/242306075/buildlog_ubuntu-xenial-amd64.ubiquity_2.21.45_BUILDING.txt.gz is still an issue [09:28] I have an appointment in a few minutes, so I'm afraid I need to disappear for about two hours soon [09:29] local ubiquity build still fails [09:29] * pitti tries to revert the a11y changes [09:30] pitti: Just fork from the version in -release, apply critical fix, migrate that, then merge and let cyphermox deal with it? [09:30] yeah, .44 is more or less that [09:31] i. e. I reverted both changes from .45, and fixed the upower one [09:31] * pitti tests to build .44 in the meantime, in case it's due to dependency changes [09:34] c'mon, .46, build [09:42] screw it, that didn't help [09:42] so it's a dependency change [09:42] need to figure this out later, appointment now [12:18] bdmurray, any chance we can boot bug 1530913 to updates today? [12:18] bug 1530913 in nova (Ubuntu Wily) "[SRU] liberty point releases" [Undecided,Fix committed] https://launchpad.net/bugs/1530913 [12:18] I'd like to get that released asap [12:36] cyphermox: you and me are gonna be buddies for the next few weeks I can feel it, bug #1549277 might be related to the upower stuff in some way [12:36] bug 1549277 in ubiquity (Ubuntu) "Ubiquity throws up a ubi-prepare error when using uefi and secureboot" [Undecided,New] https://launchpad.net/bugs/1549277 [12:37] cyphermox: that is running in vm [12:38] jibel: ^ [12:44] davmor2, sounds like a bug in the package intel-microcode [12:45] pitti: any progress ? [12:45] which sounds a bit open ended - but I'm actually only interested in ubiquity or whatever's causing the b1 issues :D [12:45] flocculant: appointment plus travel time, plus lunch, so possibly not for an hour or so [12:46] flocculant: soon [12:46] jibel: could well be [12:46] or maybe not [12:47] davmor2: ack - I'm only about for 30 minutes now anyway [12:48] davmor2, or an initramfs bug, in any case a missing dependency somewhere [12:49] davmor2, is shim-signed installed? [12:50] davmor2, it's on hw? [12:51] jibel: no this is kvm [12:52] jibel: I'm wondering if it might be the new code that turns off secureboot but won't really know for a but I guess [14:06] cyphermox, could you have a look at bug 1549045? not sure it's on purpose [14:06] bug 1549045 in ubiquity (Ubuntu) "Ubiquity drive space and connectivity checks are missing" [High,Confirmed] https://launchpad.net/bugs/1549045 [14:14] could that be related to ubiquity's test failures? they also complain about localechooser, partman etc. not being present [14:15] or tons of missing labels [14:15] this for sure feels real enough that "disable the tests" wouldn't give us much -- the package might build, but still not work [14:15] pitti, possibly, the installer also complains about missing objects to translate, which is obviously the case [14:15] https://launchpadlibrarian.net/242306075/buildlog_ubuntu-xenial-amd64.ubiquity_2.21.45_BUILDING.txt.gz -> hmm, all the partman tests [14:16] * Automatic update of included source packages: hw-detect [14:16] 1.114ubuntu2. [14:16] hmm, let's see [14:17] not sure how http://launchpadlibrarian.net/240232932/hw-detect_1.114ubuntu1_1.114ubuntu2.diff.gz could break ubiquity's tests, though [14:19] Template parse error near `Binary file (standard input) matches', in stanza #1 of tests/debconfdb [14:19] that's new, that didn't happen in the previous https://launchpadlibrarian.net/238709629/buildlog_ubuntu-xenial-amd64.ubiquity_2.21.44_BUILDING.txt.gz yet [14:21] xnox, cjwatson ^ does that ring a bell by any chance? [14:21] (looking at the ubiquity FTBFS) [14:21] I have been looking at those [14:22] the localechooser test and all are unrelated [14:23] pitti, cyphermox: oh that could be why I hit this then https://launchpad.net/bugs/1549277 [14:23] Launchpad bug 1549277 in ubiquity (Ubuntu) "Ubiquity throws up a ubi-prepare error when using uefi and secureboot" [High,Confirmed] [14:23] it must be outside of ubiquity itself for sure, so none of the bundled projects [14:23] as .44 built previously, and now not any more [14:24] I'd selected third party drivers [14:24] and I get the "Template parse error" with building .44 now [14:24] yes, lemme work on this [14:25] davmor2, it's possible, the detection of secure boot is done in the prepare stage [14:25] davmor2: no, this is different, thanks for reporting [14:25] debconf hasn't changed since Feb 16 [14:25] davmor2: was this on a secureboot system? [14:26] cyphermox: sercureboot kvm [14:26] hrm [14:26] and po-debconf changed on Jan. 7th [14:26] weird, you should have had mokutil available. [14:26] so we have a new apt, gnutls, perl, procps [14:27] debianutils, libc6, etc, OMG lots of changes [14:28] cyphermox: yeap it asked for password and stuff in syslog it is complaining about the intel-microcode firmware but again might be related to hw-detect if that is broken right? [14:28] not at all [14:29] pitti: and mokutil for disabling secureboot from userland [14:29] pitti: and apps, and unity7 and [14:29] + ..... [14:29] unity, apps etc. aren't relevant for building ubiquity I think [14:30] * pitti is currently cleaning up the build logs to diff them better [14:31] * davmor2 hugs pitti sounds like he needs it [14:31] http://paste.ubuntu.com/15187518/ → diff of build deps [14:31] thanks davmor2 :) [14:31] * davmor2 hugs cyphermox too or he feels jealous [14:32] cyphermox, pitti there is lot of changes in ubiquity .45 to rework the accessibility code, including changes to gtk_ui [14:32] jibel: well, I'm not especially worried about that [14:33] looks like things probably fail all because of the same-ish reasons as localechooser is unhappy [14:33] jibel: they aren't it, already tested [14:33] jibel: as I said, rebuilding .44 right now fails with the same thing [14:33] that's the previous version that built on Feb 16 [14:33] ah okay [14:33] hence the diff of the build deps in http://paste.ubuntu.com/15187518/ [14:33] nothing jumps out on me, though [14:34] nope [14:34] I mean, could be new grep or whatnot, but I still wonder about whether this debconf template parsing error rings a bell with anyone [14:34] yeah, it's very suspect [14:34] I'm testing a build of localechooser in a PPA [14:36] pitti: only thing I see that is new is libkmod2 [14:36] pitti: no red version of that [14:36] oh and dash by the look of it [14:38] oh and one final one coreutils [14:39] could well be new grep, maybe needs to run in a UTF-8 locale? [14:40] I was suspecting sed before [14:40] but yeah, grep [14:40] might even need to be fixed in debconf [14:40] ok, I'll try a build with the previous grep [14:40] though debconf-loadtemplate is perl [14:41] oh, no, it'll be a stage or two before d-l won't iit [14:41] *it [14:41] possibly the install rule in d-i/Makefile [14:46] seems likely, localechooser on its own seems happy enough [14:46] let's see [14:47] meh, it apparently ignored my --extra-package=/tmp/grep_2.22-1ubuntu2_amd64.deb [14:47] * pitti builds it with plan B [14:53] cyphermox, cjwatson: we have a winner! [14:53] yeah [14:53] just seeing if it reproduces locally with LC_ALL=C, I bet it does [14:54] so, we could revert grep, but I wonder if we can set C.UTF-8 for the build [14:54] either wholesale, or for the bit that needs it [14:54] let's not revert grep [14:54] cjwatson: simply sbuilding ubiquity .44 does reproduce it, yes [14:55] cjwatson: yeah, I'd like to avoid that too if possible [14:55] hey folks. any new news on the whole upower/ubiquity thing? [14:55] wxl: see last 50 lines of backscroll :) [14:55] pitti: so, you're working on it. got it :) [14:55] wxl: the upower bug fix is committed, we just need to get ubiquity to build [14:55] OH [14:55] wxl: and then the 50 before that too :) [14:55] I think just export LC_ALL := C.UTF-8 in debian/rules would likely be a good plan [14:56] we intend to do that centrally in launchpad-buildd at some point anyway [14:56] but that's a less trivial thing to change [14:57] * pitti test-builds with that [14:59] http://paste.ubuntu.com/15187721/ → the changelog is a bit fuzzy [15:00] pitti, that's obscure =) [15:00] it must be a milestone week [15:01] well, we know it's due to grep, we know that UTF-8 fixes it, we are under the gun, so that's all we know about the reason :) [15:01] * debian/rules: Build under C.UTF-8 locale. grep 2.23 causes broken debconf [15:01] templates to be built under the C locale. [15:01] how about that [15:01] I've heard of other similar things, e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815620 [15:01] Debian bug 815620 in debhelper "addsubstvar fails if there are utf characters in the substvar file" [Important,Open] [15:01] builds fine [15:02] you have 30 seconds to object :) [15:03] nah, go ahead [15:05] pushed/dput'ed [15:05] $ bzr push --tags [15:05] bzr: ERROR: no such option: --tags [15:05] bah, git, you spoiled my workflow [15:06] pitti: surely you meant https://www.youtube.com/watch?v=Hzlt7IbTp6M [15:06] infinity, flocculant, wxl: ok, so let's get https://launchpad.net/ubuntu/+source/ubiquity/2.21.46 built, published, and an image rebuilt with that, and the world should be a happier place [15:07] pitti: get it published and i'll rebuild and test an image or two [15:09] davmor2: ouch [15:13] cjwatson: pitti: thanks for looking at this [15:13] yw [15:35] * flexiondotorg_ has been following the backlog regarding ubiquity/grep. Thanks everyone. [15:41] wxl: it's on the mirrors now, so you should be able to dist-upgrade the live session [15:42] (except for armhf, that just finished building) [15:43] cyphermox, cjwatson, pitti: woohoo! Thanks all [15:45] cyphermox: ummmm I hit an issue with upgrade again, Upgrade starts now that has been fixed \o/ however now mid upgrade it kicks me out of the system and I can't log back in \o/ You love this don't you I can tell :D [15:46] a desktop? [15:47] cyphermox: I can try on a desktop this is kvm and yes secure booted again so might be related to the earlier bug [15:47] that's not what I mean [15:48] what you're trying to upgrade is a desktop, from a logged in session? [15:48] cyphermox: trusty to xenial on amd64 bit [15:48] if so, then what kicks you out must be something like restarting X or lightdm [15:48] cyphermox: one crash on fontconfig.0.crash [15:48] oh, interesting [15:49] well, please file the bug for that crash [15:49] cyphermox: let me see if I can get that uploaded [16:03] cyphermox: bug #1549356 [16:03] bug 1549356 in fontconfig (Ubuntu) "package fontconfig 2.11.1-0ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1" [Undecided,New] https://launchpad.net/bugs/1549356 [16:04] jamespage: the ceilometer package hasn't been available very long [16:05] bdmurray, there was an original sru for some point releases which is ready to go [16:05] and a subsequent one for ceilometer 5.0.2 and neutron 7.0.3 which is not yet tested [16:09] jamespage: well, ceilometer 5.0.1 was superceded by 5.0.2... [16:17] pitti: ty - so I booted current iso - grabbed ubiquity from proposed - started install from desktop - and it's finishing now [16:17] flocculant: *phew* :) [16:17] :) [16:17] soon as queuebot says something about it I'll rebuild mine [16:27] ah [16:28] cyphermox: anything else you need from that before I kill the vm? [16:29] no [16:30] all I really need is my first coffee of the day [16:30] * davmor2 sets up a grip for cyphermox [16:32] pitti: it finished as well - appeared to take a while to get to the 'Remove the install media and press enter' stage - but did [16:46] s/grip/drip even [16:52] infinity: please could you review my FFe request in bug 1473691? [16:52] bug 1473691 in squid3 (Ubuntu) "[FFe] squid: Update to latest upstream release (3.5)" [Wishlist,In progress] https://launchpad.net/bugs/1473691 [17:01] bdmurray, apologies I'd not realized that had happened [17:43] cjwatson / pitti: Probably the same as https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1547466 ? [17:43] Launchpad bug 1547466 in grep (Ubuntu) "grep switches into binary mode while processing a text file" [High,New] [17:43] cjwatson / pitti: Didn't realize it was more far-reaching. If we're subtly breaking translation templates and such, perhaps we either need to "fix" grep or switch buildds to UTF-8 across the board ASAP. [17:46] * Laney heard about another thing that broke because of new grep [17:46] pitti: when is it likely to get out of proposed? [17:47] https://anonscm.debian.org/viewvc/pkg-gnome/tools/gnome-pkg-tools/1/rules/uploaders.mk?r1=47368&r2=47367&pathrev=47368 [17:47] * Laney goes blind [17:52] flocculant, after autopkgtests are done. It's currently waiting for an executor http://autopkgtest.ubuntu.com/running.shtml [17:55] thanks jibel :) [17:55] guessed it was something like that - never seen that page before :) [18:00] flocculant, actually the page you should check when you're wondering why something is stuck in proposed is http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubiquity which links to the page above [18:03] ta [18:25] jibel: so new question :) what if something is 'Always failed' eg ubiquity on s390x [18:25] then that doesn't block migration [18:25] flocculant: "always failed" doesn't prevent migration. [18:25] cjwatson: Jinx. [18:25] ubiquity is migrating at the moment [18:25] ok - thanks both - it's all dutch to me :) [18:26] cjwatson: thanks :) [18:26] (as shown on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt, in considerably more opaque terms) [18:26] Or shown in the LP UI by the fact that it randomly disappears. ;) [18:26] hey, it's there now :P [18:26] Could we not propogate "pending" to that display element? [18:27] it would probably be a good idea [18:27] The delete/pending behaviour of "it doesn't exist" confuses everyone who isn't us. [18:27] https://launchpad.net/ubuntu/+source/ubiquity/+publishinghistory is the least confusing view despite being ugly [18:28] (and somewhat weird timestamp handling) [18:28] Right, but people land on the version page and it's blank is the complaint. [18:28] yeah [18:28] publishinghistory also requires a PhD in LP to read correctly the first time. But at least it's accurate. [18:28] ha ha ha [18:28] I'll have you know I'm merely Mr Watson [18:29] oh my ... dad jokes :p [18:29] flocculant: Well, he does have 37 kids. [18:29] :) [18:37] * davmor2 tries a netboot as everything else is broken :D [18:38] cjwatson: elementary my dear Watson [18:53] pitti: welllll i'm finally out of my meeting. i'll check into it. thanks! [18:54] pitti: it's .45 we need right? [19:02] infinity: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1547630 [19:02] Launchpad bug 1547630 in debian-cd (Ubuntu) "Server 14.04.4 OEM Install option doesn't work" [High,Triaged] [19:06] ^ more for the oops factor than anything else, really [19:07] wxl, .46 [19:07] jibel, cyphermox: OMG OMG OMG OMG OMG OMG OMG OMG OMG OMG OMG neboot worked I have a xenial desktop installed \o/ [19:08] davmor2, great, ship it [19:08] jibel: so a rebuild will get me that, right? [19:09] wxl, yes [19:09] jibel: thanks. sorry for being explicit but i want to be sure when i tell all the testers to jump XD [19:10] davmor2: That's some serious excitement. [19:11] infinity: to date every install attempt and upgrade from trusty attempt has failed dismally [19:11] cyphermox: Ahh, balls. Want to propose an MP to debian-cd? We still have one more point release for trusty, may as well fix it. [19:12] infinity: already on it [19:12] cyphermox: My hero. [19:12] fwiw, 14.04.4 isn't on the wiki on Releases either [19:12] I could only quickly find my Changes document. [19:12] aw crap i guess i didn't need to rebuild the d-i images :/ [19:13]