Merge kernel-cache & akmods repos for consistent kernel versioned builds

[bsherman]

Since these two repos have tightly coupled/dependent workflows, we should merge the workflows.

Blocks: #256

[piaste]

Hi @bsherman

First, thanks so much for your work on the project. I've had five machines running on various uBlue flavours and I've been extremely happy with them for over a year :)

Last week I had to start maintaining a simple custom Bazzite image in order to re-include the NCT6687D module.

Right after #295 was merged, fixing this issue, I was able to get it to run by using the akmods-extra:bazzite-41 image alone on top of bazzite-stable. I am running the resulting image as I write, and it's working perfectly (although I haven't tested Secure Boot yet).

However, the pipeline only worked once, and subsequent iterations ran into kernel-uname-r errors.

For example, I see that the akmods-extra image was rebuilt 14 hours ago, yet 4 hours ago my automated build failed due to a kernel/kmod mismatch:

 Problem: conflicting requests
  - nothing provides kernel-uname-r = 6.12.12-206.bazzite.fc41.x86_64 needed by kmod-nct6687d-0.0.git.109.80dc037b-1.fc41.x86_64 from @commandline
Error: building at STEP "RUN rpm-ostree install /tmp/rpms/kmods/*nct6687*.rpm": while running runtime: exit status 1

I'm trying to figure out the correct way to fix this dependency. Is there a way to determine the correct akmods-extra tag to be used for whatever the latest bazzite:stable image is ? Or do I need to e.g. copy over the relevant parts from fetch-kernel.sh script and manually add the rpms? (But my understanding is that kernel packages shouldn't be installed via rpm-ostree).

[bsherman]

@piaste

First, thanks so much for your work on the project. I've had five machines running on various uBlue flavours and I've been extremely happy with them for over a year :)

Thanks for hanging with us!

Could you please recreate this as a new issue in this repo?

I'll answer there.