vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 02142b9eaedfa5b03e45a545274cf8f47b0f2ee0
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Wed Sep 10 23:17:58 2025 +0100
autopkgest: install dosfstools for test-loop-block
5804s Wed 2025-09-10 20:09:00 UTC (11669) Failed to execute mkfs.vfat: No such file or directory
Gbp-Dch: short
commit 0319d890bd42b46323896ebbea9cf778a1988900
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Tue Sep 9 22:30:51 2025 +0100
salsa-ci: enable ppc64el builds
Gbp-Dch: ignore
commit 645b1fa318ea01fe5a7d39a38dec96fea851ce03
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Tue Sep 9 18:43:35 2025 +0100
autopkgtest: use -20 instead of -22 for zstd compression
It is a bit too aggressive and can take multiple minutes for minor gains
Gbp-Dch: ignore
commit b8dc9b0ce7e9a3ec1bab6375241e64c7984a0ebc
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Mon Sep 8 21:00:54 2025 +0100
salsa-ci: switch to recommended entry point yml
Gbp-Dch: ignore
commit 152a2b314072dce37f95e32d0e03ce2de2237696
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Mon Sep 8 16:37:46 2025 +0100
autopkgtest: set default_device_timeout_sec=240
Reading EFI variables in kvm guests started being very slow recently
so the gpt-auto-root device times out a few seconds before it shows
up. This causes a lot of spurious failures in debci, where only 2 cpus
are given to the ci runner. Bump to 240s from 90s for now.
Workaround for https://github.com/systemd/systemd/issues/38842
Gbp-Dch: ignore
commit 6d464368789213075cc507ae3a350a9fb5178377
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Sat Sep 6 14:52:17 2025 +0100
autopkgtest: manually compress logs on failure
Debci started deleting files from the artifacts archive, even though it gets
compressed later. Compress logs manually at the highest ratio possible in
the test itself to try and avoid losing logs, as it makes triaging issues
impossible.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/s/systemd.png){kind=link}