[00:08] <infinity> flexiondotorg_: Sorry, ended up somewhat (very) sick today.
[00:54] <flexiondotorg_> infinity, Sorry to hear. I'll "annoy" you another day :-) Rest up.
[01:10] <amjjawad> Oh, launchpad is down/broken for some reason! why such things happen during before a milestone release?!
[01:11] <amjjawad> infinity, I'm testing Ubuntu GNOME images and these are true mess :(
[01:11] <infinity> amjjawad: Security updates, it's only temporary.
[01:11] <wxl> amjjawad: for more info on that, see #canonical-sysadmin.
[01:11] <amjjawad> infinity, the installation is broken and I just can't install anything.
[01:13] <amjjawad> wxl, "Technically, this is a 503 error and has been caused by our database being temporarily offline. " but thanks for your advice :)
[01:13] <wxl> amjjawad: have you read the topic at #canonical-sysadmin?
[01:13] <amjjawad> infinity, http://iso.qa.ubuntu.com/qatracker/milestones/357/builds/113126/testcases
[01:13] <infinity> amjjawad: I'm staying far away from this milestone.
[01:14] <wxl> amjjawad: you can see who is involved in this milestone here https://wiki.ubuntu.com/XenialXerus/ReleaseTaskSignup
[01:14] <wxl> suffice it to say, flocculant is asleep
[01:14] <wxl> i believe stgraber is handling the canonical side of things, right, infinity ?
[01:15] <amjjawad> Thanks infinity and wxl then guess I have to wait as there is nothing I can do except confirming bugs.
[01:16] <wxl> amjjawad: you do know you can get around the upower bug by running off ac power only, right?
[01:16] <infinity> The upower bug was fixed, it just needs a respin.
[01:16] <amjjawad> wxl, I'm testing on Oracle VB. Not sure if that applies to that as well?!
[01:16] <infinity> (which stgraber left up to the flavours to do themselves)
[01:17] <wxl> infinity: not true. flocculant triggered a respin and doesn't work.
[01:17] <amjjawad> how can I know if I have access to do a re-spin or not? can I try?
[01:18] <amjjawad> to be more accurate: a re-spin for Ubuntu GNOME images only.
[01:18] <wxl> 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] <wxl> amjjawad: just click the right images, and click rebuild. bvut again, i don't think it will help
[01:18] <amjjawad> wxl, indeed, I have access to mark them as ready but never touched "re-spin" as of now.
[01:18] <infinity> lftp cdimage.ubuntu.com:/ubuntu-gnome/daily-live/20160222.2> cat xenial-desktop-amd64.manifest | grep upower
[01:18] <wxl> 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] <infinity> gir1.2-upowerglib-1.0   0.99.4-1
[01:18] <infinity> The latest version isn't in those images.
[01:18] <infinity> libupower-glib3:amd64	0.99.4-1
[01:18] <infinity> upower	0.99.4-1
[01:18] <infinity> wxl: It'll help.
[01:18] <wxl> infinity: it isn't in the xubuntu images?
[01:19] <amjjawad> darkxst, I'll give it a go!
[01:19] <infinity> wxl: The newest xubuntu images have -2.
[01:20] <cyphermox> infinity: jibel asked me to do a respin earlier too, but I have no access to do that
[01:20] <wxl> infinity: --which is supposedly the fix, right?
[01:20] <infinity> wxl: Yes.
[01:20] <wxl> infinity: and what i'm telling you is dear flocculant already tested it and no dice.
[01:20] <wxl> infinity: i know the bug is fix released. i know pitti worked on it. it didn't fix it.
[01:21] <amjjawad> is there any harm if one does a re-spin?!
[01:21] <infinity> Or the testing methodology was lacking.  I'm happy to believe both.
[01:21] <infinity> amjjawad: No.
[01:21] <wxl> amjjawad: no harm. go for it.
[01:21] <amjjawad> perfect :D
[01:21] <wxl> amjjawad: if you DO get success, let me know.
[01:21] <amjjawad> wxl, sure ;)
[01:21] <wxl> amjjawad: but the battery removal WILL work.
[01:22] <amjjawad> request a rebuild, right?
[01:22] <wxl> do it
[01:22] <amjjawad> wxl, yes, will remember the battery thing.
[01:27] <amjjawad> Done. I must leave my home now. Will keep you posted wxl in case the new build is okay.
[01:28] <wgrant> Launchpad is back.
[04:29] <wxl> 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] <darkxst> wxl, I retried them, i386 worked, amd64 is MIA!
[05:29] <wxl> 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] <wxl> 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] <darkxst> wxl, trying to find my usb stick so can test on my laptop
[05:30] <darkxst> might have to go buy another one!
[05:31] <wxl> darkxst: you can do it in a vm, too
[05:35] <darkxst> wxl, will try once it downloads
[05:50] <darkxst> infinity, amd64 ubuntu-gnome build seems to be stuck in a black hole
[06:26] <darkxst> wxl, what crashes exactly? the installer or live session?
[06:31] <darkxst> my VM cannot see the battery
[07:25] <flocculant> 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] <infinity> Yeah, the crash is in ubiquity, so live session would work fine.
[07:26] <flocculant> hi infinity :)
[07:27] <infinity> 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] <flocculant> infinity: well I have to assume that he did use the respun image - he's not new to testing :)
[07:28] <infinity> flocculant: Sure, but lots of people not new to testing mess that one up several times a year, me included. ;)
[07:28] <flocculant> yea
[07:28] <infinity> darkxst: Lemme go find your lost image.
[07:29] <infinity> darkxst: (You want stgraber for future complaints about this milestone, I'm supposedly not helping)
[07:30] <infinity> darkxst: Cancelled and re-requested, should be happier.
[07:35] <darkxst> infinity, ok noted, thanks!
[07:37] <darkxst> flocculant, I will test on a real laptop after dinner
[07:40] <darkxst> hopefully it crashed before the repartitioning bit, since I can't really do that unless I can find an old hdd
[07:41] <flocculant> darkxst: afaik it doesn't get anywhere but starting up
[07:41] <darkxst> k
[07:41] <flocculant> I'll try and breathe life back in to a really moribund laptop after work
[07:43] <darkxst> its hot here, my laptop is trying its best not to melt ;)
[07:44] <flocculant> :)
[07:44] <darkxst> 72C basically idle
[07:45] <flocculant> I don't think the sensors on any of my hardware ever see that :D
[07:45] <flocculant> UK - it's a bit warm - oooh best rain for a few days then ...
[07:45] <darkxst> Ive not since that since the prescott P4 days, wonder if the fan is gone
[08:04] <flocculant> darkxst: ok - got this old laptop working enough - it doesn't even start the installer dialogue
[08:11] <darkxst> flocculant, can you get a backtrace?
[08:12] <flocculant> probably if someone tells me how ...
[08:12] <flocculant> but not now - got 15 minutes to get ready for work now :)
[08:13] <darkxst> flocculant, if it crashed, you should get crash popup?
[08:18] <flocculant> I did
[08:22] <infinity> flocculant: I've got pitti looking into it again, perhaps he only fixed one of two bugs. :P
[08:22] <flocculant> infinity: ack
[08:23] <infinity> flocculant: pitti, pitti, flocculant
[08:24] <flocculant> ha ha ha - no need for introductions :)
[08:24] <pitti> infinity: I tried plain ubuntu for now
[08:24] <pitti> and in the live session
[08:24] <darkxst> flocculant, pitti, its crashing here also, but I am too hungry to look just yet!
[08:24] <flocculant> :)
[08:24] <pitti> does that happne in the live session or in ubiquity-only, or in the "choose between those" dialog (ubiquity-dm)?
[08:25] <darkxst> pitti ubiquity-dm crashed here
[08:25] <infinity> darkxst: Are you too hungry to get pitti some basic "dpkg -l" and backtrace info? :)
[08:25] <pitti> ah, dm
[08:25] <pitti> we are talking about bug 1548362, right?
[08:25] <pitti> just to avoid doubt
[08:25] <infinity> pitti: I was told it happens either in ubiquity-dm, or live+ubiquity.
[08:25] <darkxst> infinity, I have food on the bbq, gotta run, be back in 20mins
[08:25] <infinity> Heh.
[08:25] <infinity> pitti: I leave you with the wolves, I shouldn't be active right now.
[08:26] <infinity> Or, at least, I shouldn't be admitting to it.
[08:26] <flocculant> pitti: I have enough time to boot before leaving - I'll just double check
[08:27] <pitti> ubiquity-dm also doesn't crash here
[08:27] <pitti> flocculant: is that with an actual battery? I only tried in qemu so far
[08:27] <pitti> or is that somehow flavor specific?
[08:27] <infinity> pitti: Oh, it does require having a battery, yes.
[08:27] <pitti> well, perhaps it's easier if you could describe your precise situation in that bug
[08:27] <darkxst> pitti, no dm doesnt crash its ubiquity greeter and yes its that dbus error
[08:28] <pitti> other than "requires a MacBook Pro"
[08:28] <flocculant> pitti: yea battery
[08:28] <darkxst> and my food is burning
[08:28] <infinity> pitti: Though, apparently vbox passes through enough fake batteryness on a laptop to also trigger it. :P
[08:28] <darkxst> pitti, thinkpad t400 here
[08:29] <infinity> pitti: Crashes on startup, so entirely safe to abuse your own laptop for this, it never gets to the destructive bits.
[08:30] <pitti> ok, I'll try in vbox and on my laptop
[08:30] <flocculant> pitti: ok - I am seeing the No such interface /org/freedesktop/upower bug
[08:30] <pitti> flocculant: do you get an upower crash?
[08:30] <pitti> what does "upower -d" show?
[08:30] <flocculant> in laptop with battery
[08:31] <flocculant> I really have to go now - late already ...
[08:31] <pitti> meh, installing vbox insists on virtualbox-dkms which breaks secure boot
[08:32] <flocculant> pitti: shows a whole bunch of stuff - but no net on it atm - just got it working enough to test this
[08:32] <flocculant> and now really really off :p
[08:40] <jibel> 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] <pitti> jibel: I'm currently testing on my laptop
[08:45] <darkxst> pitti, I can't get wifi working, not able to install enough to get a backtrace
[08:48] <pitti> meh, this whole test was a waste of time
[08:49] <pitti> at least the current ubuntu desktop image still has 0.99.4-1
[08:49] <pitti> I did get the crash, and only checked the version afterwards
[08:49] <pitti> http://cdimage.ubuntu.com/cdimage/daily-live/current/xenial-desktop-amd64.manifest
[08:49] <pitti> upower0.99.4-1
[08:49] <pitti> ah, /current is from yesterday, /pending is from today
[08:51] <pitti> infinity: ^
[08:51]  * pitti rsyncs /pending and retries with that
[09:07] <jibel> 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] <pitti> jibel: got it; let's move to #u-release to keep it all in one place
[09:08] <jibel> it's already u-release?
[09:08] <flexiondotorg_> pitti, It is possible this bug is related to upower? https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1549045
[09:08] <flexiondotorg_> Because I think I'm right is saying that those checks also include a battery connectivity test?
[09:08] <jibel> flexiondotorg_, unlikely
[09:09] <davmor2> morning all
[09:09] <jibel> morning davmor2
[09:10] <pitti> cyphermox: ubiquity commit 6376> please never ever use a blank "except:" statement
[09:10] <pitti> cyphermox: this is always wrong, it hides stupid things like SyntaxError and the like
[09:11] <cjwatson> yep, should always be "except Exception:" if you specifically want a catch-all
[09:11] <pitti> I'm reverting that, and put in the proper fix for bug 1547956
[09:13] <davmor2> 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] <pitti> davmor2: nevermind, it's all figured out
[09:13] <pitti> davmor2: see #u-release
[09:13] <davmor2> pitti: awesome
[09:14] <davmor2> pitti: we're in u-release aren't we
[09:14] <pitti> davmor2: argh, sorry, so we are
[09:14] <pitti> davmor2: I have my IRC windows the wrong way around
[09:14] <davmor2> ah u-quality
[09:16] <davmor2> 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] <pitti> davmor2: it's not yet
[09:16] <pitti> davmor2: ubiquity with the fix is FTBFS
[09:16] <pitti> so, no debs to test
[09:16] <davmor2> pitti: ah right
[09:17] <pitti> infinity, cyphermox: proper fix for ubiquity crash committed to bzr
[09:17] <davmor2> 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] <pitti> 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] <pitti> I have an appointment in a few minutes, so I'm afraid I need to disappear for about two hours soon
[09:29] <pitti> local ubiquity build still fails
[09:29]  * pitti tries to revert the a11y changes
[09:30] <infinity> pitti: Just fork from the version in -release, apply critical fix, migrate that, then merge and let cyphermox deal with it?
[09:30] <pitti> yeah, .44 is more or less that
[09:31] <pitti> 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] <pitti> c'mon, .46, build
[09:42] <pitti> screw it, that didn't help
[09:42] <pitti> so it's a dependency change
[09:42] <pitti> need to figure this out later, appointment now
[12:18] <jamespage> bdmurray, any chance we can boot bug 1530913 to updates today?
[12:18] <jamespage> I'd like to get that released asap
[12:36] <davmor2> 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:37] <davmor2> cyphermox: that is running in vm
[12:38] <davmor2> jibel: ^
[12:44] <jibel> davmor2, sounds like a bug in the package intel-microcode
[12:45] <flocculant> pitti: any progress ?
[12:45] <flocculant> which sounds a bit open ended - but I'm actually only interested in ubiquity or whatever's causing the b1 issues :D
[12:45] <davmor2> flocculant: appointment plus travel time, plus lunch, so possibly not for an hour or so
[12:46] <davmor2> flocculant: soon
[12:46] <davmor2> jibel: could well be
[12:46] <jibel> or maybe not
[12:47] <flocculant> davmor2: ack - I'm only about for 30 minutes now anyway
[12:48] <jibel> davmor2, or an initramfs bug, in any case a missing dependency somewhere
[12:49] <jibel> davmor2, is shim-signed installed?
[12:50] <jibel> davmor2,  it's on hw?
[12:51] <davmor2> jibel: no this is kvm
[12:52] <davmor2> 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] <jibel> cyphermox, could you have a look at bug 1549045? not sure it's on purpose
[14:14] <pitti> could that be related to ubiquity's test failures? they also complain about localechooser, partman etc. not being present
[14:15] <pitti> or tons of missing labels
[14:15] <pitti> 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] <jibel> pitti, possibly, the installer also complains about missing objects to translate, which is obviously the case
[14:15] <pitti> https://launchpadlibrarian.net/242306075/buildlog_ubuntu-xenial-amd64.ubiquity_2.21.45_BUILDING.txt.gz -> hmm, all the partman tests
[14:16] <pitti>   * Automatic update of included source packages: hw-detect
[14:16] <pitti>     1.114ubuntu2.
[14:16] <pitti> hmm, let's see
[14:17] <pitti> not sure how http://launchpadlibrarian.net/240232932/hw-detect_1.114ubuntu1_1.114ubuntu2.diff.gz could break ubiquity's tests, though
[14:19] <pitti> Template parse error near `Binary file (standard input) matches', in stanza #1 of tests/debconfdb
[14:19] <pitti> 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] <pitti> xnox, cjwatson ^ does that ring a bell by any chance?
[14:21] <pitti> (looking at the ubiquity FTBFS)
[14:21] <cyphermox> I have been looking at those
[14:22] <cyphermox> the localechooser test and all are unrelated
[14:23] <davmor2> pitti, cyphermox: oh that could be why I hit this then https://launchpad.net/bugs/1549277
[14:23] <pitti> it must be outside of ubiquity itself for sure, so none of the bundled projects
[14:23] <pitti> as .44 built previously, and now not any more
[14:24] <davmor2> I'd selected third party drivers
[14:24] <pitti> and I get the "Template parse error" with building .44 now
[14:24] <cyphermox> yes, lemme work on this
[14:25] <jibel> davmor2, it's possible, the detection of secure boot is done in the prepare stage
[14:25] <cyphermox> davmor2: no, this is different, thanks for reporting
[14:25] <pitti> debconf hasn't changed since Feb 16
[14:25] <cyphermox> davmor2: was this on a secureboot system?
[14:26] <davmor2> cyphermox: sercureboot kvm
[14:26] <cyphermox> hrm
[14:26] <jibel> and po-debconf changed on Jan. 7th
[14:26] <cyphermox> weird, you should have had mokutil available.
[14:26] <pitti> so we have a new apt, gnutls, perl, procps
[14:27] <pitti> debianutils, libc6, etc, OMG lots of changes
[14:28] <davmor2> 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] <cyphermox> not at all
[14:29] <davmor2> pitti: and mokutil for disabling secureboot from userland
[14:29] <davmor2> pitti: and apps, and unity7 and
[14:29] <davmor2> + .....
[14:29] <pitti> 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] <pitti> http://paste.ubuntu.com/15187518/ →  diff of build deps
[14:31] <pitti> thanks davmor2 :)
[14:31]  * davmor2 hugs cyphermox too or he feels jealous 
[14:32] <jibel> cyphermox, pitti there is lot of changes in ubiquity .45 to rework the accessibility code, including changes to gtk_ui
[14:32] <cyphermox> jibel: well, I'm not especially worried about that
[14:33] <cyphermox> looks like things probably fail all because of the same-ish reasons as localechooser is unhappy
[14:33] <pitti> jibel: they aren't it, already tested
[14:33] <pitti> jibel: as I said, rebuilding .44 right now fails with the same thing
[14:33] <pitti> that's the previous version that built on Feb 16
[14:33] <jibel> ah okay
[14:33] <pitti> hence the diff of the build deps in http://paste.ubuntu.com/15187518/
[14:33] <pitti> nothing jumps out on me, though
[14:34] <cyphermox> nope
[14:34] <pitti> 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] <cyphermox> yeah, it's very suspect
[14:34] <cyphermox> I'm testing a build of localechooser in a PPA
[14:36] <davmor2> pitti: only thing I see that is new is libkmod2
[14:36] <davmor2> pitti: no red version of that
[14:36] <davmor2> oh and dash by the look of it
[14:38] <davmor2> oh and one final one coreutils
[14:39] <cjwatson> could well be new grep, maybe needs to run in a UTF-8 locale?
[14:40] <cyphermox> I was suspecting sed before
[14:40] <cyphermox> but yeah, grep
[14:40] <cjwatson> might even need to be fixed in debconf
[14:40] <pitti> ok, I'll try a build with the previous grep
[14:40] <cjwatson> though debconf-loadtemplate is perl
[14:41] <cjwatson> oh, no, it'll be a stage or two before d-l won't iit
[14:41] <cjwatson> *it
[14:41] <cjwatson> possibly the install rule in d-i/Makefile
[14:46] <cyphermox> seems likely, localechooser on its own seems happy enough
[14:46] <cjwatson> let's see
[14:47] <pitti> meh, it apparently ignored  my --extra-package=/tmp/grep_2.22-1ubuntu2_amd64.deb
[14:47]  * pitti builds it with plan B
[14:53] <pitti> cyphermox, cjwatson: we have a winner!
[14:53] <cyphermox> yeah
[14:53] <cjwatson> just seeing if it reproduces locally with LC_ALL=C, I bet it does
[14:54] <pitti> so, we could revert grep, but I wonder if we can set C.UTF-8 for the build
[14:54] <pitti> either wholesale, or for the bit that needs it
[14:54] <cjwatson> let's not revert grep
[14:54] <pitti> cjwatson: simply sbuilding ubiquity .44 does  reproduce it, yes
[14:55] <pitti> cjwatson: yeah, I'd like to avoid that too if possible
[14:55] <wxl> hey folks. any new news on the whole upower/ubiquity thing?
[14:55] <pitti> wxl: see last 50 lines of backscroll :)
[14:55] <wxl> pitti: so, you're working on it. got it :)
[14:55] <pitti> wxl: the upower bug fix is committed, we just need to get ubiquity to build
[14:55] <wxl> OH
[14:55] <davmor2> wxl: and then the 50 before that too :)
[14:55] <cjwatson> I think just export LC_ALL := C.UTF-8 in debian/rules would likely be a good plan
[14:56] <cjwatson> we intend to do that centrally in launchpad-buildd at some point anyway
[14:56] <cjwatson> but that's a less trivial thing to change
[14:57]  * pitti test-builds with that
[14:59] <pitti> http://paste.ubuntu.com/15187721/ → the changelog is a bit fuzzy
[15:00] <xnox> pitti, that's obscure =)
[15:00] <xnox> it must be a milestone week
[15:01] <pitti> 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] <pitti>   * debian/rules: Build under C.UTF-8 locale. grep 2.23 causes broken debconf
[15:01] <pitti>     templates to be built under the C locale.
[15:01] <pitti> how about that
[15:01] <cjwatson> I've heard of other similar things, e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815620
[15:01] <pitti> builds fine
[15:02] <pitti> you have 30 seconds to object :)
[15:03] <cyphermox> nah, go ahead
[15:05] <pitti> pushed/dput'ed
[15:05] <pitti> $ bzr push --tags
[15:05] <pitti> bzr: ERROR: no such option: --tags
[15:05] <pitti> bah, git, you spoiled my workflow
[15:06] <davmor2> pitti: surely you meant https://www.youtube.com/watch?v=Hzlt7IbTp6M
[15:06] <pitti> 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] <wxl> pitti: get it published and i'll rebuild and test an image or two
[15:09] <pitti> davmor2: ouch
[15:13] <cyphermox> cjwatson: pitti: thanks for looking at this
[15:13] <pitti> yw
[15:35]  * flexiondotorg_ has been following the backlog regarding ubiquity/grep. Thanks everyone.
[15:41] <pitti> wxl: it's on the mirrors now, so you should be able to dist-upgrade the live session
[15:42] <pitti> (except for armhf, that just finished building)
[15:43] <davmor2> cyphermox, cjwatson, pitti: woohoo!  Thanks all
[15:45] <davmor2> 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] <cyphermox> a desktop?
[15:47] <davmor2> 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] <cyphermox> that's not what I mean
[15:48] <cyphermox> what you're trying to upgrade is a desktop, from a logged in session?
[15:48] <davmor2> cyphermox: trusty to xenial on amd64 bit
[15:48] <cyphermox> if so, then what kicks you out must be something like restarting X or lightdm
[15:48] <davmor2> cyphermox: one crash on fontconfig.0.crash
[15:48] <cyphermox> oh, interesting
[15:49] <cyphermox> well, please file the bug for that crash
[15:49] <davmor2> cyphermox: let me see if I can get that uploaded
[16:03] <davmor2> cyphermox: bug #1549356
[16:04] <bdmurray> jamespage: the ceilometer package hasn't been available very long
[16:05] <jamespage> bdmurray, there was an original sru for some point releases which is ready to go
[16:05] <jamespage> and a subsequent one for ceilometer 5.0.2 and neutron 7.0.3 which is not yet tested
[16:09] <bdmurray> jamespage: well, ceilometer 5.0.1 was superceded by 5.0.2...
[16:17] <flocculant> pitti: ty - so I booted current iso - grabbed ubiquity from proposed - started install from desktop - and it's finishing now
[16:17] <pitti> flocculant: *phew* :)
[16:17] <flocculant> :)
[16:17] <flocculant> soon as queuebot says something about it I'll rebuild mine
[16:27] <jamespage> ah
[16:28] <davmor2> cyphermox: anything else you need from that before I kill the vm?
[16:29] <cyphermox> no
[16:30] <cyphermox> all I really need is my first coffee of the day
[16:30]  * davmor2 sets up a grip for cyphermox 
[16:32] <flocculant> 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] <davmor2> s/grip/drip even
[16:52] <rbasak> infinity: please could you review my FFe request in bug 1473691?
[17:01] <jamespage> bdmurray, apologies I'd not realized that had happened
[17:43] <infinity> cjwatson / pitti: Probably the same as https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1547466 ?
[17:43] <infinity> 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] <flocculant> pitti: when is it likely to get out of proposed?
[17:47] <Laney> 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] <jibel> flocculant, after autopkgtests are done. It's currently waiting for an executor http://autopkgtest.ubuntu.com/running.shtml
[17:55] <flocculant> thanks jibel :)
[17:55] <flocculant> guessed it was something like that - never seen that page before :)
[18:00] <jibel> 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] <flocculant> ta
[18:25] <flocculant> jibel: so new question :) what if something is 'Always failed' eg ubiquity on s390x
[18:25] <cjwatson> then that doesn't block migration
[18:25] <infinity> flocculant: "always failed" doesn't prevent migration.
[18:25] <infinity> cjwatson: Jinx.
[18:25] <cjwatson> ubiquity is migrating at the moment
[18:25] <flocculant> ok - thanks both - it's all dutch to me :)
[18:26] <flocculant> cjwatson: thanks :)
[18:26] <cjwatson> (as shown on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt, in considerably more opaque terms)
[18:26] <infinity> Or shown in the LP UI by the fact that it randomly disappears. ;)
[18:26] <cjwatson> hey, it's there now :P
[18:26] <infinity> Could we not propogate "pending" to that display element?
[18:27] <cjwatson> it would probably be a good idea
[18:27] <infinity> The delete/pending behaviour of "it doesn't exist" confuses everyone who isn't us.
[18:27] <cjwatson> https://launchpad.net/ubuntu/+source/ubiquity/+publishinghistory is the least confusing view despite being ugly
[18:28] <cjwatson> (and somewhat weird timestamp handling)
[18:28] <infinity> Right, but people land on the version page and it's blank is the complaint.
[18:28] <cjwatson> yeah
[18:28] <infinity> publishinghistory also requires a PhD in LP to read correctly the first time.  But at least it's accurate.
[18:28] <flocculant> ha ha ha
[18:28] <cjwatson> I'll have you know I'm merely Mr Watson
[18:29] <flocculant> oh my ... dad jokes :p
[18:29] <infinity> flocculant: Well, he does have 37 kids.
[18:29] <flocculant> :)
[18:37]  * davmor2 tries a netboot as everything else is broken :D
[18:38] <davmor2> cjwatson: elementary my dear Watson
[18:53] <wxl> pitti: welllll i'm finally out of my meeting. i'll check into it. thanks!
[18:54] <wxl> pitti: it's .45 we need right?
[19:02] <cyphermox> infinity: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1547630
[19:06] <cyphermox> ^ more for the oops factor than anything else, really
[19:07] <jibel> wxl, .46
[19:07] <davmor2> jibel, cyphermox: OMG OMG OMG OMG OMG OMG OMG OMG OMG OMG OMG neboot worked I have a xenial desktop installed \o/
[19:08] <jibel> davmor2, great, ship it
[19:08] <wxl> jibel: so a rebuild will get me that, right?
[19:09] <jibel> wxl, yes
[19:09] <wxl> jibel: thanks. sorry for being explicit but i want to be sure when i tell all the testers to jump XD
[19:10] <infinity> davmor2: That's some serious excitement.
[19:11] <davmor2> infinity: to date every install attempt and upgrade from trusty attempt has failed dismally
[19:11] <infinity> 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] <cyphermox> infinity: already on it
[19:12] <infinity> cyphermox: My hero.
[19:12] <cyphermox> fwiw, 14.04.4 isn't on the wiki on Releases either
[19:12] <cyphermox> I could only quickly find my Changes document.
[19:12] <wxl> aw crap i guess i didn't need to rebuild the d-i images :/
[19:13] <cyphermox> (and 14.04.5 isn't in the trusty release schedule)
[19:13] <wxl> cyphermox: yeah it would be nice to put it up there!
[19:14] <infinity> wxl: Clicking rebuild on the d-i images does nothing anyway.
[19:14] <wxl> um
[19:14] <wxl> images are marked as rebuilding on the tracker but nothing on lp https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/xenial/lubuntu
[19:14] <infinity> cyphermox: Yeah, I suppose I should put up tentative dates for 16.04.1 and 14.04.5 soon.
[19:15] <infinity> wxl: The cronjob that kicks them off runs every 5 minutes, patience.
[19:15]  * wxl breathes heavily
[19:15] <zequence> We have a rebuild requested, but I seem to remember it needs someone to start it manually. Is that right?
[19:16] <infinity> zequence: No, it should just magically happen.
[19:17] <zequence> infinity: Been a while now. A few hours. I accidentally marked the ISOs disabled first. Maybe that ruined it, somehow
[19:17] <zequence> I could cancel the rebuild, and try again
[19:17] <infinity> zequence: Well, I see a livefs building for you.
[19:17] <zequence> Oh, good
[19:18] <zequence> Ah, yes. I see now
[19:26] <cyphermox> infinity: https://code.launchpad.net/~mathieu-tl/debian-cd/kernel-cli-separator-trusty/+merge/287089
[19:28] <infinity> cyphermox: Ta.
[20:30] <wxl> yofel: darkxst: flexiondotorg_: we now have the ubiquity fix to end all fixes. you need me to rebuild for you?
[20:33] <darkxst> wxl, great! I just hit re-spin for ubuntu gnome
[20:33] <wxl> darkxst: triggered. i'll try to keep an eye out when they're done but i assume you're subscribed and get the notifications?
[20:33] <PaulW2U> wxl, flocculant looks good here on both laptops
[20:34] <flocculant> wxl: I just did kubuntu and mate
[20:34] <wxl> PaulW2U: good news. thanks for the confirm!
[20:34] <flocculant> PaulW2U: thanks \o/
[20:34] <wxl> flocculant: okie dokie
[20:34] <wxl> darkxst: oh wait, you said you hit re-spin. jesus. i need more coffee.
[20:49] <darkxst> wxl, yes I get notifications
[21:54] <flexiondotorg_> wxl, Yo
[21:54] <flexiondotorg_> wxl Thank you!
[21:54] <wxl> np buddy. thank you! if you get to feeling like playing with ppc'
[21:54] <flexiondotorg_> Just got in from a long day at work. So nice to find a new set of isos to test.
[21:54] <wxl> s, i'd love it
[21:55] <flexiondotorg_> wxl I tested Ubuntu MATE PowerPC last night.
[21:55] <flexiondotorg_> All good.
[21:55] <wxl> flexiondotorg_: well, i did mean lubuntu, but cool. :)
[21:55] <flexiondotorg_> It's late here. All I can manage is a smoke test of the new iso.
[21:55] <flexiondotorg_> I know you mean't Lubuntu :-)
[21:55] <wxl> XD
[21:55] <flexiondotorg_> Just letting you know PowerPC "works".
[21:55] <wxl> i aprpeciate it
[21:56] <flocculant> hi flexiondotorg_
[21:56] <flexiondotorg_> wxl I'll smoke test Lubuntu.
[21:57] <flexiondotorg_> Boot and quick install.
[21:57] <wxl> flexiondotorg_: thank you so much!
[21:57] <flexiondotorg_> By quick I mean an hout and a half ;-)
[21:57] <flexiondotorg_> flocculant, Yo
[21:58] <wxl> flexiondotorg_: mate's not been getting this, right? https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1547302
[21:58] <flexiondotorg_> wxl, Yes.
[21:58] <flexiondotorg_> But, I've been told is a new UI.
[21:58] <flexiondotorg_> So, the check only flag up if there is an issue.
[21:58] <wxl> flexiondotorg_: wait you are or are not?
[21:59] <flexiondotorg_> wxl.
[21:59] <flexiondotorg_> Sorry.
[21:59] <wxl> it's late, i know :)
[21:59] <flexiondotorg_> Just read that properly.
[21:59] <flocculant> flexiondotorg_: hang on - I think ^^ is a different issue to the one got marked invalid :)
[21:59] <flexiondotorg_> That is on my list to test, because I saw other flavours with it.
[21:59] <flexiondotorg_> Will test it in a sec.
[21:59] <wxl> k
[21:59] <wxl> cuz it's NOT in ubuntu
[22:00] <knome> wxl, please, "cuz" is not a word :)
[22:00] <wxl> knome: yes, and you didn't use a period at the end of your sentence or capitalize the initial letter so :þ
[22:01] <knome> wxl, Yes sir.
[22:01] <wxl> knome: you mean, "Yes, sir." XD
[22:01] <flexiondotorg_> wxl, You and I will have stuff to discuss on Monday :-)
[22:01] <knome> letz åll chenz to spi-king laik thiz
[22:02] <flexiondotorg_> h@z u g0tz w@R3z?
[22:03] <knome> haz meni torrent
[22:03] <wxl> flexiondotorg_: oooh i like the sound of that
[22:04]  * flexiondotorg_ l1K3z t0Rr3ntz
[22:04] <knome> I didn't know the user "wxl" used a screen reader.
[22:04] <wxl> ok, it's 4 in the morning there. now i understand why knome is being a poo poo butt. XD
[22:05] <wxl> er.
[22:05] <wxl> 4 minutes in the morning
[22:05]  * wxl sighs.
[22:05]  * wxl drinks more coffee
[22:06] <knome> tbe, it's midnight here, and the local time doesn't really have anything to do with how my digestion works
[22:12] <wxl> flocculant: you've already confirmed bug 1547302 does NOT affect xubuntu, correct?
[22:13] <flocculant> it didn't nope
[22:20] <flexiondotorg_> bug 1547302 does not appear to affect Ubuntu MATE.
[22:30] <amjjawad> wxl, are you around?
[22:30] <wxl> amjjawad: yes, sir?
[22:31] <flocculant> evening amjjawad
[22:31] <amjjawad> flocculant, hello :D how are you?
[22:31] <flocculant> or morning more likely :)
[22:31] <amjjawad> wxl, hi, you were right :D
[22:31] <wxl> oh jeez i don't think this bug should be against caspar
[22:31] <amjjawad> yep, it is 9:30am and I didn't have my breakfast yet
[22:31] <wxl> amjjawad: i put my feelers out and found out the truth. i was just passing it on :)
[22:32] <amjjawad> wxl, I took the battery out and you were right, it didn't show up however, I am sure we all know that was not a fix, just a workaround :D
[22:32] <wxl> amjjawad: yes but it's fixed now!
[22:32] <flocculant> amjjawad: that bug is fixed now
[22:32] <flocculant> hah
[22:32] <amjjawad> haha
[22:32] <wxl> amjjawad: 20160224.3
[22:32] <amjjawad> I just logged in so I'll test now and confirm ;)
[22:35] <amjjawad> http://launchpad.net/bugs/1547302 << I couldn't re-produce this bug
[22:36] <amjjawad> did anyone managed to re-produce it?
[22:36] <wxl> amjjawad: it's bare metal only afaik
[22:36] <wxl> amjjawad: interestingly it's only lubuntu/gnome, too
[22:36] <amjjawad> I see ...
[22:37] <amjjawad> that's explain why I could not see it on Oracle VB
[22:37] <wxl> right
[22:37] <wxl> so far that's the only vm i've confirmed it is not reproducible in but i have lots of bare metal reports, so it's a safe assumption at least some vms are out
[22:38] <wxl> maybe somehow it's how we deal with plymouth???
[22:39] <flocculant> I've not checked on hardware - can do now
[22:40] <wxl> oh!
[22:40] <wxl> did you test on bare mmetal flexiondotorg_ ??
[22:40] <flexiondotorg_> wxl, Not yet.
[22:41] <wxl> flexiondotorg_: flocculant: put you guys into the "TO BE TESTED" section of the description XD
[22:42] <flocculant> done - works
[22:42] <wxl> kthx
[22:43] <wxl> oops
[22:43] <flexiondotorg_> wxl, ?
[22:43] <wxl> flocculant: you got to come up with a new nick. you're too close to flexiondotorg_ :)
[22:43] <amjjawad> Sadly, I have no spare hardware to handle UG :(
[22:44] <wxl> flexiondotorg_: tl;dr let me know how the flavors works out :)
[22:44] <amjjawad> that is why I use VM
[22:44] <wxl> amjjawad: you have the hardware you're on, right?
[22:44] <amjjawad> I can't wxl this is my main
[22:44] <wxl> amjjawad: all you have to do is boot the iso and run the self check. no installation is needed
[22:44] <amjjawad> if this will be toasted, I'm dead.
[22:44] <amjjawad> Ah
[22:44] <amjjawad> I thought you mean testing the installation hehe
[22:44] <wxl> nonono
[22:44] <amjjawad> Yes, that I can do ;)
[22:45] <wxl> amjjawad: follow the STEPS TO REPRODUCE section XD
[22:46] <amjjawad> Hehe, yep ;)
[22:48] <flexiondotorg_> wxl, Couldn't get Lubuntu PowerPC Desktop to boot.
[22:49] <flexiondotorg_> going to try alternative.
[22:49] <wxl> aw crap
[22:51] <flocculant> done draft announcement - waiting on 3 for release notes is all \o/
[22:51] <flocculant> time for bed said zebedee ...
[23:06] <amjjawad> wxl, does UNetbootin re-produce this bug: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1547302 I made a boot-able USB with UNetbootin but it seems I am seeing a black screen only .. is this what I am suppose to see?
[23:19] <flexiondotorg_> flocculant, amjjawad wxl Are you still seeing LP: #990744 ?
[23:19] <flexiondotorg_> I was seeing that on yesterdays builds, but all seems fine now.
[23:19] <flexiondotorg_> Some flavours are still listing it as an issue. So wanted to check in.
[23:22] <amjjawad> flexiondotorg_, I didn't see it yet
[23:40] <flexiondotorg_> amjjawad, Thanks.
[23:46] <stgraber> qatracker is being updated now by Canonical IS, may be down for a few minutes (Drupal update)
[23:59] <stgraber> upgrade done