[00:29] <guiverc> i asked here awhile back (4-may) about gorilla iso's not being built; it was reported fixed by laney (thanks), plus about focal dailies are still not being built (flavors anyway; I watch lubuntu primarily) - http://iso.qa.ubuntu.com/qatracker/milestones/408/builds doesn't have ISOs for download (lubuntu, ubuntu amd64m eg, http://iso.qa.ubuntu.com/qatracker/milestones/408/builds/212787/testcases)  july-23 for 20.04.1 so it matters a little
[00:29] <guiverc> more now; another leok request
[11:46] <AsciiWolf> kenvandine, hi, I don't know if it is intended or not, but I have noticed that after updating to latest snap-store (the one that fixes app icons), deb results are now displayed on the first place when searching for apps
[11:46] <AsciiWolf> previously, there were snaps displayed before deb results
[12:06] <kenvandine> AsciiWolf: yes, that is intentional.  We no longer alter the order of the results
[12:06] <AsciiWolf> kenvandine, ah, ok :-)
[12:08] <seb128> I don't remember now, do a SRU builds with proposed enabled?
[12:11] <xnox> yes
[12:11] <xnox> (they must)
[12:19] <seb128> xnox, thanks
[12:52] <ahasenack> I'm rebuilding debian-installer because bind9-libs changed in groovy, and it's an rdep
[12:52] <ahasenack> but it's not picking up the new one
[12:52] <ahasenack> I'm wondering if this needs to happen for groovy now: https://paste.ubuntu.com/p/zPqt6jN2YG/
[12:52] <ahasenack> it does look like it
[13:28] <ahasenack> xnox: you helped me in the past with the d-i package, do you know about my question above?
[13:34] <xnox> ahasenack:  ... or remove d-i from the archive.
[13:34] <xnox> ahasenack:  or force migrate bind9-libs
[13:35] <ahasenack> xnox: or apply a similar patch to what I pasted, but for groovy?
[13:35] <ahasenack> The other two things you mentioned I cannot do :)
[14:00] <xnox> ahasenack:  but rebuilding d-i will block up on linux kernel migrations, and entagle any/all/other abi transitions too.
[14:00] <xnox> ahasenack:  i'll look into rebuilding d-i to see how much will break / how painful it would be.
[14:00] <ahasenack> ok
[14:07] <paride> sil2100, hi! I'm seeing a bunch of Focal images in http://cdimage.ubuntu.com/ubuntu-server/daily-live/current/
[14:07] <paride> I'd expect to see only Groovy images there
[14:28] <doko> # Because we believe in quality
[14:28] <doko>         -Wall -Werror
[14:28] <doko> if you would, you would fix the ftbfs :-/
[14:38] <sil2100> paride: uh
[14:38] <sil2100> paride: this is weird! cdimage copying-forward stuff again
[14:38] <sil2100> paride: thanks for reporting, let me clean up and figure out why this happened
[14:38] <doko> jamesh: could you have a look at https://launchpad.net/ubuntu/+source/ubuntu-app-launch/0.12+17.04.20170404.2-0ubuntu7/+build/19239923 ? either fix the ftbfs, or try to remove that in groovy?
[14:40] <paride> thanks sil2100
[17:32] <jrwren> does anyone know how ubuntu installer decides to install hardware related packages on install time? e.g. i have a wifi chip and the broadcom package didn't get installed at install time. I'd love to suggest a patch, but I've no idea where this data is
[17:45] <mdeslaur> jrwren: I think it uses software-properties, which in turn uses the pci ids that are specified in the driver package's rules file
[17:45] <mdeslaur> err, control file
[17:49] <jrwren>  bcmwl-kernel-source is in restricted, so maybe that is why it wasn't installed at install time?
[17:52] <mdeslaur> I don't think so, that's what that checkbox is for
[17:53] <mdeslaur> jrwren: the "ubuntu-drivers" tool can help, try ubuntu-drivers devices
[17:53] <jrwren> at install time?
[17:54] <mdeslaur> you can try it now to see how it detects your hardware