I'm really tired of hunting down all the APT "dependency" problems... There are already 7 tags that are used for something that ultimately translates to apt/dpkg in the "dependency problem" context:
- software-center which uses aptdaemon as backend which calls python-apt which uses gasp libapt for solving dependencies!
- update-manager which uses python-distupgrade which uses python-apt... blablabla.
- package .... I will talk about this later. But this is no way related with dependencies issues
- update I believe the first appearance of this tag was about [apt-get] [update], but still, alone doesn't tell me anything about the probable dependencies issues.
- upgrade I believe the first appearance of this tag was about [apt-get] [upgrade], but still, alone doesn't tell me anything about the probable dependencies issues.
- deb will talk about it along with package tag.
- packaging what have this to do with manipulating a package manager to install a package and hitting a dependency issue?
- package-management losing sanity
Why should I follow just so. many. tags!? All of these tags are used for dependency questions... it shouldn't be. They all are more likely to be accurately answered if they have apt tag. The topic is all over the place and the dependency is not helping either.
All questions about dependencies is just another layer to any of both dpkg (yeah, dpkg has dependencies issues too) or apt. Is just not useful tag if anyways you need add apt/dpkg to all dependencies question and it actually don't tell me something that a glance to the title I would know anyways.
Lets cleanup and remove the dependency and replace all the instances for apt or dpkg (or any other package system if you find them) or just remove it if there's alredy the tag applied.