[11:18] infinity, shouldn't we demote lilo-installer udeb to universe, it's annoying that it gets loaded everywhere, no? [11:39] bdmurray, could you please subscribe foundations to partman-swapfile package please? https://launchpad.net/ubuntu/+source/partman-swapfile [11:40] bdmurray, oh, i have powers too it seems. I've managed to subscribe foundations-bugs to it. [11:41] subscribing ubuntu-installer team too [18:44] cyphermox, is it an oversight that driver-injection-disk is not part of the ubiquity build? [18:45] i thought that's what is used for raid controller drivers by OEMs [18:45] I don't think it's an oversight, ubiquity uses a "desktop" kernel, not the split up kernel for d-i [18:45] depends what exactly is shipped by driver-injection-disk [18:46] is that the right source package name? [18:46] the question come up from an OEM that is trying to enable their raid controller (proprietary at the moment i am gueesing) yet use it with a dekstop/ubiquity installer for some reason [18:46] i believe hw-detect is the package that ships that [18:46] ah, yeah, makes sense [18:47] driver-injection-disk is the binary/executable name, and the udeb for it is a slightly different name [18:48] right, I see now [18:49] I don't think it's an oversight, it just never came up [18:49] I'd be tempted to say it probably don't hook up so great to the typical ubiquity UX [18:51] otherwise I'd run it just after the welcome/prepare screen, same place as where the SB stuff is hooked up, it might take a bit to hook it up cleanly [19:09] cyphermox, i think we simply want to install / activate the .deb live and for target. And do nothing for the .udeb .ude [19:09] so slightly different code path. [19:09] and obviously said OEM wants it for xenial.... [19:09] is there any other way to inject .deb during install & for target, with ubiquity images? [19:10] driver injection disk sounds like the cleanest way forward to me, but i'm not sure if there is anything else on the desktop iso. [19:10] does ubuntu-drivers do anything special in ubiquity? [19:10] well, if the driver packages are in the archive they could get picked up by ubuntu-drivers via modaliases, but I guess in this case they're not in the archive [19:11] easiest might be to use an early command? [19:16] which is fidally [19:16] *fiddly [19:27] not really