[01:36] <stephen101> Nobody home? Lol
[07:21] <FourDollars> Hi, I was asking about how to generate the Debian source package from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem last week. I can generate the Debian source package now after executing `fakeroot debian/rules clean`. However the Debian source package can not be built by sbuild with some error like http://paste.ubuntu.com/26207215/.
[08:40] <apw> FourDollars, well at a most fundamental level that is actually what happens on a buildd
[08:40] <apw> FourDollars, the error that is being reported by the kernel makefiles is that your tree is dirty
[08:40] <apw> FourDollars, did you update configs in that tree for instance ?
[08:41] <apw> FourDollars, i find the kernel makefiles say that if include/config exists or something like that
[08:41] <FourDollars> apw: No, I just add my one commit and execute `fakeroot debian/rules clean` before `dpkg-buildpackage -S -us -uc`.
[08:43] <FourDollars> Never mind. Let me try it again.
[08:45] <apw> FourDollars, once yo have applied the fix, use a git clean -x -f -d on the tree, it will _remove_ everything not in version control so expect that
[08:46] <FourDollars> apw: You are right. `git clean -x -f -d` does remove more files. Thx a lot.
[08:47] <FourDollars> So the proper commands sequence will be `git clean -x -f -d`, `fakeroot debian/rules clean`, and then `dpkg-buildpackage -S -us -uc`.
[08:48] <apw> that is what i do yes
[13:37] <dupondje> There are no signed daily (or rc) kernels for ubuntu?
[13:38] <dupondje> got 'some' errors on my new device, so want to check what is resolved yet in the newest kernel
[13:46] <apw> dupondje, signed in the sense of signed for EFI secure-boot ?  no indeed
[13:46] <apw> dupondje, though i am not sure why that would prevent them being booted
[13:47] <dupondje> apw: going to try :)
[13:53] <dupondje> allright booted 4.15.0-999-generic :)
[13:59] <apw> dupondje, being unsigned means that grub hands off to the kernel in a different manner, with efi boot services closed down
[14:21] <sforshee> kees: your patch which changes the behavior of the RLIMIT_STACK hard limit across suid exec, that has broken one of our tests. The test can be fixed, but I'm wondering how confident you are that it doesn't regress any userspace stuff?
[14:31] <dupondje> apw: ok, tought uefi only accepted signed kernels
[14:38] <dupondje> but good thing, new kernel fixes all my problems :)
[14:48] <apw> dupondje, it only boots it in secure mode
[14:48] <apw> if it is signed
[17:18] <kees> sforshee: yeah, that broke a bunch of stuff, I've already gotten it reverted upstream (and it just landed in stable too)
[17:22] <sforshee> kees: ok thanks, glad I didn't try to push that kernel through then :-)