=== chris14_ is now known as chris14
[08:28] <fscholz> Good morning, I'm currenetly searching for the git sources of lunar lobsters kernel. I would expect it on https://kernel.ubuntu.com/git/ as ubuntu/ubuntu-lunar.git but it's not there. 
[08:31] <arighi> fscholz, hi, you can find the latest lunar kernel source code here: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar
[08:32] <fscholz> thank you! 
[08:32] <arighi> for other releases simply replace "lunar" with something else and you should get the right git repo
[08:49] <xnox> we really should put a notice on kernel.ubuntu.com/git that it is deprecated
[08:51] <arighi> ^
[09:55] <chilversc> I can't find the source for v6.4-rc4 Mainline Test https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.4-rc4/ neither the tag cod/mainline/v6.4-rc4 or the commit 6a3795740a6d0f09f64d07099fb52c1bc042bd29 seems to exist in the repository.
[10:05] <juergh> chilversc: read the backlog
[10:06] <chilversc> what backlog?
[10:06] <juergh> this channel's backlog
[10:08] <fscholz> I itried the editconfigs as recommended by https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel as I understand it as the right way, to change the .config file. You recommend for all architectures to "y" and exit. But it causes some errors for me. https://pastebin.com/FUVA4YpY. The branch is "master" on lunar. 
[10:09] <fscholz> Please use the pastebin link without the final "." 
[10:10] <juergh> fscholz: `WARNING: powerpc64le-linux-gnu-gcc-12 not installed`
[10:16] <fscholz> Okay, that was the issue. Another one is check-config: FAIL: (y != -): CONFIG_RUST_IS_AVAILABLE policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y'}>)
[10:16] <fscholz> for s390x.. is there a way to exclude these architectures? Or is there an easy fix?
[10:21] <arighi> fscholz, it's just telling you that this config will be different than ours (this is due to the fact that you don't have the Rust toolchain installed in your build environment), just commit/apply that change and the build should be happy
[10:22] <arighi> fscholz, see also: https://discourse.ubuntu.com/t/kernel-configuration-in-ubuntu/35857 (about configs in the recent ubuntu kernels)
[10:32] <arighi> fscholz, hm.. wait, it's the other way around, it tells you that CONFIG_RUST_IS_AVAILABLE=y in your config, but it's not defined in debian.master/config/annotations, but I see all the arches there, in which architecture are you trying to build this?
[10:37] <fscholz> x86_64
[10:38] <fscholz> I mean amd64
[10:53] <arighi> fscholz, so if you run `fakeroot debian/rules clean updateconfigs` it should update your debian.master/config/annotations, if you're on a git repo do a `git diff` to show the changes, if everything looks good commit and then re-try the build, it shouldn't complain anymore
[11:00] <fscholz> Thank you, that fixes the issue. 
=== JanC is now known as Guest5232
=== JanC_ is now known as JanC
=== philcox_ is now known as philcox
=== JanC_ is now known as JanC
[14:10] <chilversc> Is there a simple way to build the -gcp flavour for the mainline kernel (6.4-rc4) instead of -generic?
=== JanC_ is now known as JanC
[16:46] <juergh> chilversc: not really, no.
[16:59] <arighi> chilversc, rebase all the gcp patches on top of 6.4-rc4, fix all the potential conflicts and adjust all the kernel configs... that's the simplest way I guess :)