apt/test/integration/test-apt-get-upgrade, branch mainDebians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=main2025-10-26T07:28:08ZAdjust test cases to treat 3.0 as default APT_SOLVER if not set2025-10-26T07:28:08ZJulian Andres Klodejak@debian.org2025-10-26T07:24:39Zurn:sha1:5e8e69cdd6b512480f3208298725e1e44c80f06e
Not needed so far because we export a default 3.0 APT_SOLVER, but
quite useful if we stop doing so (next commit).
solver3: Assume manual packages2025-05-26T10:45:12ZJulian Andres Klodejak@debian.org2025-05-26T09:19:11Zurn:sha1:717ca7922be8a025b8034dc840b2ad9befc3b171
If we have allowed the removal of manual packages, assume them
all before starting the solver. This should ensure that as long
as there is a solution that does not remove a manually installed
package, it is found.
This requires a sweeping set of changes in the test suite, but
ensures that we get "safe" behavior from the solver. We have
in particular seen that without asserting the installed packages,
several people ended up with ubuntu-minimal and perl removed in
a situation where that was not warranted, that is, they install
winehq, and then pull in some new perl packages in a newer version
than the installed one, and the solver chose to create a mismatched
version set, which then caused the main perl package to not be
installable.
Oops: 1b55173a-3526-11f0-b7ac-fa163e171f02
Oops: dbd5149e-36b9-11f0-bb74-fa163ec44ecd
solver3: Try candidate before installed version on upgrade2024-05-24T15:01:55ZJulian Andres Klodejulian.klode@canonical.com2024-05-19T15:42:34Zurn:sha1:acb77872861834d3c5b98ca2e81e0336a388e9f0
This fixes --no-strict-pinning attempting to upgrade all the versions
on the system. Adjust the upgrade test case accordingly:
1) no-strict-pinning pulls in systemd despite it being pinned down due
to a dependenc (this was true before this fix)
2) no-strict-pinning does not pull in the upgrade-simple because nothing
depends on it (this is what the test fixes)
test: Support the 3.0 solver in most existing test cases2024-05-24T15:01:35ZJulian Andres Klodejulian.klode@canonical.com2024-05-19T18:04:47Zurn:sha1:b5997949909ee9d5e9981c8311aea97c7b2620fd
Highlights:
- test-bug-618848-always-respect-user-requests: (Do not) Support 3.0 solver
A manually installed package is never removed just because we request
the removal of its dependency in solver3.
- test-bug-657695-resolver-breaks-on-virtuals: Support 3.0 solver
For manually installed packages, solver 3.0 would require some
new xserver-xorg-video-driver to Conflict+Replace+Provides the
old one (once the logic is implemented), but that does seem
reasonable.
- test-bug-720597-build-dep-purge: Support 3.0 solver
This needs a simple aptmark auto because pkga is removed by the
build-dep. But further adjustments are necessary because it weirdly
tested for no autoremovable packages before installing pkgc.
- test-bug-960705-*: Support 3.0 solver
Bit awkward to deal with; notably the protect to conflict doesn't
actually work anymore and that is a feature these days.
tests: support spaces in path and TMPDIR2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-15T16:20:26Zurn:sha1:3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2
This doesn't allow all tests to run cleanly, but it at least allows to
write tests which could run successfully in such environments.
Git-Dch: Ignore
test for or-group choice behaviour in upgrade2015-04-10T20:29:08ZDavid Kalnischkiesdavid@kalnischkies.de2015-03-10T20:05:02Zurn:sha1:f51401eb51939bfc932519601c43822a0aa5e343
In #780028 we were discussing how the or-group order should be more
important than keep-back decisions of 'upgrade'. We have this behaviour,
but to ensure it stays this way lets add a test for it.
Git-Dch: Ignore
test exitcode as well as string equality2015-03-16T17:01:54ZDavid Kalnischkiesdavid@kalnischkies.de2015-03-09T23:59:44Zurn:sha1:25b86db159fbc3c043628e285c0c1ef24dec2c6e
We use test{success,failure} now all over the place in the framework, so
its only consequencial to do this in the situations in which we test for
a specific output as well.
Git-Dch: Ignore
tests: support 'installed' release in insertpackage2014-10-23T14:54:27ZDavid Kalnischkiesdavid@kalnischkies.de2014-10-23T09:37:49Zurn:sha1:10e100e59a96ea7b6834a139beab5d9d70180633
It is sometimes handy to have an installed package also in the archive,
but this was until now harder than it should as you had to duplicate the
lines, which is especially dangerous while writing the tests as it
easily happens that these two lines divert and so the same-but-different
version detection kicks in.
Git-Dch: Ignore
fix progress output for (dist-)upgrade calculation2014-09-26T22:10:05ZDavid Kalnischkiesdavid@kalnischkies.de2014-08-17T10:30:21Zurn:sha1:2a884c612b10b27f4be2cc6dd689bfe448d9361a
Previously, we had a start and a done of the calculation printed by
higher-level code, but this got intermixed by progress reporting from an
external solver or the output of autoremove code…
The higherlevel code is now only responsible for instantiating a
progress object of its choosing (if it wants progress after all) and the
rest will be handled by the upgrade code. Either it is used to show the
progress of the external solver or the internal solver will give some
hints about its overall progress. The later isn't really a proper
progress as it will jump forward after each substep, but that is at
least a bit better than before without any progress indication.
Fixes also the 'strange' non-display of this progress line in -q=1, while
all others are shown, which is reflected by all testcase changes.
fixup various UI issues in the test2013-10-09T12:02:42ZMichael Vogtmvo@debian.org2013-10-09T12:02:42Zurn:sha1:d029b71845cd10ecb46893627dfe6de669ba689d