apt/.gitlab-ci.yml, branch 2.9.30Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.302025-01-20T12:41:20Zgitlab-ci: Use platform: linux/i386 instead of i386/debian image2025-01-20T12:41:20ZJulian Andres Klodejulian.klode@canonical.com2025-01-20T12:34:33Zurn:sha1:afeaf6a442bb2603a1ebce096586cef48d065ba4
This is more generic, allowing us to use jak's runner again.
.gitlab-ci.yml: Request i386 test on x86 tag only2025-01-14T12:11:00ZJulian Andres Klodejulian.klode@canonical.com2025-01-14T11:59:34Zurn:sha1:9bd1f999f7111dd16c8647295c2776311b5e818e
This allows us to register workers that can only run amd64
images like mine which runs on podman and podman does not
allow pulling i386/ without specifying --arch i386
test: Check "${METHODSDIR}/sqv" not "/usr/bin/sqv"2025-01-01T21:27:31ZJulian Andres Klodejulian.klode@canonical.com2025-01-01T21:20:25Zurn:sha1:12a3dfe6b86ca01ac2d643086b8f30e5b9189290
This is the correct check to find out whether we have built
with sqv support.
debian: Plug sqv into the package build2024-12-22T22:52:05ZJulian Andres Klodejulian.klode@canonical.com2024-12-20T11:03:26Zurn:sha1:f5a24acea31248f98db51d7a2fd1d7b2198bb177
Our goal is for each platform to have one blessed OpenPGP verification
system: Platforms that support sqv get sqv, platforms that don't get
gpgv. To do so we hardcode the architecture list at build time.
At build time we check if /usr/bin/sqv exists, which is the condition
that apt uses to see if it should build with sqv support.
We use a slight hack here to build with sqv on the official Debian
buildds but use gpgv on Ubuntu by abusing the fact that Ubuntu
resolves alternative build dependencies, and gpgv is installed
in the buildd image.
CI: Set /bin/sh shell for travis user, so flock -c works2024-05-27T16:28:25ZJulian Andres Klodejulian.klode@canonical.com2024-05-27T16:27:40Zurn:sha1:d961b55347c83ebcea2fffee304e4795f34bc752
This is awkward.
test: Run working tests against the 3.0 solver2024-05-24T11:43:56ZJulian Andres Klodejulian.klode@canonical.com2024-05-19T17:31:48Zurn:sha1:1fbdc04be7547b8c4bb84f400329415ea0bc60b5
Implement --solver, --only, -skip flags for the test suite, and
run the test suite with the broken tests skipped against solver3.
CI: Pull from testing, unstable broken atm2024-01-10T12:32:24ZJulian Andres Klodejulian.klode@canonical.com2024-01-10T12:32:24Zurn:sha1:ecd2081a9aab7744771c896b5d7db2f70f120e17CI: Do not require UID 1000 for our test user2023-08-02T14:12:31ZJulian Andres Klodejulian.klode@canonical.com2023-08-02T13:28:02Zurn:sha1:aa56836331870d975c212a5df2f13db9ce3914bf
It seems the ubuntu:lunar image has a user with UID 1000 already
which was not the case in previous versions.
gitlab-ci: Install adduser2022-12-08T17:47:02ZJulian Andres Klodejulian.klode@canonical.com2022-12-08T17:47:02Zurn:sha1:dccd88881864a269f4e3326c221cc7297ddfb3f0Do not build documentation twice in CI2022-05-07T08:45:44ZDavid Kalnischkiesdavid@kalnischkies.de2022-04-21T10:47:47Zurn:sha1:cacf80aea3f1511aa1d8436fd4fd49d916390d10
The documentation will not realistically vary between architectures so
building it twice is just wasting time and resources.