apt/test/integration/test-apt-install-file-reltag, branch mainDebians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=main2026-01-05T21:20:24Zsolver3: Rename decision to assignment2026-01-05T21:20:24ZJulian Andres Klodejak@debian.org2025-12-28T15:56:28Zurn:sha1:21d099878ed8c34f3b13747bcec380e0402e57a3
The previous use of decision here conflicted with the use
of decision level and the general notion of having made a
decision, because the assignment might have been propagated
as a matter of fact.
solver3: Verbose error messages2025-03-08T22:18:05ZJulian Andres Klodejulian.klode@canonical.com2025-03-06T19:07:30Zurn:sha1:3967b75ae4a10d0d79560dfecb8eb210aad4f4f2
Introduce a new function, LongWhyStr() that returns a longer
reason for why something is being installed (or not).
This does the same path walk as the other function does, but
it renders the clauses at each level, and one per line, so
the whole output is a lot more informative.
It is a separate function to keep the existing debug messages
use the simple single line implication graph
We remove the other special case in AddWork() for empty solutions
to mke use of the general case in Solve() instead, and then adapt
the case in Solve() to the same case as in Enqueue(). This also
happens to fix the bug that when we encountered an empty clause
we just printed the clause had no solution, but not how we got
to install the package with the clause.
Adapt the test suite for the changes which is an annoying amount
of paperwork.
test: Fix 7 test cases for 3.0 solver, annotate others2025-02-14T18:08:45ZJulian Andres Klodejulian.klode@canonical.com2025-02-11T16:02:00Zurn:sha1:e86f3d875a48987a026f79aa4e19eeda4ad01b3b
Fix the test cases we can fix directly; add annotations where we
know what work is needed, next we'll look at the other bugs.
Support release selector for volatile files as well2018-05-11T15:58:46ZDavid Kalnischkiesdavid@kalnischkies.de2018-01-26T22:33:25Zurn:sha1:ce9223cc4e4ffcc43d17ae97ff8c57fb759a2c49
The syntax is a bit awkward, but it is the same as for a package name
and introducing another syntax wouldn't really help usability, so with
apt install ./foo.deb/experimental you will get the dependencies of foo
satisfied by your default release, but if this wouldn't satisfy the
version requirements the candidate for this dependency is switched to
the version from the experimental release. The same applies for apt
build-dep ./foo.dsc/stable-backports which was the initial request.