[00:25] <sarnold> mwhudson: dude, this quickstart is awesome; it's easily the best documentation I've seen yet on supplying cloud-init metadata to a system, thanks :)
[01:32] <mwhudson> sarnold: ah haha
[01:33] <sarnold> mwhudson: way back when, I wanted to try writing my own libvirt kind of thing because libvirt annoys me; I spent two days trying to get the qemu parameters correct to feed cloud-init data to our cloud images and I don't think I ever actually got it to work
[01:34] <mwhudson> sarnold: tbf if you don't boot with -initd/-kernel it is a lot harder
[01:36] <sarnold> mwhudson: I can't recall now if I tried that or not, heh
[10:09] <ginggs> juliank: are you aware your synaptic NMU FTBFS in Ubuntu? I was looking to sponsor LP: #1870900
[10:10] <juliank> ginggs: no
[13:33] <seb128> lathiat, hey, did you have a chance to test the avahi built in the ppa?
[13:46] <teward> seb128: RE: https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1834270 - since you were on that bug back when it was opened, I'm going to NACK this as a sponsor because that seems to minor to fix for 19.10 as filed - unless this affects 20.04 as well in which case it needs patched there?  (Xubuntu related)
[13:46] <teward> it's only on my radar since someone attached a patch ;)
[13:49] <seb128> teward, looks like it's fixed in focal yes, closing sounds good to me, thanks for checking
[13:51] <teward> seb128: yep.  even if I don't have to do sponsor work I'm on the sponsors team so when it shows up on my radar I take a look heh
[13:52] <teward> marked as Eoan and Focal, Eoan=Won'tFix, Focal=FixReleased
[13:52] <seb128> thx
[13:53] <teward> yep.  sorry about the random ping but you were on the bug in the past so thought I'd check with you :0
[13:53] <teward> :) *
[13:54] <teward> not TIL or anything but always doesn't hurt with a second set of eyes :)
[14:28] <AsciiWolf> kenvandine, hi, sorry for bothering you with this again, but since Snap Store still seems to be running without the Ubuntu Software branding (its window has "Snap Store" name/icon, menu entries for Software Sources instead of Software & Updates etc.) and without the regular (deb) packages support, I wonder if there is any way to track snapd releases other than manually checking its Launchpad page... I would like to help testing
[14:28] <AsciiWolf> it, but I have Focal only in a VM and have to watch the Launchpad snapd page and/or start the VM and check for updates every day or two which is not ideal :/
[14:29] <AsciiWolf> (oops, sorry for the longer text)
[14:30] <AsciiWolf> or is there any ETA on when the new snapd release (which fixes the mentioned Snap Store issues) could happen?
[14:31] <kenvandine> AsciiWolf: the fix will be in snapd 2.44.3 which i've been told should be release around the end of this week
[14:32] <AsciiWolf> kenvandine, thanks!
[14:32] <kenvandine> AsciiWolf: what revision of snap-store do you have?
[14:32] <kenvandine> the branding fix is in latest/stable/ubuntu-20.04
[14:32] <AsciiWolf> the latest stable one
[14:32] <kenvandine> revision 345
[14:32] <AsciiWolf> hmm
[14:32] <AsciiWolf> I'll look
[14:32] <kenvandine> oh, that's not what's intended for focal
[14:33] <kenvandine> sometime next week i expect what's in latest/stable/ubuntu-20.04 will be promoted to stable
[14:33] <kenvandine> assuming everything goes as planned
[14:34] <AsciiWolf> "snap-store  20200403.d6b9c02  345"
[14:34] <AsciiWolf> this is what I have
[14:52] <AsciiWolf> kenvandine, by the way, I have just noticed a smaller issue with po files: https://bugs.launchpad.net/snap-store/+bug/1870777/comments/2
[14:56] <bdmurray> xnox: if bug 1870018 is fixed in casper can all the other tasks be closed?
[15:04] <xnox> bdmurray:  all other tasks are wishlist; ie. all of those themes have broken parsing of systemd-fsckd during normal boot.
[15:04] <xnox> bdmurray:  casper only did "if old theme, use old messages, if new theme use new messages" but systemd-fsckd on boot only uses "new messages" which are still broken.
[19:01] <pyusr> hi, question, i'm on Ubuntu 18.04 LTS and is it my imagination or is the documentation for memset in "man memset" and "man bstring" not the same ?!?
[19:01] <pyusr> my friend who is on 18.04 LTS claims it's OK for him, WTF ?
[19:02] <pyusr> sorry, for memmem in "man memmem" and "man bstring"
[19:07] <Eickmeyer[q]> !support
[19:10] <sarnold> https://manpages.ubuntu.com/manpages/trusty/man3/memmem.3.html
[19:10] <sarnold> crazy, the trusty memmem manpage isn't about memmem at all
[19:12] <pyusr> got disconnected, did anybody respond ?
[19:20] <pyusr> there is a big bug in "'man bstring" in atleast ubuntu 18.04 LTS in memmem definition ! I used it, and it's wrong
[19:23] <pyusr> any updates on getting https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1864766 closed ?
[20:31] <Odd_Bloke> focal's Contents files on-mirror (e.g. http://archive.ubuntu.com/ubuntu/dists/focal/Contents-amd64.gz) are empty currently; who should I escalate this to?
[20:34] <cjwatson> Odd_Bloke: That must be an LP bug - can you file it with us?
[20:34] <cjwatson> They're empty on the master too
[20:36] <Odd_Bloke> cjwatson: https://bugs.launchpad.net/launchpad/+bug/1871920
[20:37] <cjwatson> Thanks.  Not sure whether any of the people who are around Fri and Mon will be able to tackle that
[20:37] <cjwatson> And yes, I remembered it happening before as well, so we'll need to refresh our memories of then
[20:38] <cjwatson> IIRC it was a rare event that we happened to hit at a bad time for eoan.  I don't remember whether we actually fixed anything or just regenerated them