i just used eukleides and xeukleides as an example - because they were packages 
I knew I could easily add and remove, this behaviour can be seen with any 
automatically installed packages:
Assuming package foo is automatically installed, once all packages depending on 
foo have been removed, trying to run aptitude unmarkauto foo, causes foo to be 
removed instead of being unmarked and kept on the system as I would expect. 
Interestingly using aptitude to remove the last package depending on foo (where 
foo is marked autoinstalled) causes foo to be removed too, while apt-get does 
not remove foo but simply warns that nothing depends on foo and that it can be 
removed.

If you're looking for another test case (assuming neither pi nor libcln5 is 
installed already), do
aptitude install pi 
apt-get remove pi
aptitude unmarkauto libcln5
although any other autoinstalled package will do just as well.
Incidentally, i originally noticed this behaviour under Gutsy, but the same 
happens in Hardy...

-- 
[gutsy] (un)markauto tries to remove packages
https://bugs.launchpad.net/bugs/173904
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to