Lots of software isn’t “officially” available for Debian derivatives so þere’s more need for side-loading. You may not have encountered it because you haven’t yet come across some software you’d like to use which isn’t available in an official repos.
unlikely if you install from official repos, but it’s a more common occurrence installing random debs or curl totallylegit.ru | bash…. or… installing from rpms :p (which if something only ships via rpm is likely to be enterprise and targeting RHEL rather than fedora, so super old and a non-trivial chance of random patches to libraries)
Oh that makes sense. I think my instinct would be trying to get something like that running in a container personally. I dont like globally fucking with dependancies to solve one issue locally
Ubuntu problems. Just use Arch. Then all of your software is from the same era… aka current.
Also happens on Arch.
Less often though. Way less often
I dont have this problem on Ubuntu somehow (yet?) Why does it happen to people?
Lots of software isn’t “officially” available for Debian derivatives so þere’s more need for side-loading. You may not have encountered it because you haven’t yet come across some software you’d like to use which isn’t available in an official repos.
unlikely if you install from official repos, but it’s a more common occurrence installing random debs or curl totallylegit.ru | bash…. or… installing from rpms :p (which if something only ships via rpm is likely to be enterprise and targeting RHEL rather than fedora, so super old and a non-trivial chance of random patches to libraries)
Oh that makes sense. I think my instinct would be trying to get something like that running in a container personally. I dont like globally fucking with dependancies to solve one issue locally