Timeline for How to "autoremove" packages with aptitude package manager?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 8, 2022 at 14:58 | comment | added | Henk Poley | Apparently Aptitude::Delete-Unused is now default to true. | |
| Feb 18, 2017 at 17:39 | history | edited | lbs | CC BY-SA 3.0 | Add restrictions to the answer |
| Feb 18, 2017 at 17:20 | comment | added | lbs | @Alexey, IMHO, aptitude doesn't seem to be able to do that in your situation because it still regards the dependency present. Hope someone would point out if I misunderstand that. I think I should add some limitations to my answer. | |
| Feb 18, 2017 at 16:21 | comment | added | Alexey | Well, my question is how to reproduce apt-get autoremove with aptitude, because the behaviour of apt-get autoremove in my case works well for me. | |
| Feb 18, 2017 at 16:08 | comment | added | lbs | There is a clue in the footnote of Managing automatically installed packages, "they(auto installed packages) will be removed when there is no path via Depends, PreDepends, or Recommends to them from a manually installed package." Maybe that's the situation that you have met. aptitude why traces up to a manually installed package "ubuntu-gnome-desktop". I don't know whether aptitude treats the dependency valid even if the path is broken in the middle, but it seems to be the case. | |
| Feb 18, 2017 at 8:20 | comment | added | Alexey | No, they are not marked for deletion. By the way, normally, to remove packages marked for deletion and to perform other pending actions, it is enough to run aptitude install. | |
| Feb 18, 2017 at 7:52 | review | First posts | |||
| Feb 18, 2017 at 7:54 | |||||
| Feb 18, 2017 at 7:47 | history | answered | lbs | CC BY-SA 3.0 |