This is not a SFW instance. NSFW communities will be tagged, and efforts will be made to keep SFW communities clean, but proceed at your own comfort level.
some iconic duos in the Linux community: Arch and AUR malware, Ubuntu and bad updates, NixOS and community/team members leaving, Manjaro and failing to renew its cert.
Recently, the nvidia-dkms driver updates wouldn’t build for 5.x series kernels, so if you hadn’t cleaned up old kernels, the update bombed out before updating the initrd filesystem, the system couldn’t boot without intervention. Thankfully, I noticed before trying to reboot my work desktop, and the solution was “apt autoremove && apt upgrade”.
But the install media for my desktop at home was 18.04, and it’s running 26.04 now. It has an AMD GPU, so it hasn’t had update problems.
Its intended behavior from Debian team. because they ships a version of the software at the time and only backport security patches. So if the version they ship has bugs then those bugs stay for years. This generates quite a bit of noise for upstream projects but it is what it is.
some iconic duos in the Linux community: Arch and AUR malware, Ubuntu and bad updates, NixOS and community/team members leaving, Manjaro and failing to renew its cert.
Really, something like this ever happened lol?
I’m sure it has. The idea that it’s frequent is unhinged.
And @rotten@lemmy.today
Wait…please tell me y’all heard of that crazy drama recently where there was tons of AUR packages getting infostealer malware added in.
They got a lot more cautious after that incident but… I’m less keen on the AUR now…
Edit: https://archlinux.org/news/active-aur-malicious-packages-incident/
Welcome to Linux, do you want the BenevolentDictatorOS, WeaponsManifaturerOS, MalwareOS or Debian?
you forgot the oldest of them all, Debian and the its museum, their repos
This is the only drama in your list I’m not familiar with already. What/when did they last break?
Recently, the nvidia-dkms driver updates wouldn’t build for 5.x series kernels, so if you hadn’t cleaned up old kernels, the update bombed out before updating the initrd filesystem, the system couldn’t boot without intervention. Thankfully, I noticed before trying to reboot my work desktop, and the solution was “apt autoremove && apt upgrade”.
But the install media for my desktop at home was 18.04, and it’s running 26.04 now. It has an AMD GPU, so it hasn’t had update problems.
If your playbooks don’t include an autoremove, you’re doing it wrong!
Or rather, lessons learned from when the default /boot partition was only like 100 MB.
Debian and shipping broken packages
Bruh what? I went to debian for server because of stability. It only updates like once a decade and still ships broken packages?
Its intended behavior from Debian team. because they ships a version of the software at the time and only backport security patches. So if the version they ship has bugs then those bugs stay for years. This generates quite a bit of noise for upstream projects but it is what it is.
deleted by creator