summaryrefslogtreecommitdiff
path: root/test/integration/test-apt-cli-why
Commit message (Collapse)AuthorAgeFilesLines
* solver3: Follow installed Suggests earlierJulian Andres Klode2026-05-171-2/+7
| | | | | | | We accidentally followed "keepauto" and friends earlier, breaking `apt why` for suggested packages. Reported-By: uau on IRC
* why: Render info about all providers on virtual packagesJulian Andres Klode2026-01-201-0/+7
| | | | | | | | | | 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-notJulian Andres Klode2025-05-191-0/+71
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).