[01:04] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity-slideshow-ubuntu [source] (zesty-proposed) [125]
[02:45] -queuebot:#ubuntu-release- Unapproved: golang-1.6 (xenial-proposed/main) [1.6.2-0ubuntu5~16.04 => 1.6.2-0ubuntu5~16.04.2] (kubuntu, ubuntu-desktop)
[02:55] -queuebot:#ubuntu-release- Unapproved: golang-1.6 (yakkety-proposed/main) [1.6.3-1ubuntu1.1 => 1.6.3-1ubuntu1.2] (kubuntu, ubuntu-desktop)
[03:10] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Zesty Final] has been updated (20170412)
[03:10] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Zesty Final] has been updated (20170412)
[03:10] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Zesty Final] has been updated (20170412)
[03:10] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Zesty Final] has been updated (20170412)
[03:10] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Zesty Final] has been updated (20170412)
[03:10] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Zesty Final] has been updated (20170412)
[03:12] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Zesty Final] has been updated (20170412)
[03:12] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Zesty Final] has been updated (20170412)
[03:31] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Zesty Final] has been updated (20170412)
[03:31] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Zesty Final] has been updated (20170412)
[03:32] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Zesty Final] has been updated (20170412)
[03:32] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Zesty Final] has been updated (20170412)
[03:32] -queuebot:#ubuntu-release- Builds: Ubuntu Server i386 [Zesty Final] has been updated (20170412)
[03:32] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Zesty Final] has been updated (20170412)
[03:32] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Zesty Final] has been updated (20170412)
[03:33] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi2 [Zesty Final] has been updated (20170412)
[03:41] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Zesty Final] has been updated (20170412)
[03:41] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Zesty Final] has been updated (20170412)
[03:56] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop amd64 [Zesty Final] has been updated (20170412)
[03:56] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop i386 [Zesty Final] has been updated (20170412)
[03:57] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Zesty Final] has been updated (20170412)
[03:57] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop i386 [Zesty Final] has been updated (20170412)
[03:57] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Zesty Final] has been updated (20170412)
[03:57] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop i386 [Zesty Final] has been updated (20170412)
[04:07] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Zesty Final] has been updated (20170412)
[04:07] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Zesty Final] has been updated (20170412)
[04:07] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Zesty Final] has been updated (20170412)
[04:07] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Zesty Final] has been updated (20170412)
[04:08] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Zesty Final] has been updated (20170412)
[04:08] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Zesty Final] has been updated (20170412)
[04:15] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Zesty Final] has been updated (20170412)
[04:15] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD i386 [Zesty Final] has been updated (20170412)
[06:11] -queuebot:#ubuntu-release- Unapproved: gnss-sdr (zesty-proposed/universe) [0.0.9-3 => 0.0.9-4] (no packageset) (sync)
[06:11] -queuebot:#ubuntu-release- Unapproved: accepted gnss-sdr [sync] (zesty-proposed) [0.0.9-4]
[06:20] <ginggs> morning! would someone please 'force-badtest roary/all/armhf roary/all/s390x'  ?  it depends on bedtools, which is no longer built on those architectures
[06:26] <ginggs> also 'force-badtest pbgenomicconsensus/all/i386' - it depends on python-pbcore, which in turn depends on python-pysam which is no longer built there
[07:05] <rbalint> can i do something to lp:~rbalint/autopkgtest-cloud to get it merged? it unblocks mathicgb and botch to get in zesty
[07:07] <apw> rbalint, looking
[07:07] <apw> rbalint, have you proposed it for merging ?
[07:08] <apw> rbalint, and if so could you send me the url for the merge-request
[07:44] <rbalint> apw: thanks, i proposed now https://code.launchpad.net/~rbalint/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/322430
[08:02] <davmor2> Morning guys
[08:07] <sil2100> Morning
[08:08] <davmor2> sil2100, infinity: did everything that needed to land land and everything respin?
[08:10] <sil2100> davmor2: I think yes, Adam's not around here yet - he might now more in case he encountered something after work hours
[08:26] <infinity> davmor2: Barring install/boot critical bugs, I'm considering the current set final.
[08:26] <infinity> davmor2: So, find those critical bugs. :P
[08:26] <infinity> (Or, alternately, find that we don't have any?)
[08:36] <sil2100> I opt for not finding any
[08:40] <davmor2> sil2100: man it's me you know I'm gonna break it ;)
[08:40] <sil2100> Test with you eyes closed!
[08:41] <rbasak> [SRU] could someone glance at bug 1506427 please? I'm not sure how it ended up in trusty-proposed. I see no message about it (plus it doesn't appear to have been verified in trusty, but that's a separate matter)
[08:41] <davmor2> sil2100: I do how else do you expect me to test screenreader
[08:41] <davmor2> infinity: I'll start with one test of each today rather than concentrating on one I think
[09:01] <infinity> rbasak: sru-review/sru-accept won't comment if there's no bug task, and the trusty task was nominated but never accepted.
[09:02]  * infinity fixes that.
[09:07] <rbasak> Hmm
[09:08] <rbasak> I thought it would sort out the bug task automatically. Thanks.
[09:11] <davmor2> infinity, Laney: can one of you fire up i386 ab320064e2a11bbec19000c122886641 *zesty-desktop-i386.iso in live session I still have the crashed date-time indicator
[09:12] <sil2100> davmor2: on the final images? Could you check what version of indicator-datetime you have?
[09:13] <davmor2> sil2100: indicator-datetime 15.10+17.04.20170322-0ubuntu1
[09:13] <sil2100> davmor2: uh, that looks old
[09:14] <sil2100> davmor2: you should have 15.10+17.04.20170322-0ubuntu2
[09:14] <sil2100> davmor2: are you sure it's the latest image?
[09:14] <sil2100> Let me check the manifest
[09:16] <sil2100> davmor2: ok, so I see in the manifest that the latest image has indicator-datetime ubuntu2, so the correct one - you have to be using an older image
[09:17] <davmor2> sil2100: check the md5sum above mine locally matches it and it matches the image on the servers under current
[09:18] <sil2100> davmor2: no, it doesn't
[09:18] <sil2100> davmor2: ah, ok, you shouldn't use current
[09:18] <davmor2> http://cdimages.ubuntu.com/daily-live/current/MD5SUMS
[09:18] <sil2100> davmor2: you need to use 'pending'
[09:18] <sil2100> http://cdimage.ubuntu.com/ubuntu/daily-live/pending/
[09:18] <davmor2> sil2100: no we test from current
[09:18] <sil2100> This is the latest
[09:19] <davmor2> sil2100: it is what all the iso tracker tests point to ;)
[09:19] <davmor2> brb errand
[09:20] <sil2100> davmor2: that's what I see from the isotracker ;p http://iso.qa.ubuntu.com/qatracker/milestones/375/builds/145751/downloads
[09:20] <sil2100> Anyway, get the latest iso and check :)
[09:22] <infinity> davmor2: You're both wrong.  We don't test from current or pending, we test from the date directories that the tracker explicitly links to. :P
[09:26] <sil2100> I guess infinity's right, I also generally check the date directory but that's when I browse cdimage directly ;p Mostly because I always mixed up what current and pending mean
[09:28] <xnox> Laney, infinity: i've navigated to https://platform-qa-jenkins.ubuntu.com/job/ubuntu-zesty-desktop-i386-iso-download/ and I am logged in and I clicked "Build with Parameters" to trigger a brand new top level run, hopefully that should fetch the brand new ISO and trigger the rest of the jobs
[09:28] <xnox> i am logged in, and I think back in the day they gave me "rights"
[09:28] <xnox> but i may have powers
[09:28] <Laney> I want powers
[09:46] -queuebot:#ubuntu-release- Unapproved: cppformat (zesty-proposed/universe) [3.0.1+ds-1 => 3.0.1+ds-1ubuntu1] (no packageset)
[09:47] -queuebot:#ubuntu-release- Unapproved: accepted cppformat [source] (zesty-proposed) [3.0.1+ds-1ubuntu1]
[09:48] <davmor2> sil2100: thanks dude
[09:49] <sil2100> davmor2: xnox was looking into why the images didn't move by themselves to current
[09:49] <sil2100> He's running the jobs manually it seems
[09:50]  * davmor2 slaps Laney hand and tells him he is not a ranger
[09:50] <xnox> sil2100, right.
[09:50]  * xnox only (re)-trigger download job and thus downstream test jobs.
[09:50] <xnox> imho this was just waiting for the timer trigger.
[09:52] <xnox> sil2100, davmor2: i386 desktop did move to current now; and i've only just retriggered amd64 tests
[10:12] <flexiondotorg> Laney infinity Morning.
[10:12] <flexiondotorg> Interesting bug has surfaces in the 17.04 testing which might affect all flavours.
[10:13] <flexiondotorg> dnsmasq is not seeded, therefore connection sharing in Network Manager doesn't work.
[10:13] <flexiondotorg> https://bugs.launchpad.net/ubuntu-mate/+bug/1681912
[10:14] <flexiondotorg> Wondering how best to address this? Should flavours seed dnsmasq or should network-manager Recommends dnsmasq?
[10:14] <infinity> flexiondotorg: s/dnsmasq/dnsmasq-base/
[10:14] <infinity> flexiondotorg: But also it was dropped in favour of systemd-resolved.
[10:14] <flexiondotorg> Right, dnsmasq-base. But is this something each flavour should resolve in their seeds?
[10:15] -queuebot:#ubuntu-release- Unapproved: mtx (xenial-proposed/main) [1.3.12-9 => 1.3.12-9ubuntu<IP_ADDRESS>] (ubuntu-server)
[10:15] <infinity> flexiondotorg: No, I don't think seeding it is correct.
[10:16] -queuebot:#ubuntu-release- Unapproved: mtx (yakkety-proposed/main) [1.3.12-9 => 1.3.12-9ubuntu<IP_ADDRESS>] (ubuntu-server)
[10:16] <infinity> flexiondotorg: But this might need a larger discussion with, say, cyphermox.
[10:17] <davmor2> Yay no crash
[10:18] <infinity> flexiondotorg: Where does one find this sharing option?  Does it require a static interface?
[10:19] <infinity> flexiondotorg: Anyhow, we're also at a point where I'm not accepting anything that isn't install/boot-critical, so we can discuss today, but fixes would be in SRUs, IMO.
[10:19] <flexiondotorg> infinity I'll request the reporter provides more details...
[10:19] <infinity> You might also want to tell the reporter to remove dnsmasq, and just use -base.
[10:19] <infinity> The former wreaks havoc with other things like VPNs.
[10:19] <flexiondotorg> ack
[10:24] -queuebot:#ubuntu-release- Unapproved: libsbml (zesty-proposed/universe) [5.13.0+dfsg-1 => 5.13.0+dfsg-1ubuntu1] (no packageset)
[10:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Zesty Final] has been marked as ready
[10:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Zesty Final] has been marked as ready
[10:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Zesty Final] has been marked as ready
[10:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Zesty Final] has been marked as ready
[10:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Zesty Final] has been marked as ready
[10:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Zesty Final] has been marked as ready
[10:25] -queuebot:#ubuntu-release- Unapproved: accepted libsbml [source] (zesty-proposed) [5.13.0+dfsg-1ubuntu1]
[10:36] -queuebot:#ubuntu-release- Unapproved: pywavelets (zesty-proposed/universe) [0.5.1-1ubuntu1 => 0.5.1-1.1] (no packageset) (sync)
[10:36] -queuebot:#ubuntu-release- Unapproved: accepted pywavelets [sync] (zesty-proposed) [0.5.1-1.1]
[11:04] <davmor2> Laney, sil2100, infinity: so looking good on i386 now testing amd64 to make sure it didn't regress there
[11:04] <sil2100> davmor2: thanks!
[11:15] <davmor2> cyphermox, infinity: did you guys do something to the press enter to continue cause it is showing up now on i386 and amd64 \o/
[11:18] <flocculant> davmor2: I've always found that to be one of those sometimes you see it bugs ...
[11:19] <davmor2> flocculant: no I was hitting it always but now I'm not and cyphermox said he had an idea and might squeeze it in so I don't know if that happened
[11:19] <flocculant> :)
[11:27] <davmor2> sil2100: Laney infinity looking good on amd64 too
[11:27] <sil2100> Ship it!
[11:29] <davmor2> sil2100: hold your horses lots of other tests yet those were the basic ones :P
[11:35] <davmor2> D'oh ofcourse the enter dialogue appeared I was in livecd mode D'oh
[11:36] -queuebot:#ubuntu-release- Unapproved: freeciv (zesty-proposed/universe) [2.5.6-2 => 2.5.6-2ubuntu1] (no packageset)
[11:37] -queuebot:#ubuntu-release- Unapproved: accepted freeciv [source] (zesty-proposed) [2.5.6-2ubuntu1]
[11:43] <davmor2> Yeah so my no enter key bug is still valid :D
[11:44] <davmor2> Just my head not on completely straight for some reason
[12:06] <infinity> davmor2: Yeah, doubt that one's getting fixed this cycle.
[12:07] <davmor2> infinity: yeah thought it was fixed forgot I ran the live session to see if it was fixed in both live and installed
[12:10] <jbicha> I am installing Ubuntu GNOME zesty/amd64 and I clicked the box to install third-party software and it looks like the install is stuck at installing adobe-flashplugin, see also LP: #1682031
[12:11] <jbicha> chrisccoulson: ^
[12:12] <infinity> jbicha: Have an installer log that could shed some light?
[12:12] <jbicha> oh wait, it eventually did complete, it just took a long time
[12:18] <jbicha> it looks like it took 15 minutes to download updates including Flash LP: #1682107
[12:19] <jbicha> maybe I just need a better Internet connection?
[12:19] <infinity> There's a firefox in there, probably.
[12:19] <infinity> But 15m is pretty ick.
[12:34] <jbicha> it worked fine with i386, it might just have been my network being congested (I *was* zsyncing i386 in the background)
[12:51] -queuebot:#ubuntu-release- Unapproved: rejected munin [source] (trusty-proposed) [2.0.19-3ubuntu0.4]
[12:52] <jbicha> ok, I retried amd64 and it is *very* slowly downloading adobe-flashplugin
[12:57] <jbicha> Fetched 30.4MB in 5 min (101 kB/s)
[12:57] <infinity> Ouch.
[13:04] <ginggs> infinity: thanks for the previous force-badtests - htsjdk looks like uinstallable tests as well, but i can't see what
[13:07] -queuebot:#ubuntu-release- Unapproved: astroquery (zesty-proposed/universe) [0.3.4+dfsg-2 => 0.3.4+dfsg-2ubuntu1] (no packageset)
[13:07] <cyphermox> good morning
[13:07] <infinity> cyphermox: EVERYTHING IN THE INSTALLER IS BROKEN AND IT'S ALL YOUR FAULT.
[13:07] <cyphermox> is it?
[13:07] <infinity> No.
[13:07] -queuebot:#ubuntu-release- Unapproved: accepted astroquery [source] (zesty-proposed) [0.3.4+dfsg-2ubuntu1]
[13:08] <cyphermox> I knew it, only some things in the installer are broken and it's sometimes my fault
[13:08] <infinity> Yes, that.
[13:09] <wgrant> The slow Flash download is probably because we're being rather heavily hit by the update overnight.
[13:09] <wgrant> This is why we have mirrors for everything else :/
[13:10] <infinity> archive.c.c could certainly do with a mirror.
[13:10] <infinity> Or just a fatter link and a lot of RAM, since the entire mirror contents can probably be hot all the time.
[13:10] <infinity> s/mirror/archive/
[13:11] <jbicha> or is there a way that update could be better phased so we don't have everyone trying to get the file at the same time?
[13:12] <infinity> Could be.  But it's too late for this one.
[13:12] <infinity> Err, maybe could be.  If partner actually pays attention to extra overrides.
[13:13] <infinity> wgrant: ^-- Does NMAF do the right thing if we actually tried to phase partner?
[13:13] <wgrant> I'm not sure who many downloads are flashplugin-installer vs adobe-flashplugin
[13:13] <wgrant> infinity: It should.
[13:13] <infinity> Also that too.
[13:13] <infinity> The way we distribute flash is a cluster.
[13:13] <wgrant> (flashplugin-installer is multiverse, but pulls adobe-flashplugin from partner, for those unfamiliar with this particular specialness)
[13:14] <wgrant> infinity: Half of that sentence is redundant.
[13:14] <apw> heh
[13:17] <apw> interestingly i suspect that applied to both sentences equally
[13:17] <wgrant> Hah, indeed
[13:21] -queuebot:#ubuntu-release- Unapproved: profanity (zesty-proposed/universe) [0.5.0-0.1 => 0.5.0-0.1ubuntu1] (no packageset)
[13:22] -queuebot:#ubuntu-release- Unapproved: accepted profanity [source] (zesty-proposed) [0.5.0-0.1ubuntu1]
[13:28] <infinity> ginggs: It's because libngs-java only exists on x86.
[13:30] <ginggs> infinity: ah, thanks - will you force-badtest that too?
[13:30] <infinity> Yeah.
[13:31] <ginggs> infinity: thanks!
[13:36] -queuebot:#ubuntu-release- Unapproved: gnome-settings-daemon (zesty-proposed/main) [3.24.0-0ubuntu2 => 3.24.1-0ubuntu1] (ubuntu-desktop)
[13:38] <jbicha> what's the guideline for 0-day SRUs?
[13:39] <infinity> jbicha: Same as any other SRU.  But if it meets the combination of urgent and very obviously correct, we can push it out faster (again, like a regular SRU).
[13:40] <infinity> jbicha: So, basically, if it's the sort of SRU where you'd be comfy saying "Hey, Adam, can we push this out ASAP, it's urgent and super obvious to fix, and super easy to test that it's not broken", then yay 0-day.
[13:41] <jbicha> ok, I'm doing some 3.24.1 uploads that aren't needed in the release images
[13:43] <ginggs> rbalint: i triggered botch and mathicgb autopkgtests
[13:44] <rbalint> ginggs: thanks, i have just asked sil2100, too, to do that :-)
[13:45] <rbalint> ginggs: for the next release i have ambitious plan to keep the update_excuses list low :-)
[13:46] <infinity> rbalint: We all share that ambition.  It fades in time.
[13:46] <cjwatson> don't discourage them :)
[13:46] <infinity> Heh.
[13:46] <infinity> rbalint: Also, your pywavelets upload FTBFS on armhf.
[13:47] <infinity> rbalint: (alignment bug)
[13:47] <rbalint> infinity: maybe i'll buy some candys myself or others every day when the queue is short enough :-)
[13:48]  * rbalint checking pywavelets
[13:48] <infinity> rbalint: test_multidim.test_byte_offset ... Bus error (core dumped)
[13:48] <infinity> rbalint: Not at ALL suspicious that one would find an alignment bug in something called test_byte_offset.
[13:56] -queuebot:#ubuntu-release- Unapproved: gnome-control-center (zesty-proposed/universe) [1:3.24.0-0ubuntu1 => 1:3.24.1-0ubuntu1] (edubuntu, ubuntugnome)
[14:01] <rbalint> infinity: yes, it looks like alignment
[14:02] <rbalint> infinity: i suspect buildds use /proc/cpu/alignment=4  LP: #1516331 and Debian uses /proc/cpu/alignment setting of 2 (fixup) on armhf
[14:03] <infinity> rbalint: We definitely don't do fixups, yes.  I believe we discovered that arm64 kernels can't do it (we don't build on armv7 anymore)
[14:03] <rbalint> infinity: this is why we don't see FTBFS on Debian buildds, except for sparc64 which is picky: https://buildd.debian.org/status/package.php?p=pywavelets&suite=unstable
[14:04] <rbalint> infinity: looks like there are some unaligned issues to fix till tomorrow then :-)
[14:11] -queuebot:#ubuntu-release- Unapproved: gnome-photos (zesty-proposed/universe) [3.24.0-0ubuntu1 => 3.24.1-0ubuntu1] (desktop-extra, ubuntugnome)
[14:27] -queuebot:#ubuntu-release- Unapproved: rejected bluez [source] (xenial-proposed) [5.37-0ubuntu6]
[15:47] -queuebot:#ubuntu-release- Unapproved: bison (zesty-proposed/main) [2:3.0.4.dfsg-1 => 2:3.0.4.dfsg-1build1] (core)
[15:48] -queuebot:#ubuntu-release- Unapproved: dctrl-tools (zesty-proposed/main) [2.24-2 => 2.24-2build1] (core)
[15:48] -queuebot:#ubuntu-release- Unapproved: dh-exec (zesty-proposed/main) [0.23 => 0.23build1] (core)
[15:48] -queuebot:#ubuntu-release- Unapproved: gfxboot (zesty-proposed/main) [4.5.2-1.1-5 => 4.5.2-1.1-5build1] (core)
[15:49] -queuebot:#ubuntu-release- Unapproved: gobi-loader (zesty-proposed/main) [0.7-0ubuntu2 => 0.7-0ubuntu3] (ubuntu-desktop)
[15:49] -queuebot:#ubuntu-release- Unapproved: hfsutils (zesty-proposed/main) [3.2.6-13ubuntu1 => 3.2.6-13ubuntu2] (core)
[15:49] -queuebot:#ubuntu-release- Unapproved: hello (zesty-proposed/main) [2.10-1 => 2.10-1build1] (core)
[15:49] -queuebot:#ubuntu-release- Unapproved: ibmasm-utils (zesty-proposed/main) [3.0-1ubuntu11 => 3.0-1ubuntu12] (ubuntu-server)
[15:50] -queuebot:#ubuntu-release- Unapproved: ibus-sunpinyin (zesty-proposed/main) [2.0.3-5build2 => 2.0.3-5build3] (input-methods, ubuntu-desktop)
[15:50] -queuebot:#ubuntu-release- Unapproved: irda-utils (zesty-proposed/main) [0.9.18-14ubuntu1 => 0.9.18-14ubuntu2] (ubuntu-desktop)
[15:50] -queuebot:#ubuntu-release- Unapproved: joyent-mdata-client (zesty-proposed/main) [0.0.1-0ubuntu2 => 0.0.1-0ubuntu3] (ubuntu-cloud, ubuntu-server)
[15:50] -queuebot:#ubuntu-release- Unapproved: ipvsadm (zesty-proposed/main) [1:1.28-3 => 1:1.28-3build1] (ubuntu-server)
[15:50] -queuebot:#ubuntu-release- Unapproved: john (zesty-proposed/main) [1.8.0-2 => 1.8.0-2build1] (core)
[15:50] -queuebot:#ubuntu-release- Unapproved: lockfile-progs (zesty-proposed/main) [0.1.17 => 0.1.17build1] (ubuntu-server)
[15:50] -queuebot:#ubuntu-release- Unapproved: lupin (zesty-proposed/main) [0.57 => 0.57build1] (core)
[15:50] -queuebot:#ubuntu-release- Unapproved: lsscsi (zesty-proposed/main) [0.27-3 => 0.27-3build1] (ubuntu-server)
[15:51] -queuebot:#ubuntu-release- Unapproved: m2300w (zesty-proposed/main) [0.51-12 => 0.51-12build1] (ubuntu-server)
[15:51] -queuebot:#ubuntu-release- Unapproved: maas-enlist (zesty-proposed/main) [0.4+bzr38-0ubuntu2 => 0.4+bzr38-0ubuntu3] (ubuntu-server)
[15:51] -queuebot:#ubuntu-release- Unapproved: nicstat (zesty-proposed/main) [1.95-1 => 1.95-1build1] (ubuntu-server)
[15:51] -queuebot:#ubuntu-release- Unapproved: powertop (zesty-proposed/main) [2.8-1build1 => 2.8-1build2] (core)
[15:51] -queuebot:#ubuntu-release- Unapproved: mouseemu (zesty-proposed/main) [0.16-0ubuntu9 => 0.16-0ubuntu10] (core)
[15:52] -queuebot:#ubuntu-release- Unapproved: opensp (zesty-proposed/main) [1.5.2-13ubuntu1 => 1.5.2-13ubuntu2] (ubuntu-desktop)
[15:52] -queuebot:#ubuntu-release- Unapproved: quota (zesty-proposed/main) [4.03-2 => 4.03-2build1] (core)
[15:52] -queuebot:#ubuntu-release- Unapproved: tmispell-voikko (zesty-proposed/main) [0.7.1-4 => 0.7.1-4build1] (ubuntu-desktop)
[15:52] -queuebot:#ubuntu-release- Unapproved: tinycdb (zesty-proposed/main) [0.78 => 0.78build1] (ubuntu-desktop, ubuntu-server)
[15:53] -queuebot:#ubuntu-release- Unapproved: uucp (zesty-proposed/main) [1.07-23 => 1.07-23build1] (core)
[16:20] -queuebot:#ubuntu-release- Unapproved: python-tx-tftp (zesty-proposed/main) [0.1~bzr42-0ubuntu2 => 0.1~bzr47-0ubuntu1] (ubuntu-server)
[16:23] -queuebot:#ubuntu-release- Unapproved: apt-xapian-index (zesty-proposed/universe) [0.47ubuntu12 => 0.47ubuntu13] (kubuntu)
[16:29] <slashd> For SRU, There is a patch for sssd pkg via LP#1566508 in trusty upload queue [https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text=sssd] uploaded on 2017-03-29. We were wondering if one of you could please have a look at it in order to review/build it into -proposed if this pass all the necessary validation of course. I currently don't see any sssd pkg already in -proposed that could possibly block the
[16:29] <slashd> process.
[16:32] <nacc> slashd: does it just need sponsoring?
[16:33] <nacc> oh wait, it's sponsored but not reviewed, i see
[16:33] <slashd> nacc exactly
[16:33] <nacc> slashd: i think rbasak was on sru today, his time
[16:34] <nacc> slashd: but not sure
[16:34] <bdmurray> Is anybody looking at bug 1681566?
[16:35] <nacc> bdmurray: is the underlying issue that the dkms trigger isn't seeing the new kernel for some reason?
[16:35] <bdmurray> nacc: maybe?
[16:35] <nacc> bdmurray: i'm grabbing the logs to see
[16:37] <bdmurray> slashd: Why did the patch names change from .patch to .diff?
[16:39] <slashd> bdmurray, looking
[16:40] <nacc> bdmurray: confusing from the original log -- i see nvidia-375.39-0ubuntu5 get installed and it says "REmoving all DKMS modules" .. then i see linux-image-generic-4.10.0-19-generic get installed and the dkms trigger runs ... and runs again with linux-headers-4.10.0-19-generic, linux-image-extra..., then a new dkms get installed, then the nvidia-375 driver installs, and seems to only run for the
[16:40] <nacc> running kernel
[16:40] <nacc> i wonder if the hook is wrong in the new driver?
[16:41] <slashd> bdmuarray, seems like there is a mixed of both in d/p (.diff and .patch), which probably confuse the creator of the patch (note that I haven't look the patch nor sponsor it myself).
[16:41] <slashd> bdmurray^
[16:43] <bdmurray> slashd: it also introduces a bunch of noise into the diff for us to review.
[16:43] <slashd> vtapia, can you answer bdmurray since you are the patch submitter ^^
[16:44] <vtapia> hey, I used diff
[16:45] <vtapia> after discussing this with tjaalton, to keep track of the patches in pkg-sssd
[16:46] <slashd> bdmurray ^
[16:46] <bdmurray> But why were the existing patches renamed from .patch to .diff?
[16:48] <vtapia> let me check, please
[16:54] -queuebot:#ubuntu-release- Unapproved: gbrowse (zesty-proposed/universe) [2.56+dfsg-2 => 2.56+dfsg-2ubuntu1] (no packageset)
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted gbrowse [source] (zesty-proposed) [2.56+dfsg-2ubuntu1]
[17:00] <rbasak> I did glance at sssd but it looked very confusing so I skipped past in order to make progress.
[17:00] <nacc> rbasak: :)
[17:01] <bdmurray> rbasak: because of the patch renaming right?
[17:01] <rbasak> Previous changelog entries edited IIRC etc
[17:01] <bdmurray> We should just reject it then.
[17:01] <bdmurray> If two of us have skipped it.
[17:02] <vtapia> hmmm
[17:02] <vtapia> so those changes are already in -updates
[17:02] <rbasak> That and some verifications already done but the Trusty upload pending, so it seemed a bit involved to untangle it
[17:02] <rbasak> sssd appears in pending-sru
[17:03] <bdmurray> rbasak: that's for xenial
[17:03] <nacc> for non-trusty
[17:03] <bdmurray> vtapia: in -updates for what?
[17:03] <rbasak> Sure, but that's what I meant by confusing. I'd want to unravel all of that in my head to make sure everything's straight before touching anything
[17:03] <vtapia> the patch renaming bdmurray
[17:04] <bdmurray> vtapia: Where does the patch renaming exist in -updates?
[17:04] <rbasak> And if I'm going to reject, I prefer to make it really clear what needs to be done to make progress instead, and that was going to take longer to figure out, so I moved on to some easier ones
[17:04] <rbasak> Anyway I'm pretty much EOD now, so shall I leave this to bdmurray?
[17:04] <bdmurray> Sure
[17:05] <rbasak> If it's still outstanding tomorrow, ping me and I'd be happy to go through it in realtime if somebody has the patience.
[17:05] <rbasak> bdmurray: thanks!
[17:05] <vtapia> sorry bdmurray, I'm completely mistaken
[17:05] <bdmurray> Part of my point is this is taking a lot of time / patience because the diff is wacky.
[17:07] <rbalint> infinity: i think the problem with pywavelets is actually in numpy:
[17:07] <rbalint> infinity: import numpy as np; np.dtype([('ddata', 'float32'),('pad', 'byte')]).alignment
[17:07] <rbalint> infinity: 1
[17:08] <bdmurray> vtapia: To be absolutely clear this is what makes no sense to me. http://pastebin.ubuntu.com/24368576/ lines 16,17 and lines 25,26
[17:09] <vtapia> I see what I did, please reject the SRUs
[17:09] -queuebot:#ubuntu-release- Unapproved: accepted bison [source] (zesty-proposed) [2:3.0.4.dfsg-1build1]
[17:11] -queuebot:#ubuntu-release- Unapproved: rejected sssd [source] (trusty-proposed) [1.11.8-0ubuntu0.6]
[17:11] <bdmurray> vtapia: Done, if you need something sponsored feel free to ping me.
[17:11] <vtapia> thanks a lot bdmurray, and sorry for this
[17:11] <slashd> rbasak, bdmurray, tks for your quickly jumping on it
[17:14] -queuebot:#ubuntu-release- Unapproved: rejected dctrl-tools [source] (zesty-proposed) [2.24-2build1]
[17:18] -queuebot:#ubuntu-release- Unapproved: accepted dh-exec [source] (zesty-proposed) [0.23build1]
[17:23] -queuebot:#ubuntu-release- Unapproved: python-tx-tftp (zesty-proposed/main) [0.1~bzr42-0ubuntu2 => 0.1~bzr47-0ubuntu1] (ubuntu-server)
[17:25] -queuebot:#ubuntu-release- Unapproved: rejected gfxboot [source] (zesty-proposed) [4.5.2-1.1-5build1]
[18:22] <bdmurray> infinity/slangasek: I think bug 1681566 is a problem with dkms in general.
[18:22] <nacc> bdmurray: agreed based upon your last comment, someting seems wrong with the hook
[18:23] <bdmurray> I'm not familiar with that package though.
[18:24] -queuebot:#ubuntu-release- Unapproved: accepted gobi-loader [source] (zesty-proposed) [0.7-0ubuntu3]
[18:26] <jbicha> buffer 2
[18:26] <infinity> bdmurray: Not fixing it on images (which is fine, cause upgrades tend to be from the network), but I can have a look tomorrow if no one else has.
[18:27] <bdmurray> infinity: What should I look at in the package?
[18:28] <infinity> bdmurray: I'd start with seeing if xenial->yakkety had the same upgrade issue.  If not, then diff yakkety->zesty versions and poke around.
[18:29] <nacc> bdmurray: if you want me to, i can import dkms so you have a git tree to look at for seeing the changes
[18:29] <infinity> bdmurray: So, uhm.  I dunno.  I didn't have a killer "look at this bit" in mind, I've just played with it a lot in the ast.
[18:29] <infinity> s/ast/past/
[18:31] <nacc> bdmurray: when you're in that broken state (where dkms hasn't built the module for the 17.04 kernel), i wonder if you can try to run dkms manually with various optoins to see if you can get it to build
[18:34] -queuebot:#ubuntu-release- Unapproved: accepted hello [source] (zesty-proposed) [2.10-1build1]
[18:38] -queuebot:#ubuntu-release- Unapproved: accepted hfsutils [source] (zesty-proposed) [3.2.6-13ubuntu2]
[18:39] <nacc> bdmurray: sorry, lappy hung up when i reconnected to my monitor -- let me know if you did want an import or if i can help at all
[18:40] <bdmurray> "an import"?
[18:40] <slashd> bdmurray, FYI vtapia changed the "v-d" tag to "v-f" for the 2 bugs related to sssd (LP#1566508 & LP#1669712) for releases where the existing patch has been mistakenly renamed. He will correct and re-submit later. I just want to make sure you are aware.
[18:40] <nacc> bdmurray: the server team's git importer
[18:40] <nacc> bdmurray: will import the published history for dkms into a git tree, so you can git {blame, log}, etc files to see what was changed when
[18:41] -queuebot:#ubuntu-release- Unapproved: accepted ibmasm-utils [source] (zesty-proposed) [3.0-1ubuntu12]
[18:41] <nacc> bdmurray: given you only are looking at what's in zesty, you may not need it to figure out the issue :)
[18:43] -queuebot:#ubuntu-release- Unapproved: multipath-tools (zesty-proposed/main) [0.6.4-3ubuntu3 => 0.6.4-3ubuntu4] (core)
[18:44] -queuebot:#ubuntu-release- Unapproved: accepted ibus-sunpinyin [source] (zesty-proposed) [2.0.3-5build3]
[18:45] -queuebot:#ubuntu-release- Unapproved: rejected ipvsadm [source] (zesty-proposed) [1:1.28-3build1]
[18:46] -queuebot:#ubuntu-release- Unapproved: accepted irda-utils [source] (zesty-proposed) [0.9.18-14ubuntu2]
[18:54] -queuebot:#ubuntu-release- Unapproved: rejected lsscsi [source] (zesty-proposed) [0.27-3build1]
[18:54] -queuebot:#ubuntu-release- Unapproved: rejected lockfile-progs [source] (zesty-proposed) [0.1.17build1]
[18:55] -queuebot:#ubuntu-release- Unapproved: rejected lupin [source] (zesty-proposed) [0.57build1]
[18:57] -queuebot:#ubuntu-release- Unapproved: accepted john [source] (zesty-proposed) [1.8.0-2build1]
[18:58] -queuebot:#ubuntu-release- Unapproved: rejected maas-enlist [source] (zesty-proposed) [0.4+bzr38-0ubuntu3]
[18:58] -queuebot:#ubuntu-release- Unapproved: rejected mouseemu [source] (zesty-proposed) [0.16-0ubuntu10]
[18:59] -queuebot:#ubuntu-release- Unapproved: rejected quota [source] (zesty-proposed) [4.03-2build1]
[19:01] -queuebot:#ubuntu-release- Unapproved: rejected uucp [source] (zesty-proposed) [1.07-23build1]
[19:04] -queuebot:#ubuntu-release- Unapproved: rejected joyent-mdata-client [source] (zesty-proposed) [0.0.1-0ubuntu3]
[19:04] -queuebot:#ubuntu-release- Unapproved: ampliconnoise (zesty-proposed/universe) [1.29-6 => 1.29-6ubuntu1] (no packageset)
[19:05] -queuebot:#ubuntu-release- Unapproved: accepted ampliconnoise [source] (zesty-proposed) [1.29-6ubuntu1]
[19:05] -queuebot:#ubuntu-release- Unapproved: accepted m2300w [source] (zesty-proposed) [0.51-12build1]
[19:08] -queuebot:#ubuntu-release- Unapproved: accepted nicstat [source] (zesty-proposed) [1.95-1build1]
[19:08] -queuebot:#ubuntu-release- Unapproved: rejected tinycdb [source] (zesty-proposed) [0.78build1]
[19:09] -queuebot:#ubuntu-release- Unapproved: accepted opensp [source] (zesty-proposed) [1.5.2-13ubuntu2]
[19:11] -queuebot:#ubuntu-release- Unapproved: accepted powertop [source] (zesty-proposed) [2.8-1build2]
[19:13] -queuebot:#ubuntu-release- Unapproved: accepted tmispell-voikko [source] (zesty-proposed) [0.7.1-4build1]
[19:15] -queuebot:#ubuntu-release- Unapproved: rejected python-tx-tftp [source] (zesty-proposed) [0.1~bzr47-0ubuntu1]
[19:15] <slangasek> cyphermox: multipath-tools upload in queue, are you expecting this in the final images?
[19:17] <slangasek> also, er, somehow this bug is marked fix-released in zesty
[19:28] <cyphermox> wat
[19:28] <cyphermox> no, I'm expecting this as a SRU
[19:28] <cyphermox> if we can sneak it in, all good, but I don't think it's that critical
[19:30] <slangasek> ok
[19:30] <slangasek> cyphermox: want to put an SRU template on the bug then? :)
[19:30] <cyphermox> yes, getting to it
[19:30] <cyphermox> I'm in a one on one right now
[19:35] <bdmurray> priorities
[19:40] <cyphermox> bdmurray: I know, but slangasek already has a dedicated priority queue.
[19:41] <slangasek> infinity: why bump z3c.rml / schooltool to -proposed now, vs. leaving python-pypdf around for a bit?
[19:41] <cyphermox> slangasek: can you please reject the multipath-tools upload? seems like it's pointing to the wrong bug anyway
[19:42] <slangasek> cyphermox: ack
[19:42] <slangasek> done
[19:43] -queuebot:#ubuntu-release- Unapproved: rejected multipath-tools [source] (zesty-proposed) [0.6.4-3ubuntu4]
[19:48] <cyphermox> infinity: same as yesterday but for today; any issue came up in iso testing (but isn't on iso.qa.u.c) that I should look at in priority?
[19:49] <cyphermox> I had a quick look at UbuntuKylin bugs, but they pretty much all seem to be in ukui-control-center or something
[19:49] -queuebot:#ubuntu-release- Unapproved: multipath-tools (zesty-proposed/main) [0.6.4-3ubuntu3 => 0.6.4-3ubuntu4] (core)
[20:03] <slangasek> infinity: sorry, ignore question re: z3c.rml / schooltool, this was clearly my fault for removing python-pypdf back in Feb while it still had revdeps
[20:19] <jackpot51> Is today's daily ISO the release?
[20:19] <slangasek> not until it's been released
[20:19] <jackpot51> Does it feel like it will?
[20:20] -queuebot:#ubuntu-release- Unapproved: zimlib (zesty-proposed/universe) [1.4-2 => 1.4-2ubuntu1] (no packageset)
[20:21] <cyphermox> jackpot51: if you have time, you can help testing: http://iso.qa.ubuntu.com/qatracker/milestones/375/builds
[20:21] <jackpot51> Definitely do
[20:21] <slangasek> g++ -shared [...] -o libvp
[20:21] <slangasek> x.so.4.1.0
[20:21] <slangasek> [...]
[20:21] -queuebot:#ubuntu-release- Unapproved: accepted zimlib [source] (zesty-proposed) [1.4-2ubuntu1]
[20:21] <slangasek> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/Scrt1.o: In function `_start':
[20:21] <slangasek> (.text+0x20): undefined reference to `main'
[20:22] <slangasek> good job
[20:24] <cyphermox> o.O?
[20:24] <slangasek> no idea :)
[20:24] <cyphermox> hehe
[20:26] <slangasek> jbicha: I see you synced zeroinstall-injector, which FTBFS because of wrong link order (Ubuntu's default of -Wl,--as-needed, which is not used in Debian - https://wiki.ubuntu.com/ToolChain/CompilerFlags#A-Wl.2C--as-needed).  Is that something you'd want to follow up on with Debian?
[20:26] <jackpot51> cyphermox: Which test cases do you need?
[20:27] <slangasek> jackpot51: https://iso.qa.ubuntu.com
[20:27] <cyphermox> jackpot51: take your pick, priority to those that aren't fully tested (not 5/5 or whatever)
[20:29] -queuebot:#ubuntu-release- Unapproved: zeroinstall-injector (zesty-proposed/universe) [2.12-3 => 2.12-4] (no packageset) (sync)
[20:29] <jbicha> slangasek: let's try this version ^ (all I did last month was sync a newer version on top of the already existing autosynced ftbfs)
[20:29] -queuebot:#ubuntu-release- Unapproved: accepted zeroinstall-injector [sync] (zesty-proposed) [2.12-4]
[20:30] <slangasek> jbicha: any reason to expect that one to work better, given that it's an Ubuntu-specific build failure?
[20:31] -queuebot:#ubuntu-release- Unapproved: gjs (zesty-proposed/universe) [1.48.0-0ubuntu1 => 1.48.1-0ubuntu1] (desktop-extra, mozilla, ubuntugnome)
[20:33] <cyphermox> jackpot51: it's getting increasingly late to fix things, but you might want to have a good look at OEM-mode installs, I know you care about those :)
[20:33] <jackpot51> I will
[20:34] <jackpot51> Thanks cyphermox! I will fill out the OEM install test then
[20:36] <jbicha> slangasek: it worked https://launchpad.net/ubuntu/+source/zeroinstall-injector/2.12-4
[20:36] <slangasek> jbicha: ok then :)
[20:38] <jbicha> the maintainer was subscribed to Ubuntu bugs for his package which is always nice :)
[20:40] -queuebot:#ubuntu-release- Unapproved: gnome-desktop3 (zesty-proposed/main) [3.24.0-0ubuntu1 => 3.24.1-0ubuntu1] (ubuntu-desktop)
[20:41] <ginggs> rbalint: around?
[20:42] <rbalint> ginggs: yes :-)
[20:43] <ginggs> kodi-visualization-spectrum should build if you change DEB_BUILD_MAINT_OPTIONS = hardening=+all -> +all,-pie
[20:45] <ginggs> rbalint: yes it does, just built in my PPA
[20:45] <ginggs> shall I upload?
[20:50] <jackpot51> http://iso.qa.ubuntu.com/qatracker/milestones/375/builds/145748/testcases/1305/results
[20:50] <jackpot51> Tested it, OEM config looks great on Ubuntu
[20:59] <jackpot51> I still can crash the installer with WPA 2 enterprise cyphermox :P
[20:59] <cyphermox> yes
[21:00] <jbicha> jackpot51: stop crashing the installer! ;)
[21:02] <rbalint> ginggs: thanks!
[21:02] <jackpot51> Sorry!
[21:05] <rbalint> ginggs: yes, please upload this should be ok
[21:06] <ginggs> rbalint: done
[21:06] -queuebot:#ubuntu-release- Unapproved: kodi-visualization-spectrum (zesty-proposed/universe) [1.1.1-1 => 1.1.1-1ubuntu1] (no packageset)
[21:07] -queuebot:#ubuntu-release- Unapproved: accepted kodi-visualization-spectrum [source] (zesty-proposed) [1.1.1-1ubuntu1]
[21:16] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Zesty Final] has been marked as ready
[21:16] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop i386 [Zesty Final] has been marked as ready
[21:45] -queuebot:#ubuntu-release- Unapproved: gnome-shell (zesty-proposed/universe) [3.24.0-0ubuntu2 => 3.24.1-0ubuntu1] (desktop-extra, edubuntu, mozilla, ubuntugnome)
[21:57] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Zesty Final] has been marked as ready
[21:57] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Zesty Final] has been marked as ready
[21:57] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Zesty Final] has been marked as ready
[21:57] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Zesty Final] has been marked as ready
[21:58] <jackpot51> Where is my Ubuntu Desktop amd64 [Zesty Final] ?
[21:58] <jackpot51> Make it happen! :)
[22:05] -queuebot:#ubuntu-release- Unapproved: mutter (zesty-proposed/universe) [3.24.0-0ubuntu1 => 3.24.1-0ubuntu1] (desktop-extra, edubuntu, ubuntugnome)
[22:46] <bdmurray> infinity: laney has a potential fix attached to bug 1681566
[22:48] <infinity> jackpot51: It's not Thursday.
[22:49] <jackpot51> It is in some places ;-)
[22:50] <infinity> bdmurray: Seems potentially reasonable.  I can look with fresher eyes in the morning.
[22:51] <infinity> jackpot51: It's not sufficiently Thursday for people to be bugging us about the release.
[22:51] <infinity> jackpot51: (You may think it's cute and funny until you realize that we have millions of users, thousands of whom know how email and IRC work, and hundreds of whom think that's a fun thing to use it for)
[22:53] <cyphermox> bdmurray: looks elegant
[22:56] <jackpot51> Oy vey. infinity: I've been in this too, just ask cyphermox. I'm helping where I can
[22:56] <jackpot51> Going home, will be back in to bug in 18 hours
[22:58] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Zesty Final] has been marked as ready
[22:58] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Zesty Final] has been marked as ready
[23:00] <tsimonq2> infinity: Will there be another global respin, or are we done?
[23:00] <infinity> tsimonq2: We look pretty done, but I make no promises until it ships.
[23:01] <flexiondotorg> See you later this morning infinity :-)
[23:02] <tsimonq2> infinity: That's fair to say (I get that last minute things sometimes happen), I just wanted to make sure that nobody was sitting on $something-important until now.
[23:02] <tsimonq2> infinity: Thanks for letting me know.
[23:16] <cyphermox> tsimonq2: the big bad bugs should be showing up on the iso.qa dashboard
[23:17] <cyphermox> there are some bugs open showing up there, but there has been for every release (AFAIK) and it doesn't look like any translates to "omg the world is on fire"
[23:17] <cyphermox> that said, not everything is fully tested either, can you help on some of those?
[23:35] <tsimonq2> cyphermox: Have anything in mind, or just "Go Do"?
[23:36] <cyphermox> I have weird results trying to test the OEM-config mode for Kubuntu, maybe you can try that, let me know if it works well for you
[23:36] <cyphermox> I keep hitting a blank screen, not sure whether it's my system or the image.
[23:37] <tsimonq2> cyphermox: Any specific steps you want me to take besides what's on the tracker?
[23:37] <cyphermox> nope, that should be the steps
[23:39] <wxl> cyphermox: i've had that problem before. and other times, not.
[23:39] <cyphermox> could just be that I'm giving the VM too little memory, I suppose
[23:39] <tsimonq2> cyphermox: OK, getting the ISO now.
[23:39] <wxl> yeah i only had it in vms
[23:39] <wxl> and admittedly i tend to kind of strangle my vms for resources :)
[23:40] <tsimonq2> wxl: I'd be testing with a spare hard drive on this 16 GB, 6-core machine, I shouldn't have any resource restrictions here. :P
[23:40] <tsimonq2> (and if I do, welllll that's a problem :P)
[23:40] <cyphermox> I just let virt-manager do its thing there, I didn't bother using my scripts for vms for this one
[23:40] <wxl> i've seen this https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1561745
[23:40] <cyphermox> that should translate to 1G
[23:41] <cyphermox> ugh, seriously?
[23:41] <wxl> but this is the main one we were using for tracking https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/1638473
[23:42] <tsimonq2> cyphermox: Before I reboot, anything bad on Lubuntu?
[23:42] <tsimonq2> Or are we Clear For Launch there?
[23:42] <cyphermox> I don't know
[23:42] <cyphermox> Lubuntu looks decent, but I don't make the go/no-go decisions
[23:43] <cyphermox> think of me like a I'm testing monkey; I just test the things and occasionally eat bugs.
[23:43] <tsimonq2> cyphermox: Then I'm asking with your testing monkey hat on. :P
[23:44] <tsimonq2> (because I'm the guy who makes the go/no-go decisions for Lubuntu now)
[23:44] <cyphermox> judging from the dashboard, lubuntu is tested, and marked ready already.
[23:44] <tsimonq2> Because I did that. :P
[23:45]  * tsimonq2 goes with "cyphermox> Lubuntu looks decent..."
[23:46] <cyphermox> tsimonq2: to be clear, I did *not* personally run a Lubuntu image today; I can only make a general observation based on the bugs showing on the dashboard.
[23:48] <tsimonq2> Apologies for the confusion here, I don't think I've been clear, what my real question is is this: Are there any low-level overarching issues or anything in Lubuntu that you've found that I should be concerned about?
[23:48] <cyphermox> I don't think so, but like I said, i didn't test lubuntu at all for this image.
[23:49] <tsimonq2> Ok, thank you. Sorry again, I wasn't clear with what I was asking. :)
[23:50] <tsimonq2> cyphermox: If you could, I would absolutely appreciate it (as a just-in-case thing). I can pay in beer if I ever see you at a conference. ;)
[23:50] <wxl> you'd have to be old enough XD
[23:50] <valorie> totally not possible for you to legally buy cyphermox beer!
[23:50] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (zesty-proposed/main) [2.440 => 2.441] (desktop-core)
[23:50] <wxl> hahhahahah
[23:50] <wxl> jinx :)
[23:50] <valorie> but I'll cover it.....
[23:51] <cyphermox> slangasek: ^
[23:51] <cyphermox> re: livecd-rootfs.
[23:51] <slangasek> cyphermox: thanks; hands full right now but I'll look in a bit
[23:51] <cyphermox> no problem
[23:52] <cyphermox> tsimonq2: ok, coming up
[23:52] <tsimonq2> wxl: My point in that being, the chances of me seeing cyphermox are low enough that I probably won't see him until I'm 21+ ;)
[23:52] <tsimonq2> (if at all, as much as I love y'all, I won't see *everyone* at a conference...)
[23:53] <tsimonq2> cyphermox: Thank you. :)
[23:53] <cyphermox> seems like I broke keyboard-detection
[23:54] <cyphermox> broke as in "manage to trick it into thinking of the wrong keyboard"
[23:54]  * tsimonq2 goes AFK for 10-20 mins to do some room cleaning, by the time I'm back, ISO should be done...
[23:55] <tsimonq2> s/ISO/ISO downloading/
[23:55] <cyphermox> oh, it's because I can't read.
[23:56] <tsimonq2> cyphermox: PEBKAC is exactly why I sometimes spit internal brain logs verbosely into a channel (can't think of a better way to word that, and that sounds pretty cool :P)
[23:56] <slangasek> that's fine; keyboard-detection is for writing, not for reading
[23:57] <cyphermox> is that why everything always starts with qwerty?
[23:58] <cyphermox> or .,somethingsomethign for yu.
[23:58] <tsimonq2> Dvorak <3 - I'd use it if I had the motor skills to learn it :P