apt/test/integration/test-apt-cli-why, branch 3.1.12Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=3.1.122025-05-19T15:20:09ZIntroduce apt why, apt why-not2025-05-19T15:20:09ZJulian Andres Klodejak@debian.org2025-05-19T12:17:23Zurn:sha1:7724d170751b3dc1717ba7a08881437cf7151996
These are implemented somewhat differently from aptitudes
why and why-not commands: They produce the actual solver
trace for why a particular decision has been taken.
For the why-not case, we need to explicitly discover our
specified package, as if nothing else depends on it in
our graph, it would otherwise always be undiscovered and
conflicts not detected (see e.g. level-3 in the test).