352
Upstream images vs bazzite: https://github.com/ublue-os/countme/blob/main/growth_upstream_with_bazzite.svg
My prediction: bazzite may have more installs than Fedora KDE by the end of the year.
this post was submitted on 19 Jul 2026
352 points (99.2% liked)
Linux
67616 readers
1111 users here now
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.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What do you mean? How can it be possible to eliminate a packaging error? If the packaging team makes a mistake you get a broken software, regardless whether you download a binary through a repository or through flatpak.
Because the image never gets built if there's a packaging error, so the user never ends up on a broken image. A broken package never makes it to the end. If it's broken the user just doesn't get an image until the package is fixed and then they get a new image.
I had broken packages getting installed before. They would compile correctly but certain functionality would not work due to how it was packaged. This is not something which can be prevented, I do not believe it is possible.
It is 100% possible and people have been doing it for years. If the package is broken the final product is never built, it's impossible to ship it to the end user since it's one whole complete image.
I am afraid we are talking about different things. Recently I had to report a broken package to a repository. The problem was that they mapped a path to the incorrect directory.
The software compiled and worked correctly, but some specific functionality which needed to read data from that directory was broken.
I do not think there is a way to prevent this kind of errors.
In normal repos they also test their packages. I do not think it is possible in any distribution repo to ship a binary which did not compile. Dynamic library linking may have some problems I guess, but unless you're using arch that is generally never a real problem with package manager installations. I have never got a package which plain does not run.