Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
If all of those are Ubuntu || Debian base os repos then yes ... that is terribad. But if those are some specific package repos it's not necessarily that bad - it's not good, but it's not bad if there are no releases for newer Ubuntu || Debian distro releases because the package repo author decided to stop providing those packages and instead switched to Snaps. But it's more likely it's just as you suspect - upgrading done/gone wrong.
@theKarlisK when you have 4 different RELEASE repos configured....
I would simply pull the plug.
It's usually the terminal stage of a snowflake server.
Someone just ran dist-upgrade over and over and noone knows what is configured and especially why.
You've now to unfuck the mystery of 3 release upgrades, maybe unclean (package|config|repo) installation's, missing / changed configuration, maybe leftovers, maybe old packages from non maintained repositories...
I could continue. ;)
But all in all, just pull the plug.
Set up a fresh machine, install necessary software, document and check / fix the fallout.
Everything else is just denying the fact that the machine can go poof at anytime and noone knows what to do.
Aldar11041y@IntrusionCM That is actually what we suggested.
Seeing as it was a "dedicated", not "managed" server (The reason being, managed has our managment in its cost, but no root access), we would have to play a detective to un-fuck the server.
Funny, boss said the guy used to actually own a managed server, but... Decided to switch. What a fun turn of events.
raspark1783346dDid someone say docker?