Nov 10, 3:41pm

That's a reasonable choice — a general wishlist is more robust, and the maintainer (who knows how the garbage detection actually works) is the right person to pin down the mechanism. A few adjustments to match that intent:

Keep the kernel case strictly as an example, not as the explanation. Move the "More details about this example" section (the cventin comparison, NeverAutoRemove discussion) into a clearly-labeled "Example" or "Background" section, and avoid asserting any specific protection mechanism. E.g.:

"In this case, the package is not proposed for autoremoval either, for reasons that are not documented (possibly some kernel-protection mechanism); the maintainer may be able to clarify."

Phrase the feature request in mechanism-free terms. Instead of "try chains from NeverAutoRemove packages", the general formulation is something like:

"When no chain from a manually installed package is found, aptitude could report why the package is nevertheless kept installed — e.g. a dependency chain from an automatically installed package that is itself protected from autoremoval, or any other reason aptitude's own logic has for not considering the package removable."

That way the request doesn't depend on whether the cause is NeverAutoRemove, libapt kernel protection, or something else, and it directly serves the user's actual need (understanding "why is this still here?").

What survives as the core ask — three things, all general:

  1. aptitude why output should not say "No dependencies require to install X" when installed packages do in fact depend on X (your other bug covers the message wording).
  2. When there's no chain from manual packages, aptitude should ideally explain what keeps an automatically installed package installed (this bug).
  3. The criteria aptitude uses to decide a package is not autoremovable are not documented — worth one sentence, since it's what made your example hard to interpret, and it's a doc gap regardless of which mechanism applies.

With that structure, the kernel details become supporting evidence rather than claims a maintainer could rebut, and the report stays valid whatever their answer is.

Nov 10, 3:41pm

This is a shared conversation and may include unverified content that doesn't reflect Mistral AI's views. Login to resume chatting.

Vibe can make mistakes. Check answers. Learn more