User1: Nobody home? Lol
User2: 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/.
User3: FourDollars, well at a most fundamental level that is actually what happens on a buildd
User3: FourDollars, the error that is being reported by the kernel makefiles is that your tree is dirty
User3: FourDollars, did you update configs in that tree for instance ?
User3: FourDollars, i find the kernel makefiles say that if include/config exists or something like that
User2: User3 No, I just add my one commit and execute `fakeroot debian/rules clean` before `dpkg-buildpackage -S -us -uc`.
User2: Never mind. Let me try it again.
User3: 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
User2: User3 You are right. `git clean -x -f -d` does remove more files. Thx a lot.
User2: So the proper commands sequence will be `git clean -x -f -d`, `fakeroot debian/rules clean`, and then `dpkg-buildpackage -S -us -uc`.
User3: that is what i do yes
User4: There are no signed daily (or rc) kernels for ubuntu?
User4: got 'some' errors on my new device, so want to check what is resolved yet in the newest kernel
User3: dupondje, signed in the sense of signed for EFI secure-boot ?  no indeed
User3: dupondje, though i am not sure why that would prevent them being booted
User4: User3 going to try :)
User4: allright booted 4.15.0-999-generic :)
User3: dupondje, being unsigned means that grub hands off to the kernel in a different manner, with efi boot services closed down
User5: User6 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?
User4: User3 ok, tought uefi only accepted signed kernels
User4: but good thing, new kernel fixes all my problems :)
User3: dupondje, it only boots it in secure mode
User3: if it is signed
User6: User5 yeah, that broke a bunch of stuff, I've already gotten it reverted upstream (and it just landed in stable too)
User5: User6 ok thanks, glad I didn't try to push that kernel through then :-)
ubuntu-kernel
Ubuntu IRC