[01:13] sarnold: Here [01:14] ugh === chris14_ is now known as chris14 [05:03] @arraybolt3, yes, that :-) [05:31] johnnie, our documentation is a mess and hopelessly outdated :-( The good news is that we now have a docs person on the team who started cleaning it up. In the meantime I can try to help. Don't use cranky. It's not ready yet for external consumption. [05:37] johnnie, you need to add the new flavor to debian.master/config/annotations and debian.master/rules.d/amd64.mk (assuming it's for amd64). Then rebuild the annotations using './debian/rules updateconfigs'. This will give you the new flavor with the same configs as generic. Then build it with './debian/rules clean build-' or produce packages with './debian/rules binary-. [05:38] note that 'updateconfigs' will fail the first time (changes to the annotations are treated as failures). If you run it a second time it should pass. [05:39] https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel (partially relevant) [05:46] If you want to make config changes -> debian/rules editconfigs [05:48] To produce 'real' kernel configs -> debian/rules genconfigs. configs are in CONFIGS/ directory. this is can be used for sanity checking the final configs that are used during the build. [05:48] Making changes to CONFIGS/ files won't have any effect. [06:07] johnnie, see this sample https://code.launchpad.net/~juergh/+git/linux/+ref/noble/linux/new-flavor === chris14_ is now known as chris14 [19:14] Thanks for the info juergh. I will try that right now.