I have Bazzite running on a BC-250 machine. A few weeks ago, I made some changes using rpm-ostree related to zram and swap. I had assumed that, because I used rpm-ostree, the changes would become part of the “tree” and I could rollback to the original settings. But when I went to look at Bazzite’s rollback tools, it seemed solely focused on rolling back to previous official releases, and I couldn’t find any reference to the specific changes I made.

  • breadsmasher@lemmy.worldEnglish
    161·
    8 hours ago

    https://docs.bazzite.gg/Installing_and_Managing_Software/rpm-ostree/

    Layering packages irresponsibly can be destructiveand may prevent updates as well as other issues until the layered packages are removed.

    Use this method as a last resort and for anything at a “system-level” only since it can pause updates, if the package contains dependency issues with future upgrades, until the package is uninstalled.

    MAJOR caveats using rpm-ostree

    Layering packages can cause severe consequences including:

    • Pause system updates until package(s) are uninstalled.
    • Prevent rebasing to different images until package(s) are uninstalled.
    • Conflict with existing packages as part of the image leading to dependency issues.
    • Updates taking longer to download as you layer more packages to your system.

    Youre breaking a core tenant of immutable distros by installing system level packages. i think that might be your misunderstanding?

    • throwaway403@programming.dev
      3·
      4 hours ago

      Bazzite’s messaging has merit, but we’d be making a mistake by regarding it as absolute. It makes more sense to take them as carefully written guide lines for a specific audience.

      Furthermore. with all due respect, but OP’s writing doesn’t imply installing/managing software with rpm-ostree. Which, is actually the subject of the documentation entry you quoted. As such, I think you might have misunderstood them.

      Youre breaking a core tenant of immutable distros by installing system level packages.

      Finally, FWIW, I absolutely disagree with the above. The page you quoted from seems to agree with me on this: “Layering packages are mostly intended for system-level applications, libraries, and other dependencies.”