[06:25] <cpaelzer> good morning
[07:00] <pitti> Good morning
[07:00] <cpaelzer> hi pitti, welcome to the new week
[07:00] <pitti> hey cpaelzer, wie gehts?
[07:01] <cpaelzer> pitti: mal wieder das Montags-Grauen wenn man soertiert was die Woche anstehen sollte, aber Gut :-)
[07:01] <cpaelzer> pitti: Ich hoffe bei Dir ists auch nciht schlimmer wie sonst
[07:02]  * cpaelzer is no motivation genius this week :-)
[07:03] <pitti> cpaelzer: I just went back to bed :-P
[07:03] <cpaelzer> pitti: then you shouldn't reply here right?
[07:03] <pitti> cpaelzer: nah, alright, we had a nice weekend and now off into the ping/email backlog
[07:03] <cpaelzer> k, so same as me
[07:04] <cpaelzer> pitti: except I expect your backlog to be a magnitude bigger
[07:05] <pitti> certainly not a magnitude -- it can't be bigger than what I can do in a day :)
[07:05] <pitti> ginggs: right, some package already dropped the upstart jobs, so syncing/dropping them to reduce delta seems fine to me
[07:06] <pitti> ginggs: and anythign > xenial can't boot with upstart anyway as it's gone
[07:25] <ginggs> pitti: thanks
[07:51] <dholbach> @pilot in
[08:40] <knocte> hi guys, is there any sane way to install a gtk3 theme by not having to trust a PPA?
[09:45] <xnox> Logan, no, we are not merging 1.1
[09:45] <xnox> Logan, do not merge it, we _reverted_ to 1.0
[10:15] <juliank> Hmm, 3 things fail for apt/1.4~beta1: (1) doxygen - because it requires osmium which is gone in zesty (2) postgresql-debversion - because of some 9.6 vs 9.5 madness (3) unattended-upgrades due to PEP 8 issues
[10:16] <juliank> I can fix (3) later today, (2) seems hard, and (1I I'm not srue
[10:17]  * juliank wonders why doxygen is even part of the apt autopkgtests
[10:18] <juliank> apt b-d on it, but shouldn't that be the opposite direction?
[10:32] <xnox> juliank, doxygen's debian/tests/control depends on apt
[10:32] <juliank> Ah
[10:32] <juliank> OK
[10:32] <xnox> for better or worse...
[10:37] <dholbach> Tribaal, do you want to prepare debdiffs for the other releases for bug 1644153 too?
[10:37] <dholbach> or do you want to wait for the build to pass and test on zesty first?
[10:37] <Tribaal> dholbach: sure, I can do that
[10:37] <dholbach> excellent!
[10:38] <dholbach> let me know when you're done and I'm happy to take a look
[10:38] <Tribaal> dholbach: I just realized my quilt patches didn't have the headers, I'll add them to the new ones
[10:38] <dholbach> cool, thanks
[10:38] <Tribaal> (or to zesty as well if it's not late)
[10:39] <Tribaal> dholbach: I applied the diff manually on zesty -I'm pretty confident it'll work :)
[10:39] <dholbach> ok
[10:42] <Odd_Bloke> rbasak: gce-compute-image-packages was added to the ubuntu-cloud packagesets for yakkety/zesty; we're also going to be SRU'ing it as a new package to trusty and xenial; can it be added to a packageset before it exists, or will I need to work with someone (an AA?) to do the first upload before that can happen?
[10:47] <pitti> Laney: wow, look at the queues on http://autopkgtest.ubuntu.com/running
[10:47] <pitti> Laney: somehow suspicious that armhf finished so much faster :)
[10:48] <pitti> (but looks alright on excuses)
[10:49] <cpaelzer> smallest and biggest platforms win the autopkgtest race
[10:49] <Laney> pitti: I noticed!
[10:49] <Laney> pitti: did you ever think about using lxd for the other arches?
[10:50] <pitti> Laney: think, yes; if we had an index of which tests have isolation-machines, we could dispatch the other ones into LXD instead of full VMs
[10:50] <pitti> but never managed to implement, this is quite involved
[10:50] <Laney> nod
[10:51] <Laney> densification seems to work quite well for this workload
[10:52] <pitti> Laney: yeah, the 3 mins overhead of cloud instance preparation are the dominant factor for these perl tests in particular
[10:52] <rbasak> Odd_Bloke: it seems to have let me add it for trusty and xenial. So see if that works?
[10:55] <rbasak> cyphermox: any opinion on bug 1641124 please?
[10:56] <Odd_Bloke> rbasak: Will do so at some point today; thanks!
[10:56] <Odd_Bloke> (LP is certainly allowing me to nominate for those series now, which is how I noticed this in the first place.)
[11:38] <pitti> rharper, smoser: the systemd side of bug 1636912 is in -proposed now, this should unblock that cloud-init bit that you had to revert in the previous round
[11:38] <pitti> rharper, smoser: I tested it locally, but would appreciate if you could give it a whirl and v-done?
[12:16] <Tribaal> dholbach: attached debdiffs for yakkety and xenial on https://launchpad.net/bugs/1644153
[12:34] <rbasak> cyphermox: in response to https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1211110/comments/50, we now have a fresh report at https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1634689. Please could you take a look?
[13:07] <dholbach> Tribaal, thanks
[13:07] <Tribaal> dholbach: I wasn't entirely sure about the version numbering - but I *think* that should cover all bases.
[13:07] <dholbach> ok
[13:08] <dholbach> I'll take a look
[13:09] <Tribaal> (upgrading xenial -> yakkety -> zesty will work)
[13:12] <dholbach> cool
[13:21] <dholbach> @pilot out
[13:24] <Tribaal> woohoo thanks dholbach
[13:24] <dholbach> anytime Tribaal
[14:08] <LocutusOfBorg> $ syncpackage -f daemontools
[14:09] <LocutusOfBorg> ginggs, ^^ :) wrt upstart dropping
[14:12] <LocutusOfBorg> didrocks, please double check the sync :)
[14:44] <rharper> pitti: nice! I'll rebuild the UC16 image with cloud-init changes to the systemd unit for networkd
[15:33] <chiluk> stgraber, where does lxd store the information gathered by lxc config show <container>?  I'm just curious how to migrate a container that has attached devices since I haven't discovered where the configuration for the attached disk lives.
[15:54] <chiluk> tych0 ^^ do you know?
[15:54] <chiluk> is that all stored in the /var/lib/lxd/lxd.db ?
[15:54] <tych0> chiluk: yes
[15:54] <tych0> chiluk: you can add another remote and then do a `lxc copy host1:container host2:`
[15:54] <tych0> and it will copy the container and all its config
[15:54] <chiluk> tych0: ok.. that's what I figured you'd say.
[15:55] <tych0> chiluk: alternatively, you can do a, `lxc config show foo | lxc config edit bar`
[15:55] <chiluk> tych0: some of the earlier documentation still refers to tarballs and scp..
[15:55] <tych0> if you just want to copy the config between different containers
[15:55] <tych0> chiluk: orly, where?
[15:55] <chiluk> tych0: I'll send it your way if I come accross it again.
[15:55] <tych0> chiluk: cool, thanks!
[15:56] <chiluk> I was looking at all this saturday when I rebuilt my server with compartmentalized lxc containers for each application.
[15:56] <tych0> chiluk: \o/ :)
[15:56] <chiluk> pretty happy with the results so far.
[15:59] <chiluk> tych0: are you working on lxd now?
[15:59] <tych0> chiluk: yep
[15:59] <chiluk> tych0: how long has that been going on?
[16:00] <tych0> chiluk: three years :)
[16:00] <tych0> well, i guess LXD has only existed for two
[16:00] <tych0> but before that i was working on LXC
[16:01] <chiluk> tych0: I always associate you with desktop people... probably because you own that tiling window manager ..
[16:01] <tych0> chiluk: ha, yes. in fact i've never done any desktop work for canonical at all :(
[16:38] <nacc> mdeslaur: so to be clear, we don't need to carry forward any of the 76/78/80 patches and the build flag change?
[16:38] <nacc> mdeslaur: re: imagemagick
[18:10] <cyphermox> rbasak: mdeslaur: ack, I will look again
[18:25] <nacc> bdmurray: i'm looking to do another MRE for php7.0 to x and y. Would it be appropriate to re-use the prior bug (LP: #1569609)? Or should I file a new bug?
[18:29] <bdmurray> nacc: If the other one was successful / Fix Released then a new one.
[18:30] <nacc> bdmurray: ack, thanks!
[18:46] <mdeslaur> nacc: exactly, the only diff we need with debian is the build-depends change
[18:50] <nacc> mdeslaur: thanks!
[23:38] <nacc> rbasak: should we merge iproute2 (re: LP: #1615209) ?