4

If I attempt to uninstall a metapackage, apt does not actually remove the metapackage's dependencies, only the "wrapper" itself. Even when running apt autoremove, these subpackages are not listed. I find it confusing that autoremove removes dependencies for most normal packages, but not many metapackages. Why is this?

Improve this question

2 Answers 2

Reset to default
6

Meta-packages are not magic in any regard: the concept "of meta-package" is not part of the APT system - a meta-package is simply a package which doesn't have actual content, just dependencies. So removing them has the same effect as removing a package with actual content that also depends on some other stuff, like a web server application module will require a web server, but when you remove it - the web server should still stay installed.

That being said, APT keeps track of which packages were automatically installed because another package requested them (like a meta-package requesting "actual" packages, or a web server application module requiring a web server), and once you remove the requiring package APT will suggest you run apt autoremove to get rid of such automatically installed packages.

The main problem with "meta-packages" as they are used in the Ubuntu operating system is that they depend on a lot of packages, essentially installing a huge selection of software with a single install. When installing so many packages, especially such that are very closely tied together - you can get a lot of cross-dependencies: the meta package requires packages A, B and C for you, but A also depends on B and B (maybe surprisingly) also depends on A. So if you remove the meta-package, only C will get removed.

As a concrete example, lets consider the LXDE meta-package lubuntu-desktop:

The following answers have more details:

Improve this answer
7
  • Thanks for your answer -- I guess I should have stated my question better. A lot of times it seems that apt autoremove does not show any of the metapackage's dependencies, while it would if a "normal" package was uninstalled. Any thoughts on that?
    – tech4him
    Jan 20, 2019 at 21:53
  • @tech4him: I edited my answer to address your edit
    – Guss
    Jan 20, 2019 at 21:55
  • 1
    Thanks! It has happened for most alternative desktop environments I've tried to install on a regular (GNOME) base system (xubuntu-desktop, kubuntu-desktop, lubuntu-desktop, etc). To uninstall, I've always had to go back to the Apt log.
    – tech4him
    Jan 20, 2019 at 21:57
  • @tech4him - after a bit more research, I have a better answer for you.
    – Guss
    Jan 20, 2019 at 22:22
  • That example would also explain why a package with a cyclic dependency, but installed directly (not via metapackage), would still autoremove. When it is below another "layer", those asumptions do not work as well. I'm assuming cyclic dependencies are less common in non-"core" packages such as desktops (but still possible).
    – tech4him
    Jan 20, 2019 at 22:40
2

ALL packages installed by the Ubuntu's ubiquity installer are apt-marked 'Manual' (instead of 'Auto), making all those packages ineligible for autoremoval.

You can still remove them, of course, you just cannot autoremove them.

The Ubuntu Server, Minimal Image, and Cloud Image installers are not based on ubiquity, and their packages are eligible for autoremoval.

If you are not familiar with apt-marking, it's simply how apt keeps track of which dependencies were specified by the admin ('Manual'), and which were pulled in as dependencies ('Auto'). See man apt-mark for more information about it.

The reason for the non-standard Ubiquity behavior is to protect you: Folks modify their desktop systems in all kinds of ways, including ways that require removal of the metapackage. Most users don't usually intend to remove their entire desktop, doing so unexpected can be a rather Significant Emotional Event, so the Ubuntu developers made the change to protect users from their own (unintended) folly. After all, Ubuntu is intended for new and unskilled users, too.

Folks who want to prune their packages to just what they actually use (we all have tried that at one time or another) will find it much easier to start from the Minimal Image and build up rather than fight the apt-marking to cut down.

Improve this answer
2
  • That's a very good point, although I was mostly asking about a secondary metapackage install after the system was already installed. Does this answer address this at all, or is it only regarding initial install? It's helpful either way -- I'd just like to clarify.
    – tech4him
    Jan 23, 2019 at 23:53
  • 1
    After the installed system is running, then the Ubiquity change no longer applies, of course. All apt actions will be normal: Newly-installed dependencies will be apt-marked 'auto', and will be eligible for auto-removal.
    – user535733
    Jan 24, 2019 at 0:15

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .