=== chris14_ is now known as chris14 === chris14_ is now known as chris14 === JanC_ is now known as JanC [09:29] is there an overview somewhere about the differences between ubuntu and mainline [09:32] no. you'd need to look at git or debian/changelog but it's not obvious. [09:33] high level features listed somewhere? [09:33] no [09:34] is git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic forked from mainline? [09:36] like, it should be good to add as a remote of my local kernel.org/github torvalds repo? [09:37] kinetic is v5.19 plus patches [09:38] we always start from upstream's first release and than add on [09:43] is there a WIP branch for 6.x? [09:44] git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar [09:44] git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linuxunstable/+git/unstable [09:45] https://code.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/unstable [09:46] which will have the least issues for a desktop (amd TR, nvidia 2080) [09:47] you can also try mainline builds https://kernel.ubuntu.com/~kernel-ppa/mainline/ [09:48] not supported though [09:50] what brings debian/rules into the source tree [09:51] what source tree? [09:51] e.g. upstream, tag v6.1 [09:52] mainline builds? [09:52] commit 830b3c68c1fb1e9176028d02ef86f3cf76aa2476 (HEAD, tag: v6.1) [09:52] Author: Linus Torvalds [09:52] I reckon the kernel itself does not maintain any distributions build scripts [09:53] what? there's no debian/* in upstream. [09:54] yes, thats what I meant. it is maintained by debian which ubuntu forked from? [09:55] we don't fork the kernel from debian. I have no clue what you're asking [09:57] if you're talking about our mainline builds on kernel.ubuntu.com then we pull the debian/* files from our closest Ubuntu kernel. the tooling is here https://git.launchpad.net/~canonical-kernel/+git/kteam-tools/tree/mainline-build [09:59] so tooling scripts place debian/ into a source checkout before building and also packages it into source packages, which is how you get it when you use apt-get source, but it is not part of a kernel source repo that you maintain as a fork, correct? [10:01] thank you for being patient with me [10:05] not really no. we're talking 2 different things here: mainline builds and regular Ubuntu packages that land in the archive. [10:07] mainline builds are automatic builds. they are triggered when there's a new upstream x.y.z tag. for these the debian/* files are automatically added and packages are automatically built using scripts from kteam-tools. these you can only get from kernel.ubuntu.com via manual download. [10:09] for official ubuntu kernels, we start with - let's say - updstream v5.19 (fork it) and manually add debian/* to our repo. then layer patches on top as needed. build source packages upload them to LP and they eventually show up in the archive as apt getable [10:21] ah so debian/ actually is commited to e.g. mainline-crack, so I should be able to build from that using fakeroot debian/rules [10:39] *** The source tree is not clean, please run 'make ARCH=x86 mrproper' [10:39] *** in /home/florian/src-misc/mainline-crack [10:41] https://help.ubuntu.com/community/Kernel/Compile - seems outdated referencing instructions for as old as hardy [10:58] oh, I had a .config file that was not supposed to be there [11:49] DEB_BUILD_OPTIONS=parallel=16 AUTOBUILD=1 NOEXTRAS=1 skipabi=true fakeroot debian/rules binary-generic [11:50] I used this to build 6.1 and it worked. how do I only build the modules, or even just one module [11:50] specifically snd_usb-audio