Le 29.10.2013 03:51, ruckus rogue a écrit :
On Mon, Oct 28, 2013 at 6:21 PM, <berenger.mo...@neutralite.org>
wrote:
They have been installed because zonecheck probably needs them (
required )
but if they are recommended by other packages then they will not be
removed.
I do not think there is any solution to fix that. If there is one, I
would
be happy to learn it.
Still doesn't make sense to me. I install "zonecheck" only. And that
brought in the dependencies. Then I uninstalled 'zonecheck' it should
have taken back those dependencies with it. None of the packages were
marked recommended. So how could other packages outside zonecheck
need
them?
You have package A already installed. It recommends to install package
C, but you did not installed it.
Then, you ask the system to install package B, which depends on C. So,
C is still installed.
Finally, you remove B. B is uninstalled, but C stays on the system
because A recommends it. The system simply have no clue that it was
installed because of B and not A, so it keeps it. There is no way to
remember the whole decision chain which led to install a package (system
can not know that you did not installed it because it was recommended by
A), and if those links would have been kept, it would be painful for
users to handle every link by hand, when you manage lot of packages.
I have also noticed that sometimes packages which were marked
Automatically Installed becomes only Installed, often after a problem
while downloading a package list, but this is a bug that I have no idea
about how exactly to reproduce.
What I suggest you when you just want to try a package and remove it
after (which is something I do often enough to be bothered by the same
issue as you), is to use the aptitude ncurse interface. Go on details of
the target package, and purge all it's dependencies ( quite easy: go on
"depend", and press "_". Same for recommends ). Then, you will have
broken packages. Just fix them and go. My opinion is that for this
usage, it is better to fix those breakages by hand rather than using the
solver (I simply do not like the solver at all), but it is your choice.
Anyway, I just don't remember this behaviour before. I thought it was
new and was trying to find out why all packages that come dependent
with a package don't leave when that package leaves.
My first really used installation of Debian is something like 4-5
years. I never installed gnome or KDE because of their dependencies, and
have always searched for minimal systems (because windows learn me that
the more useless stuff installed on your computer, the more likely you
will have troubles). The only change I think to have noticed was the
recommended packages becoming automatically installed at some point, but
I am not sure that it was not that I simply discovered that field.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/3265010e219e1abc05c3472896b38...@neutralite.org
