<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration, branch 2.9.30</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.9.30</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.9.30'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2025-02-14T18:08:45Z</updated>
<entry>
<title>solver3: Only enqueue shared dependencies at the package level</title>
<updated>2025-02-14T18:08:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-05T19:37:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=943562a4ed2ddc80b84466d85e821037937f8b5c'/>
<id>urn:sha1:943562a4ed2ddc80b84466d85e821037937f8b5c</id>
<content type='text'>
Dependencies shared by all versions are enqueued at the package
level, so avoid enqueuing duplicates at the version level. This
presumably has no meaningful impact on performance, potentially
a negative performance impact on some workloads as we now need
to find the duplicates again; it can become useful when there
is a lot of backtracking.

More importantly though this improves error messages, because
now we can say that "all versions of foo depend on X", rather
than saying "foo=1 depends on X" and you are left wondering
why we did not select "foo=2".

In this commit though, improved error messages are not implemented,
they depend on redesigning the reason tracking to use clauses.

Also the rationale tracking includes a lot more dependencies of
the form "pkg:arch=version -&gt; pkg:arch" which are annoying. Improved
error messages should fold them into one node.
</content>
</entry>
<entry>
<title>solver3: Remove work rescoring in favor of unit propagation</title>
<updated>2025-02-14T18:08:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-12T19:39:33Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=2050ecb34a9e18cf1d8edbff8c52d456a7229162'/>
<id>urn:sha1:2050ecb34a9e18cf1d8edbff8c52d456a7229162</id>
<content type='text'>
Instead of expensive rescoring of all outstanding items, use
unit propagation to find new units after conflicts.

We still count the items when adding them; but unless they are
0 or 1, which they should not be, they don't have any effect:
The size field is now effectively static.

If the size of an optional clause changed to 1, it is inserted
a second time, and then moves up to the top of the optional
items per the Work::operator&lt; rules.
</content>
</entry>
<entry>
<title>test: Remove long obsolete FIXME for solver3</title>
<updated>2025-02-14T18:08:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-11T23:19:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=87f55c2bf50bbe4ba66e50e3b8bacd6d841fd1ab'/>
<id>urn:sha1:87f55c2bf50bbe4ba66e50e3b8bacd6d841fd1ab</id>
<content type='text'>
</content>
</entry>
<entry>
<title>test: Annotate the broken test cases</title>
<updated>2025-02-14T18:08:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-11T23:07:30Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=cfb8a9e8610d9595a6c1f8368835e7cfbcf67cc5'/>
<id>urn:sha1:cfb8a9e8610d9595a6c1f8368835e7cfbcf67cc5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>test-ubuntu-bug-614993: Avoid implicit upgrade-by-source requirement</title>
<updated>2025-02-14T18:08:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-11T21:13:27Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9028df1955a914230ba772776bac7fa0fb530ecf'/>
<id>urn:sha1:9028df1955a914230ba772776bac7fa0fb530ecf</id>
<content type='text'>
This allows it to work with solver3 before that feature is implemented.

This essentially reverts the change to that test made in
119a8d0ed19a4e946591b9aef7d662e14ca7ece5
</content>
</entry>
<entry>
<title>ResolveByKeep: Do not pass UPGRADE_ALL to EDSP solver</title>
<updated>2025-02-14T18:08:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-11T21:04:17Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=47b227a6dd609528a9f9f5c46d74f95919e21826'/>
<id>urn:sha1:47b227a6dd609528a9f9f5c46d74f95919e21826</id>
<content type='text'>
When we call an EDSP solver from ResolveByKeep(), we are not
in an upgrade context: In an upgrade context, we call the solver
directly from upgrade.cc instead of doing any Resolve() or
ResolveByKeep() calls.

This fixes the test-bug-602412-dequote-redirect test case,
where ResolveByKeep() was called as part of --fix-missing
</content>
</entry>
<entry>
<title>test-dont-forget-conflicts-via-unknown-architectures: Use install, not upgrade</title>
<updated>2025-02-14T18:08:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-11T20:26:10Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=fdc8682db546077cb24b2cc8861b2d5e4eee9da5'/>
<id>urn:sha1:fdc8682db546077cb24b2cc8861b2d5e4eee9da5</id>
<content type='text'>
The 3.0 solver does not support upgrade arguments to override the
policy.
</content>
</entry>
<entry>
<title>Fix test-phased-updates-upgrade</title>
<updated>2025-02-14T18:08:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-11T20:21:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=175f950685df84395547119f93aa305866d7e36d'/>
<id>urn:sha1:175f950685df84395547119f93aa305866d7e36d</id>
<content type='text'>
Our upgrade policy does not support specifying packagenames to
upgrade commands that are not subject to the policy. It's possible
this can be addressed at a later time, but let's not block the rest
of the test from running.
</content>
</entry>
<entry>
<title>solver3: Fix ordering of or groups</title>
<updated>2025-02-14T18:08:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-11T19:23:59Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=2423207431980cb10c085b0890523b1e802c9ab4'/>
<id>urn:sha1:2423207431980cb10c085b0890523b1e802c9ab4</id>
<content type='text'>
We inadvertently performed a global ordering of all possible
solutions for the or group using CompareProviders3.

This however is not correct, as we lose the ordering of the
dependency group *too* much. Mostly this has no effect, but
you can see for example in test-explore-or-groups-in-markinstall
various instances of it.

Adjust said test case to work with the 3.0 solver to the extent
possible under the current design. The 3.0 solver does Recommends
after processing any manually installed packages; as such the
various Recommends test cases do not work: A `Recommends: okay|upgrade`
will not upgrade `upgrade` if it visited `upgrade` first.

This may change at a future time, but the correct semantics for
Recommends are not entirely clear. Notably, the existing solver
is not always consistent. You can see here where they matter,
but recently I added test-solver-recommends-depends in which
the Recommends do not influence the choice of other Depends.
</content>
</entry>
<entry>
<title>solver3: Implement phasing as part of strict pinning rules</title>
<updated>2025-02-14T18:08:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-11T18:08:44Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ffe2565c36421401550d11990a761d70ac81d208'/>
<id>urn:sha1:ffe2565c36421401550d11990a761d70ac81d208</id>
<content type='text'>
Phased updates are ignored when strict pinning is on; such that
only the installed version will be available. By design of SAT
solvers, this means that the version selection clause is unit,
and hence the version can be directly propagated, i.e. that
choice is safe.
</content>
</entry>
</feed>
