apt/test/integration/test-apt-cli-why, branch 3.1.14Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=3.1.142026-01-20T13:07:15Zwhy: Render info about all providers on virtual packages2026-01-20T13:07:15ZJulian Andres Klodejak@debian.org2026-01-20T13:04:20Zurn:sha1:34876ed2e5cdf504e2a4f9721486d279ae5f3be6
Refactor code into a doOne helper lambda, and then add loop
over the providers to use it.
This fixes a crash seen by Benjamin in a nice way than just
failing :)
Reported-by: Benjamin Drung
Introduce 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).