[01:19] <blahdeblah> Any ops around?  I would like to get upcoming mailing lists outage announced in topic.
[01:22] <valorie> blahdeblah: has the announcement been sent to the MLs themselves?
[01:23] <blahdeblah> valorie: All the mailing lists?  No.  I can't even imagine how painful that would be to organise.
[01:24] <Unit193> Any?
[01:24] <blahdeblah> It's been announced to the community council and the Canonical staff mailing list.
[01:25] <blahdeblah> And one of the ML moderators said he'd organise an announcement to ubuntu-users; not sure if that happened yet.
[01:27] <valorie> wow, that's such a tiny subset
[01:27] <valorie> ubuntu-devel at the very least I would say
[01:28] <sarnold> it would be nice to not receive fifty emails about it though :)
[01:28] <valorie> sure
[01:28] <blahdeblah> valorie: Hence why I'm asking around more than 48 hours in advance... ;-)
[01:28] <valorie> right -- but IMO the people who care the most are the ML subscribers
[01:29] <Unit193> sarnold: What if I forward it to you 30 times?
[01:29] <sarnold> Unit193: well, if _you_ do it.. <3
[01:34] <valorie> one thing I really do like about gmail is that if you get the same mail multiple times, it only shows up once, with all the other identical copies spread out below
[01:35] <Unit193> Unfortunate but so far those are private lists.
[07:29] <ouroumov> seb128, hello. I've had no responses following the mail I sent to -devel about bug 1700930
[07:43] <cpaelzer> rbasak: on the changes files adapted for SRU processing
[07:44] <cpaelzer> rbasak: I got no mail, IRC about them but they are still in queue
[07:44] <cpaelzer> rbasak: was that on trying to fix-up/finding out why the tools mean to close the totally wrong bug?
[07:44] <cpaelzer> rbasak: or is there anything I can/shall do to unblock?
[08:29] <tjaalton> doko: looks like the llvm5/gcc7 linking bug is resolved, so I'll bump mesa to use llvm5 in debian and then later also artful?
[08:33] <doko> tjaalton: could you make sure that we can demote llvm-4 for a?
[08:34] <tjaalton> doko: yep
[08:34] <doko> ta
[08:34] <doko> I'll bump doxygen
[08:46] <doko> Laney, seb128: please could the desktop team file a MIR for hunspell-dz?
[08:46] <seb128> k
[08:57] <doko> jamespage: https://bugs.launchpad.net/ubuntu/+source/defusedxml/+bug/1713264 needs copyright update
[09:06] <jamespage> doko: working that now
[09:37] <cjwatson> are the latest LXD images:ubuntu/artful/amd64 images known-broken?  looks like ifupdown is gone from them but they don't have adequate netplan configuration in place
[09:37] <cjwatson> so 'lxc launch images:ubuntu/artful/amd64 test && lxc exec test apt update' fails
[09:38] <cjwatson> I'm not sure where the image building logic lives
[09:41] <Odd_Bloke> cjwatson: I believe that stgraber owns the images: images, and we own the ubuntu: images.
[09:42] <cjwatson> there are no artful images in ubuntu:
[09:42] <cjwatson> (I'm trying to build an autopkgtest base image, so specifically need artful)
[09:43] <Odd_Bloke> "Ah, true, there will be in ubuntu-daily: though", he said, checking.
[09:43] <cjwatson> aha
[09:43] <cjwatson> thanks, let me see if those are healthier
[09:44] <Odd_Bloke> Yep, there they are.
[09:44] <cjwatson> and looks like the images: build scripts are in https://github.com/lxc/lxc-ci
[10:00] <blahdeblah> Mailing list & channel ops, please see the email I've just sent to ubuntu-devel-announce/ubuntu-users (or the earlier Canonical staff anouncement) and forward/update topics as necessary.
[10:12] <cjwatson> Odd_Bloke: ubuntu-daily:artful/amd64 indeed works, though only by virtue of still having ifupdown installed
[10:15] <cjwatson> still, might do me for now
[10:19] <zyga> cyphermox: hey, in case you have some more modem insight, on artful, there's no gui for the modem in network-manager anymore, I'm logged into the "ubuntu" session, is that expected?
[10:23] <Odd_Bloke> cjwatson: Yeah, we're currently wrestling with getting the ifupdown-free image to work in ScalingStack; testing there gates image publication.
[10:28] <cjwatson> Odd_Bloke: do you have a link to the relevant bits of build scripts?  I'm just working on an update to the lxc-ubuntu template
[10:30] <Odd_Bloke> cjwatson: https://git.launchpad.net/~cloudware/cloudware/+git/cpc_build_tools/tree/lxd_metadata <-- internal-only unfortunately, for Reasons(TM)
[10:32] <cjwatson> thanks
[10:45] <Unit193> slangasek: Thanks for the gifted patch to ruby-rbnacl!
[11:14] <Laney> ah
[11:14] <Laney> that'll be why the new autopkgtest lxd runners I tried to create don't work :-)
[11:18] <xnox> cjwatson, Odd_Bloke, Laney - do you mean https://github.com/lxc/lxc/pull/1770/files ?
[11:20] <xnox> Odd_Bloke, also that merge of devel into master looks odd; and is missing some of my commits =/
[11:22] <Odd_Bloke> xnox: "that merge"?
[11:23] <xnox> Odd_Bloke, hm, maybe i am reading things badly in that lxd_metadata script
[11:23] <xnox> Odd_Bloke, everything is fine, and i was looking at the wrong branch.
[11:23] <xnox> somehow thought that https://git.launchpad.net/~cloudware/cloudware/+git/cpc_build_tools/commit/?h=master&id=307b2aacfa744b156be4f76b8275fc1898b649fd went missing, but it is not
[11:24] <Odd_Bloke> :)
[11:27] <cjwatson> xnox: Yeah, I just noticed that :)
[11:28] <cjwatson> (and left a minor review comment to sync up with what I'd already done locally)
[11:30] <doko> jamespage: for #1713617, do you want to replace xclip by xsel?
[11:50] <sil2100> jbicha: hey! Could you please add the Regression Potential field to the description of the bug + fill in the Impact part for bug https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1708936 ?
[11:55] <jbicha> sil2100: I added a couple lines. I only filed the bug, I didn't fix it :)
[11:56] <xnox> cjwatson, $ cat /etc/network/if-up.d/openssh-server -> is something similar needed in netplan/networkd world? E.g. a udev rules file that triggers openssh-server reload?
[11:57] <xnox> or e.g. a unit that binds to something dynamic or some such?
[12:00] <sil2100> jbicha: thanks ;) Ok, I *guess* this is good enough - since the bug title does say the impact pretty well
[12:00] <xnox> cjwatson, we can have .path unit monitoring /run/systemd/network stuff and trigger openssh-server reloads.
[12:00] <jbicha> thanks
[12:19] <cjwatson> xnox: let's not perpetuate that; there's already talk that it may be sensible just to drop that, although it needs further investigation
[12:20] <xnox> ack
[12:40] <doko> cking: your xchat-gnome upload ftbfs
[12:41] <niedbalski> sil2100, ping re: LP:#1708305 , I did the verification for xenial/zesty, but just the zesty package was moved into -updates. Could you check the xenial one?
[12:42] <seb128> cking, that xchat-gnome upload is weird btw, you state in the changelog that it fixes a ftbfs like if the package was still in the archive but you are in fact adding it back, would have been nice to explain the rational of why the removal reasons are not valid anymore (it was deleted because it's unmaintained and superseeded by hexchat)
[12:44] <niedbalski> bdmurray, ^^ please
[12:50] <sil2100> niedbalski: hey! Let me check that
[12:53] <xnox> cking, yeah y no hexchat? =)
[12:53] <xnox> hexchat is awesome
[12:56] <sil2100> niedbalski: ok, now it's good for release, last time it didn't age long enough yet (was in -proposed for less than 7 days)
[12:57] <niedbalski> sil2100, aaah i see, ack. thank you.
[13:22] <slashd> rbasak, I heard the percona ppc64el bug in on your queue (LP: #1657256) ? Is that right ?
[13:23] <rbasak> slashd: yeah it's in my queue, but I'd be happy for anyone else to sponsor that too.
[13:24] <slashd> rbasak, Just for our information ... how far it is in your queue ? ;) Seems difficult to find a sponsor for percona especially for this bug.
[13:24] <slashd> tinoco, niedbalski ^
[13:30] <rbasak> Predicting my queue is a little difficult as the items vary in sizing massively. I'll try and get to it this week for you. Feel free to ping to remind me.
[13:30] <rbasak> As it will hopefully be a pretty quick task too. I'm just reluctant to context switch right now.
[13:31] <slashd> rbasak, sure thanks we appreciated it.
[13:31] <slashd> tinoco, niedbalski ^^^
[13:32] <niedbalski> slashd, rbasak thank you
[15:02] <ESphynx> hi guys, would there be a reason why 32 bit builds are failing?
[15:03] <cjwatson> ESphynx: I think you'll have to be a bit more specific
[15:04] <ESphynx> cjwatson: our i386 and armhf builds are failing and I was wondering why :P just realized it might actually be an endless loop, I didn't really understand the build log
[15:09] <ESphynx> yeah sorry... figured it out, our fault :P thanks.
[15:27] <doko> jamespage: fyi, defusedxml autopkg tests fail
[15:28] <doko> I only promoted the package in -proposed
[15:34] <jamespage> doko: ack
[15:34] <jamespage> tomorrow - just dealing with a libvirt issue with cpaelzer atm
[15:37] <stgraber> cjwatson: we have a pull request from xnox to try to fix that netplan mess, currently being reviewed
[15:37] <cjwatson> stgraber: yeah, I saw that eventually, thanks
[15:37] <xnox> stgraber, netplan tools and technology ;-)
[15:37] <xnox> not mess!
[15:38] <ogra_> the plan is in the name !
[15:39] <stgraber> xnox: well, the migration from ifupdown to netplan in artful has been a mess :)
[15:59] <slangasek> Unit193: ffi >_<
[21:06] <smoser> hey, anyone interested, i'd apprecate review of
[21:06] <smoser>  https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/330043
[21:07] <smoser> apw, ^ you having been last touched there, i'd appreciate your input