this post was submitted on 14 Sep 2026
70 points (97.3% liked)
Linux
67588 readers
743 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
He/She was maintainer of the Void Linux packages, that is the package build scripts, updates, etc., not the projects and source code which these packages are based on.
For example, Guix has now over 32000 packages, including an Emacs package. But of course, they did not re-create Emacs to make that package - they just made a build definition which uses the Emacs git repo, in order to build the Guix package. Or in the case of Ubuntu, it is based on the package definitions in Debian testing, so the Ubuntu maintainers do not have to write all the build scripts or package definitions - but they still have to do significant work in order to adapt them that everything fits together.
Or with Arch Linux, the packages are taken relatively vanilla from upstream, they package stuff more "as is" as compared to Debian. Which means less work, and often more clarity for experienced users.
Coming back to Void Linux, this means for these 100+ Void Linux packages which are currently orphaned, it is feasible that other people with good Linux experience adopt these, with a reasonable effort - some are important.
Distro package maintainers are different than software dev maintainers.
They mean no one can be reasonably be up to date on software security updates, and (ideally) ensuring all packages changes are not malicious (as well as the small stuff like properly integrating to the distro, but idk how void works enough to comment on that)
Cause like I can write a ton of guix configs that'll probably run until the next ice age, but that does nothing about the dev who's software I packaged, that now decided they're personally god and need to spread christ as fast as possible.
(Also off topic but that's the power and curse of nixos-like distros, its too easy to package so odds are the shit ain't updated, and suddenly there's 1000 Firefox packages in nixpkgs)
Some people do an astounding amount of work.
And then there are many, many, which help a little.
Also, if, say, somebody finds that in Debian testing is a malicious package, people which maintain Arch will learn that. Open information sharing between many thousands of people willing to coordinate is a superpower.
Oh god yeah, its just filtering through the slop that actually matters.
But like the XZ trojan that was only affecting Debian installs, each distro needs to individually have competent maintainers to ensure their store is safe.
If for exapmle I set a couple 'bugfixes' in the guix package file for emacs, I could reasonably infect a number of systems if a lazy maintainer just approved the request. (Or other attacks without even involving guix if I notied a bug in a package spelling and typo squatted it, or stole signing keys and pushed updates to the repo myself).
None of these would change anything to other distros maintainers, but because this distros AI maintainer could risk a large number of users devices.