APT::AutoRemove::SuggestsImportant "false" should be the default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Ubuntu) |
Opinion
|
High
|
Unassigned | ||
Bionic |
Opinion
|
High
|
Unassigned | ||
ubuntu-release-upgrader (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
After an upgrade to 17.10, I took a look at how much cruft I had accumulated on my system, and started marking various packages 'auto' which I know I don't care about keeping installed.
apt autoremove didn't remove nearly as much stuff as I expected, and as I dug down into some of them I found that a number of them were being kept because other packages on the system have Suggests: referencing them.
This is asymmetric and wrong. If Suggested packages are not automatically installed by default, then a Suggests should also not prevent a package from being automatically removed.
After a web search led me to 'https:/
Related branches
- Brian Murray: Approve
-
Diff: 29 lines (+11/-0)2 files modifiedDistUpgrade/DistUpgradeCache.py (+3/-0)
debian/changelog (+8/-0)
Changed in apt (Ubuntu): | |
importance: | Undecided → High |
tags: | added: rls-bb-incoming |
tags: | removed: rls-bb-incoming |
tags: | added: id-5a73419b7c0ad42ef48287b0 |
Changed in apt (Ubuntu Bionic): | |
status: | New → Opinion |
Changed in apt (Ubuntu Bionic): | |
status: | Triaged → Opinion |
Changed in ubuntu-release-upgrader (Ubuntu Bionic): | |
status: | New → Triaged |
tags: | added: id-5ab94d08cbdbbc3e7f60dad4 |
I package A suggests package B and you install B because C depends on it, and now you remove C a year later, removing B might or might not be a good idea. I think it's better to be on the safe side here and not remove stuff the user might have come to rely on in autoremove.