[12:04] <dupondje> Hi All! There doesnt happen to be daily linux-firmware builds somewhere?
[12:08] <apw> dupondje, don't think so no, what are you looking for
[12:11] <dupondje> apw: well I need to run drm-tip kernel because otherwise my docking station is crashing my system :) Now when installing it I notice "W: Possible missing firmware /lib/firmware/i915/cnl_dmc_ver1_07.bin for module i915
[12:11] <dupondje> guess its better to have recent firmware next to a recent kernel :)
[12:12] <dupondje> but guess i'll have to build my own :)
[12:15] <apw> well if you have the file you can just drop it in the directory
[12:15] <apw> you don't need a package
[12:19] <dupondje> ah, the lazy solution is maby easier :D
[12:29] <jmux> Hi. I have a pending Xenial 4.4 SRU since ~2 weeks (https://lists.ubuntu.com/archives/kernel-team/2018-February/089892.html).
[12:29] <jmux> I've read the SRU suspend mail, so I'm wondering, when new patches will be picked up.
[12:30] <jmux> It would be nice to have a proposed kernel to test in three weeks, as we're going to run our final tests with the new HW:
[12:31] <jmux> I still can patch the kernel myself, but would really like to avoid it, as this means patching all security updates.
[12:33] <jmux> Now that the other patches for the HW are accepted upstream, I'll open some new SRUs, but these aren't critical, as I can easier fix them via DKMS updates.
[13:47] <smb> jmux, There is a long list of things to be picked up once the 16.04.4 point release is done. But with the recent history of emergencies I would not dare to give any specific dates.
[13:48] <walac> Hi, this might be a stupid question, but I am trying to create a custom linux-image-4.4.0-1014.14-aws package, but debian tools like debuild look for files under debian/ directory, wherein this package they are in debian.aws. How could I create a clean source package in this case?
[13:53] <smb> walac, have you tried running "debian/rules clean" once before running the build?
[13:57] <walac> smb: yep, just after asking the question here I figure it out with dpkg-source... typical
[14:20] <jmux> smb: I just saw a lot of stuff was applied, but mostly fixes, not a feature backport. I was just wondering what was going on.
[14:22] <jmux> smb: I'll plan my patching in two weeks and if a proposed kernel is available I'll use it, otherwise patch myself.
[14:23]  * jmux has read the normal SRU cyccle is ~ a month, but since the cycles were suspended indefinitly - so be it
[14:24] <bjf> jmux, we've been doing almost weekly kernel updates with the latest meltdown/spectre fixes. because of how quickly they have been coming we've not wanted to put
[14:24] <bjf> jmux, much more in that just those to lessen the chance of regression
[14:25] <bjf> jmux, March 1 is the new release date for the point release. we hope to start regular SRU cadences again once that's out the door
[14:36] <jmux> bjf: I'm aware and not complaining. I just have my fixed dates for the new HW. And I can patch the stuff myself. I'll adapt my TODO lists and at some future point switch to the Ubuntu kernel again.
[14:37] <jmux> bjf: I already have additional patches for the HDA, cifs, i915, fujitsu-latptop keycode support, but sinse all these are modules, I simply build DKMS packages.
[14:39] <jmux> bjf: but the rfkill module is compiled in, so there is no other way then to patch the kernel
[14:44]  * jmux ... and now that 4.15 is in bionic, I'll have to test and eventually port some of it, as some of these patches were just accepted upstream
[17:49] <Fjodor> Just popped in and saw jmux mention 4.15 being in Bionic - not sure if there is a separate channel for DKMS packages, but if someone needs a patch for broadcom-sta, I cooked one up in the beginning of the 4.15rc-cycle, if someone needs it. Not super-easy, but also not overly hard, so no prob if someone else have come up with something better
[18:11] <walac> could anyone tell me why my build failed? https://launchpadlibrarian.net/357156677/buildlog_ubuntu-trusty-amd64.linux-aws_4.4.0-1014.14taskcluster_BUILDING.txt.gz
[19:01] <apw> walac: the error 8s at the bottom, you didn't create the previous abi
[19:21] <walac> apw: I didn't get (kernel building newbie here)
[19:22] <walac> :)
[19:28] <walac> apw: ah, ok, google is a friend, got it now :)