Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.9.4 2024-05-24T15:01:55Z 2024-05-24T15:01:55Z Julian Andres Klode julian.klode@canonical.com 2024-05-23T11:24:25Z urn:sha1:4a2b89be6fa73b9c193d5b70e11a9305272efc3e We also need to issue a MarkDelete() if the package is marked for installation currently but should not be, not only if it did not have a previous version. This fixes the final test in test-multiarch-barbarian, the others only needed adjustments to mark all packages as automatic. 2024-05-24T15:01:55Z Julian Andres Klode julian.klode@canonical.com 2024-05-21T14:57:56Z urn:sha1:aaa9e415ce48964726401462767d6038da6d82e7 When restoring previously solved items, we try to restore items that have become unsolved again by skipping items that have a solved solution. Well at least we thought we did, but we accidentally had a "not" in there that inverted the meaning, hence we lost work items on backtracking. This mostly did not seem to have caused any issues, I stumbled over it while trying to add `autoremove` listings to `upgrade`, but fixing it also fixes: test-ubuntu-bug-1130419-prefer-installed-ma-same-siblings This used to say "E: Broken packages", meaning the solver lost a non-optional install request and the 2nd stage solver caught an incomplete solution. Also test-bug-735967-lib32-to-i386-unavailable restores the legacy solver behavior, so win win? 2024-05-24T15:01:55Z Julian Andres Klode julian.klode@canonical.com 2024-05-20T12:59:58Z urn:sha1:cd245a57f273d3c069543c19d6ac31c84879ce7b This somewhat improves reliability of not breaking Recommends, e.g. if the Recommends gets tightened. One test case enabled by this now is the test-resolver-provider-exchange, which with a simple change to allow removal of automatically installed packages works now. 2024-05-24T15:01:55Z Julian Andres Klode julian.klode@canonical.com 2024-05-19T19:24:08Z urn:sha1:0fa3b176652ff10276569a478c910ca866a4da5d As per the test-suggests-promoted-to-recommends test. This is still a bit messy as we ignore alternative choices and only check the last one, but um seems useful? 2024-05-24T15:01:55Z Julian Andres Klode julian.klode@canonical.com 2024-05-24T13:17:41Z urn:sha1:56737e4bdb58e03eeea6f915259f3a18a79642a3 The previous commit basically fixes this, it just requires some minor small adjustments 2024-05-24T15:01:35Z Julian Andres Klode julian.klode@canonical.com 2024-05-19T18:04:47Z urn: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. 2024-05-24T11:43:56Z Julian Andres Klode julian.klode@canonical.com 2024-05-20T11:17:35Z urn:sha1:0c700522df1c96fd591020e7b3e29bc7e36dec14 We do not show them yet, so let's ignore them so we can focus on getting the rest of the tests to work. 2024-05-24T11:43:56Z Julian Andres Klode julian.klode@canonical.com 2024-05-19T17:31:48Z urn:sha1:1fbdc04be7547b8c4bb84f400329415ea0bc60b5 Implement --solver, --only, -skip flags for the test suite, and run the test suite with the broken tests skipped against solver3.