344
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Sep 2026
344 points (98.9% liked)
Linux
19081 readers
515 users here now
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
founded 3 years ago
MODERATORS
I mean they could have just picked Debian 12... I doubt Debian will make retroactive slop updates to older versions of the distro. At least that's what I'm doing on the systems I administer: set up a custom package that conflicts with base-files >= 13 and with some already-known slopified version numbers (thanks to Open Slopware) to keep things a bit more under control.
Could have but
I had to freeze rsync because of that :(
Thanks to how Debian versions packages, numero 2 is solved with a package solution like mine (liberal use of
>>for package version comparison), so that you can't install the updates that come with slopification.