[06:00] <Unit193> Is there a reason firefox skipped artful-proposed the last couple uploads?
[07:36] <fossfreedom_> hi all - just testing our latest daily Ubuntu ISO. I cannot ping google.com from either the live ISO session nor an installed session in virtualbox. Can anyone help to provide a bit of insight what has gone wrong in our ISO?
[07:36] <fossfreedom_> s/Ubuntu/Ubuntu Budgie/
[07:37] <tsimonq2> fossfreedom_: Can you ping 8.8.8.8?
[07:37] <tsimonq2> If you can, I usually jump to systemd-resolved acting up again. :P
[07:38] <fossfreedom_> yep - it looks like 8.8.8.8 is working
[07:38]  * tsimonq2 kicks systemd-resolved *grr*
[07:39] <fossfreedom_> sorry - my networking knowledge is non-existent in this systemd world ... what is systemd-resolved?
[07:39] <tsimonq2> (in all reality, that's just a wild guess, don't take my word on it, I personally like for systemd-resolved to be my scapegoat for DNS problems :P)
[07:40] <tsimonq2> fossfreedom_: It replaced resolvconf
[07:40] <tsimonq2> It's the homegrown systemd thing
[07:41] <fossfreedom_> k.  thanks.  Kind of difficult to run ubuntu-bug systemd-resolved without a network :P
[07:41] <tsimonq2> :P
[07:43] <fossfreedom_> tsimonq2, do you have a current daily handy?  just wondering if its just us affected, or all dailies as of yesterday.
[07:45] <tsimonq2> fossfreedom_: I'm running it locally, fresh rebooted 12 hours ago, no problems
[07:45] <fossfreedom_> :(
[07:48] <Unit193> I find DNS usually works better without resolved. :P
[07:49] <tsimonq2> Unit193: I agree 100%. :P
[07:50] <fossfreedom_> who is our systemd-resolved / network-manager SME ?
[07:50] <tsimonq2> fossfreedom_: c y p h e r m o x iirc
[07:50] <tsimonq2> idk, could have changed :)
[07:51]  * tsimonq2 goes to bed, it's approaching 3 AM!
[08:04] <Laney> mwhudson: sucks eh
[08:15] <mwhudson> Laney: which autopkgtest was failing that way?
[08:15] <Laney> mwhudson: ummmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
[08:15] <Laney> python-docker or something
[08:15] <Laney> anything which installs docker as a dependency tho
[08:15] <Laney> docker itself probs
[08:16] <mwhudson> let's see what happens in an artful chroot on diamond i guess
[08:16] <Laney> does that message mean anything to you?
[08:16] <mwhudson> er lxd
[08:16] <Laney> it sounded a bit like an ABI break
[08:16] <mwhudson> well it's the dynamic linker having a fit?
[08:17] <mwhudson> R_PPC64_ADDR16_HA doesn't really sound like the sort of relocation that usually gets as far as the dynamic linker though
[08:25] <mwhudson> uhh
[08:25] <mwhudson> why is the load on diamond 150
[08:27] <mwhudson> i'm sure the 5 apt.systemd.daily processes are entirely unrelated :(
[08:48] <fossfreedom_> cyphermox, is this one you can help us with please? or let us know who can? TIA https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712283
[09:44] <jibel> xnox, ^ it could be due to last upload of resolvconf. It's gone from the image.
[09:49] <xnox> jibel, yes and no. both ifupdown and resolvconf are no longer required, which is normal. with systemd that migrated last friday there are changes to DNS.
[09:49] <xnox> i shall test things with latest image to see what's going on
[09:50] <xnox> (however note that resolvconf was only demoted from priority important on monday)
[09:51] <jibel> xnox, okay.
[09:52] <xnox> i believe cloud images failed to publish too.
[09:53] <xnox> mwhudson, apt.systemd.daily arguh?!
[10:07] <xnox> jibel, hmmmm ubuntu-desktop doesn't boot for me at all
[10:08] <mwhudson> xnox: the machine was unhappy, some io nonsense
[10:13] <xnox> fossfreedom_, jibel $ sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
[10:13] <xnox> fixes things interractively, investigating why that's not the case out of the box.
[10:17] <fossfreedom_> xnox +1 cheers.  That works nicely.
[10:23] <xnox> jibel, fossfreedom_ - and i think i know what i need to upload to fix this.
[10:28] <xnox> hm, however i am confused why /etc/resolv.conf is an empty file inside the chroot
[10:28] <xnox> inside the image that is.
[10:40] <xnox> hm.... looks like a bug in livecd-rootfs
[10:52] <mwhudson> Laney: well docker passes a smoke test in an artful lxd on a xenial host  on ppc64el :(
[10:53] <Laney> mwhudson: can you start an artful VM?
[10:53] <mwhudson> Laney: let's see
[10:57] <mwhudson> how do i figure out the ip address of a vm with virsh again?
[10:59] <mwhudson> cpaelzer: i've started the mwhudson-artful vm on diamond but it doesn't seem to be talking to the network, help?
[11:01] <xnox> mwhudson, use older artful vm? =) pre-monday ideally
[11:01] <xnox> there is a bug in current networking not working.
[11:01] <xnox> possibly try starting systemd-networkd and netplan
[11:01] <mwhudson> xnox: this one is a little old
[11:01] <xnox> horum, ok.
[11:02] <mwhudson> anyway i should go to bed instead of this
[11:02] <mwhudson> if someone wants to reproduce https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1711935 and give me access to a system / vm where i can do so too, that would be most excellent
[13:34] <seb128> bdmurray, hey, could you have a look to the patch on https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1703365? It looks good to me, maybe you can look if it makes sense to you as well and get it merged?
[14:20] <doko> seb128: why did you set the status to comitted? https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1703662
[14:20] <seb128> doko, because it was closed by nobody actually promoted it
[14:20] <seb128> so fix released felt wrong
[14:21] <doko> s/by/but/ ?
[14:21] <seb128> yes, sorry
[14:21] <seb128> I should have set it to triaged or something else?
[14:21] <doko> set back to new. committed means it is approved and needs an archive admin to promote
[14:21] <seb128> which is the case there afiak
[14:22] <doko> and think cyphermox can handle that then
[14:22] <doko> ?
[14:22] <seb128> it's approved and showing on component mismatch
[14:22] <seb128> see comment #5
[14:23] <cyphermox> wat?
[14:24] <cyphermox> r-p-a-t was Fix Committed because the MIR was good, and ready to be promoted.
[14:30] <seb128> cyphermox, it got fix released without being promoted which is why I changed the status back to fix commited, which doko was asking about
[14:30] <seb128> I guess it just need to be promoted
[14:30] <seb128> I need to change location but I'm going to do that once I'm back online (if nobody beats me to it)
[14:32] <doko> Mirv: #1708428 needs a package subscriber, I guess the same as libvoikko?
[14:54] <bdmurray> seb128, jibel: I'm out today but will have a look at the u-m bug tomorrow.
[15:05] <cpaelzer> xnox: I saw you dropping upstart jobs from irqbalance
[15:06] <cpaelzer> xnox: I might remeber wrong but those jobswere no delta but in Debian right?
[15:06] <cpaelzer> xnox: and if so would there be any pain to leave them as is - it now has a native systemd service anyway
[15:06] <cpaelzer> xnox: so whats the purpose on actively dropping those?
[15:06] <xnox> cpaelzer, yes there is pain.
[15:07] <cpaelzer> any bug or other explanation I could refer to when understanding :-) ?
[15:09] <xnox> package size, image size, install size, conffile checks in dpkg on every upgrade, longer build times, larger maintainer scripts, larger backups, larger etckeeper, larger and longer 'grep -r /etc'
[15:09] <xnox> cpaelzer, they are small, but it is a lot times 10,000 containers
[15:10] <xnox> i'm aiming to have /etc/init gone from artful lxd cotnainer and I am 3 packages away from achieving that
[15:10] <cpaelzer> xnox: ok, no offense please just wanted to understand :-)
[15:10] <cpaelzer> now I see your point thanks
[15:10] <cpaelzer> did you submit the drop as request to Debian?
[15:11] <xnox> cpaelzer, not yet, but i will do a mass bug file in debian with dd-list
[15:11] <cpaelzer> ok thanks
[15:11] <xnox> at the moment i want to clear lxd default container by feature freeze, then proceed with debian mass bug file
[15:11] <xnox> some scripts dropped were ubuntu delta (thus minimising delta)
[15:11] <xnox> some bugs are filed upstream / to debian
[15:12] <cpaelzer> ok, I had a merge ready and just wanted to get context
[15:12] <cpaelzer> now I'm able to redo it properly - thanks for the details xnox
[15:13] <xnox> cpaelzer, grab the diff from launchpad and reply it on top of your merge, it should apply clean sans changelog whcih will need tweaks
[15:36] <seb128> jbicha, hey, did you see my ping about n-m/connectivy api? (sorry was offline for a bit, and now I don't want to disturb the meeting :-)
[15:37] <jbicha> seb128: I think so, haven't had a chance to look through jamesh's backported patchset yet
[15:37] <seb128> jbicha, I think it's a simple matter of applying to the vcs/uploading, it's just that my todo is full for today and I'm off tomorrow
[15:38] <seb128> so if you would like to handle the upload that would be welcome
[15:38] <seb128> otherwise I try to do that on thursday
[15:38] <jbicha> seb128: if it doesn't take too much time, could you try to kickstart the desktop version tracker again today?
[15:39] <seb128> jbicha, sure
[15:39] <jbicha> yes, I'll try to look through the NM uploads by tomorrow
[15:40] <seb128> thanks
[15:42] <jackpot51> Discussion about Pop! OS right now, right here: https://chat.pop-os.org/community/channels/town-square
[15:43] <nacc> jackpot51: ... why are you putting that in this channel?
[15:44] <seb128> seems spam, he cross posted on other channels as well
[15:44] <nacc> seb128: +1\
[15:45] <jackpot51> Not spam, just if you guys are interested
[15:45] <jackpot51> If not, please ignore, I won't send any more messages
[15:48] <jackpot51> It is *one* message to talk about an Ubuntu based distribution. We are currently discussing default settings and applications
[15:52] <seb128> jackpot51, well, you gave little context on what you plan to discuss and why it could be useful to Ubuntu developers to join
[15:54] <jackpot51> Sorry for that seb128
[23:52] <Unit193> Hrm, not patch pilot listed on the calendar for a while.  Can I get anyone interested in helping a flavor out?  bug 1709733