vcswatch reports that
this package seems to have a new changelog entry (version
5.44, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit 51fa86dd3c4baf388828ed3a5cff4d69c2318aa6
Author: Simon McVittie <smcv@debian.org>
Date: Mon Jan 20 10:52:17 2025 +0000
Update changelog
commit 8515dbf2cef9249dc3003dd6470559c78cbe27e2
Merge: b1503a6 e7b996f
Author: Simon McVittie <smcv@debian.org>
Date: Sat Jan 18 10:16:30 2025 +0000
Merge branch 'wip/smcv/1078205' into 'master'
virt-podman: Document that full systemd functionality needs CAP_SYS_ADMIN
See merge request ci-team/autopkgtest!396
commit b1503a6f744bc33b89d71dad8f3d8195b7c2b089
Merge: 18bed60 9e86d5a
Author: Simon McVittie <smcv@debian.org>
Date: Sat Jan 18 10:10:17 2025 +0000
Merge branch 'wip/smcv/1093275' into 'master'
tests: By default only exercise timeouts on known-fast architectures
See merge request ci-team/autopkgtest!506
commit 9e86d5a2d9c18064fad57d8dc80f6b07c8cd6107
Author: Simon McVittie <smcv@debian.org>
Date: Fri Jan 17 10:26:13 2025 +0000
tests: By default only exercise timeouts on known-fast architectures
We test timeouts by making one part of a test use sleep(1) to block
for a while, trying to guess a timeout *T* that will be long enough to
accommodate initial test setup (up to that point), setting autopkgtest's
timeout to a little more than *T*, and making sleep(1) sleep for
considerably more than *T*. If all goes well, this means that everything
before the targeted point runs (and we can confirm this by screen-scraping
the log), and then the test times out (and we can check that autopkgtest
responds correctly to that).
However, choosing an appropriate value of *T* is difficult. If we make
*T* too long, successfully running the autopkgtest test suite takes that
much longer, even on an arbitrarily fast machine; this is undesirable
because full coverage implies running the test suite several times
with different backends, which can be extremely time-consuming already
(see #1020699). Conversely, if we make *T* too short, we can hit test
failures on slower machines like riscv64, with the test timing out
before initial setup has finished, meaning autopkgtest will (correctly!)
report the failure differently.
In practice the timeouts we have chosen are all tuned for reasonably
fast developer machines like x86, and the code under test is identical
on any architecture, so skip these tests by default on architectures
that are not known to be fast and reliable.
Developers can set `AUTOPKGTEST_TEST_TIMEOUTS=1` to force these tests
to run even on slower architectures, or `AUTOPKGTEST_TEST_TIMEOUTS=0`
to force them to be skipped even on fast architectures.
Signed-off-by: Simon McVittie <smcv@debian.org>
Closes: #1093275
commit 18bed60326297786e07651557df851fedd25aaad
Author: Simon McVittie <smcv@debian.org>
Date: Fri Jan 17 09:26:28 2025 +0000
Remove obsolete alternative dependency on pep8
pycodestyle has been available since at least Ubuntu 18.04 and Debian 10,
which are both older than our documented minimum host system.
Gbp-Dch: short
Closes: #1093161
commit 49b838c6da2738562b511a8ea6dd1196f65629ad
Author: Simon McVittie <smcv@debian.org>
Date: Sat Dec 21 12:30:17 2024 +0000
d/README.source: Mention some apt features that we cannot use yet
Signed-off-by: Simon McVittie <smcv@debian.org>
commit e7b996fdabd815e6d227953aa4459166192c41d0
Author: Simon McVittie <smcv@debian.org>
Date: Mon Dec 9 10:44:18 2024 +0000
virt-podman: Document that full systemd functionality needs CAP_SYS_ADMIN
See https://bugs.debian.org/1078205 and
https://github.com/containers/podman/discussions/23558 for more details.
Closes: #1078205
Signed-off-by: Simon McVittie <smcv@debian.org>
![[bug history graph]](https://qa.debian.org/data/bts/graphs/a/autopkgtest.png){kind=link}