apt/test/integration/test-apt-cli-why, branch main Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=main 2026-05-17T18:10:59Z solver3: Follow installed Suggests earlier 2026-05-17T18:10:59Z Julian Andres Klode jak@debian.org 2026-05-17T18:09:37Z urn:sha1:10a05580e74e2ba5a5768d45c6f9feff216c8689 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 packages 2026-01-20T13:07:15Z Julian Andres Klode jak@debian.org 2026-01-20T13:04:20Z urn: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-not 2025-05-19T15:20:09Z Julian Andres Klode jak@debian.org 2025-05-19T12:17:23Z urn: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).