429
Fedora Silverblue is the most frustrating distro so far
(lemmy.world)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Love the irony, but this is painting a little too good a picture
Most times yes, but major updates usually cause some trouble, like from 39 to 40, you couldn't do it without uninstalling the codecs for Firefox. Firefox that is installed by default as an RPM, because the Flatpak Firefox doesn't yet have 100% compatibility with all the features that work with the RPM, so as a user you're pretty much led to get yourself stuck in this hole, not too difficult to fix in the end, but still a pain to find out and fix.
Everything else is 100% true! And I think it will be always hard to beat as an implementation of immutability (second place only to NixOS imo), A/B partitioning doesn't hold a candle to OSTree
Weird. I use Bazzite which is off of Kinoite and the upgrade from 39 -> 40 was seamless.
Doesn't Bazzite have the base image modified to have the codecs included already? I think that's probably why you didn't experience any disruption there
link: https://github.com/ublue-os/bazzite/?tab=readme-ov-file#about--features
what happened is rpm-fusion was lagging behind the official fedora repos, so, you could have just waited, or enabled the automatic update and forget about it
Is that so? From the issue I read there was no way around it because the two images are fundamentally incompatible once you layer that package, you had to remove the layered package, it seemed from the discussion that they might have "fixed" the base image at some point as a pull request was opened on Pagure. I waited a bit for it to go upstream, but nothing happened for a long time and just went thorugh with the manual intervention, and actually, now that I check it again, the maintainer siosm commented that they can't accept the PR
oh, i never had that issue, only the rpm-fusion lag, never thought that the codecs needed a different approach