Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=main 2025-10-26T07:28:35Z 2025-10-26T07:28:35Z Julian Andres Klode jak@debian.org 2025-10-26T06:59:52Z urn:sha1:487ce0983c2008991566b4cfb269fd7d29a08e98 We never implemented comment support in the skip test file for -j as we only run with -j, but the debian/tests/run-tests runs without parallelism. 2025-10-26T07:28:35Z Julian Andres Klode jak@debian.org 2025-10-26T06:58:43Z urn:sha1:78da58ec0c1cdbda6cdd22c63f85ddac703bb0d6 Remove the exports for the default as we don't want those inherited, they can just be reset. Set the skip file to /dev/null when a solver is selected, to make sure that tests don't fall back to the default skip file. 2025-10-25T20:16:54Z Julian Andres Klode jak@debian.org 2025-10-25T15:42:11Z urn:sha1:c5c5d10d1b2ac0a589102315840c4f2a075b18c1 Enable the new solver by default and remove the vendor-specific configuration change in Ubuntu's drop-in. 2025-02-14T18:08:45Z Julian Andres Klode julian.klode@canonical.com 2025-02-11T15:34:54Z urn:sha1:0c79613a5ef111ae09e1c94a2866f63fbf51c524 Strip everything after "#" and spaces before it. 2025-02-12T13:54:32Z Arnaud Rebillout arnaudr@kali.org 2025-02-12T13:50:48Z urn:sha1:f67e9858fd0f12c2b8aa6ca9450cde427513d883 The `--skip` option was introduced in commit 1fbdc04be7547b8c4bb84f400329415ea0bc60b5, and it was broken straight from the start for the case where `TESTTORUN` is not set (see last hunk in this commit, the mistake is obvious). It went unnoticed as the GitLab CI runs tests with the `-j` option, so `TESTTORUN` is set. While ci.debian.net runs without -j, but doesn't skip any test, so it doesn't trigger the bug either. 2024-12-19T22:41:01Z Julian Andres Klode julian.klode@canonical.com 2024-12-19T21:11:04Z urn:sha1:a00fbbdb28cc31e78882301c2efe7218583ab4cb Remove the test case for MD5 and expired signatures, as we can't create them (can't set signing digest, and can't set signature expiry). Tests for them have been added to test-method-gpgv instead. We override sq in a function with cert-store and key-store set to none. This supports both sq 0.40 and sq 1.0. 2024-06-13T12:32:32Z Julian Andres Klode julian.klode@canonical.com 2024-06-06T09:40:14Z urn:sha1:bfb9f2124b8f9da48b53d279278de3f8f0a00b82 When a test-* file is created but not executable, we'd ignore the argument and then our subprocess would run the entire test suite itself, sequentially. Silly. Let's just see if the file exists instead, then the test will fail. 2024-05-24T11:43:56Z Julian Andres Klode julian.klode@canonical.com 2024-05-19T16:52:20Z urn:sha1:03f4568283205a26386584002b9ec740c55c9fb7 This makes things a bit nicer. We also include a list of passed tests here, to use with --only to validate solver3 changes, as well as the list of skipped tests. But too lazy to implement these for the non-parallel case. 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. 2022-05-07T08:45:44Z David Kalnischkies david@kalnischkies.de 2022-04-21T10:51:20Z urn:sha1:e5aa5c04ecbd3cdab611794cebf9eb3aa8cbddd4 We use 'stty sane' to combat against stepped output and co caused by (especially) failed tests, but it does so many things that it occasionally fails to reset some bits in the parallel interaction we have with it which fails the tests without a real problem in apt… Ideally we would be better at stitching the output together, but for the time being lets ignore these failures instead to stabilize the tests.