Rebasing from `bluefin-dx-nvidia:stable` to `bluefin-dx-nvidia:latest` doesn't change the kernel

DarkGhostHunter commented 1 week ago

Describe the bug

As title. Rebasing the image should change the kernel, or at least ask to do it somewhere if not.

The kernel stays at Linux 6.10.7-200.fc40.x86_64, so rebasing to latest defeats the purpose.

What did you expect to happen?

To change the kernel

Output of `rpm-ostree status`

State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:stable
                   Digest: sha256:79fe03796db8afa2817cdbc4884b139183a84ac146a309f462c04e00bd834931
                  Version: 40.20241007.0 (2024-10-08T05:44:22Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:latest
                   Digest: sha256:541d688e32fd93d81fce6cdacfa710cc37fafeb9fb4b3487c0b87d1a2d3d9b1b
                  Version: 40.20241010.0 (2024-10-11T22:19:23Z)

Output of `groups`

developer wheel

Extra information or context

No response

castrojo commented 1 week ago

You're currently booted onto your :stable image and not the :latest one, which is why you still see the old kernel. That's what the dot on the left means, it's the one you're booted into, booting into latest should get you what you need.

Though the fix with the dx-group you need is incoming and these should be done in the next few minutes, when these turn green then I would do the update:

https://github.com/ublue-os/bluefin/actions/runs/11308213011/job/31450808227

DarkGhostHunter commented 1 week ago

I reverted back to stable since latest didn't yield the fsync kernel, that's why you see the (Actual) ostree being stable first and latest second.

DarkGhostHunter commented 1 week ago

I can confirm that installing :latest does use the fsync kernel, but I didn't bother to rebase to :stable and see if the kernel remained.

ublue-os / bluefin