Comment 4 for bug 173904
Revision history for this message
| Heinrich Kruger (heindsight-deactivatedaccount) wrote Re: [gutsy] (un)markauto tries to remove packages | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
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...