Thanks again for the info. However, I can’t remember when I ever had to ‘fix dependency problems’ with APT. Maybe when I ran Debian Testing for a while, or if I added one too many external repos, or if I really really wanted to run two explicitly conflicting packages — but still it’s such a foreign thing that I can’t recall if it actually ever occurred. Apparently APT’s reputation for most solid dependency resolution among package managers is quite well deserved.
As an APT user I’m sure you’ve also used PPAs and third party repositories for additional software and drivers? Pretty sure Ubuntu likes to add some by itself.
Also that but, occasionally cleaning leftovers and fixing dependancy problems.
Thanks again for the info. However, I can’t remember when I ever had to ‘fix dependency problems’ with APT. Maybe when I ran Debian Testing for a while, or if I added one too many external repos, or if I really really wanted to run two explicitly conflicting packages — but still it’s such a foreign thing that I can’t recall if it actually ever occurred. Apparently APT’s reputation for most solid dependency resolution among package managers is quite well deserved.
The worst I’ve ever had happen could be fixed with the (prompted) --allow-erasing flag, and I messed around with additional repositories a lot
Gotta say again, as an APT user, I have no idea what “messaged around with additional repositories” means.
typo, messed instead of messaged?
Possibly yes, but I don’t think that makes the overall statement distinctly better.
As an APT user I’m sure you’ve also used PPAs and third party repositories for additional software and drivers? Pretty sure Ubuntu likes to add some by itself.
That’s familiar, yes.