I rebased my laptop install to bazzite-dx yesterday and for some reason, the stable branch installed a testing image (testing-44.20260802) instead of the latest stable image (stable-44.20260802). I pinned to the latest stable for now but does anyone know why bazzite rebase helper would do this?
Is it not letting you rebase to stable?
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stableRebasing to normal Bazzite worked fine, but for some reason rebasing on Bazzite-DX, even when picking a specific stable image, would pull the testing image from the same day every time
A couple of issue trackers I found that may (or may not be) related:
- https://github.com/ublue-os/bazzite/issues/5255
- https://github.com/ublue-os/bazzite-dx/issues/209
- https://github.com/ublue-os/bazzite-dx/issues/198
Question: Could you paste the output of
rpm-ostree status?Thanks for the links, I still hadn’t rebased my desktop yet so I took a before and after of both rpm-ostree and fastfetch, and saw 209 in effect
Before
After
What has me still confused is that the different bazzite update tool in the testing image was also confused by the image
Bazzite Update Tool
I mean why would it say a stable image has a testing id and bootloader if its not testing
