So a new major version of Debian has been released, and now I see a lot of complaints about various issues stemming from an upgrade. I do not remember this many after an LTS Ubuntu version. I don’t want to rush to conclusions like “Ubuntu has money for better quality assurance”. I can easily come up with explanations for why these statistics can be skewed, like “Ubuntu-loving plebeians do not come to complain to elite Lemmy users about their puny problems”. I’m curious what you think?
That’s why you’re supposed to remove 3rd party repos before you update, but nobody reads the release notes anymore, I guess.
Why doesn’t apk have a routine that disables 3rd party repos when doing a full system update?
I don’t know, I’m not on the Debian team. This is probably a question for them. I think the mailing list is public if you wanted to ask someone.
I read the release notes and followed all the relevant instructions and had zero issues, was a very smooth and easy process.
Doesn’t the upgrade manager of Debian disable them automatically, like Ubuntu does?
I don’t think so, because it shouldn’t be an automated process. Doing that blindly is a great way to have orphaned and incompatible package versions left on your machine.
Is this worse than an upgrade which breaks the system?
The update won’t break the system if you follow the update instructions (remove packages from those repositories first). The Ubuntu way does break the system (see my other comment).
I have no idea, but I don’t think the team would add a bunch of useless crap into the release notes for no reason. Doesn’t sound very Debian to me.
Here’s the link to the relevant section of the release notes, for your reference. It’s short.
Thank you! I guess I prefer Ubuntu’s safety net for upgrades.
The Debian safety net is not to use third-party repos at all.