Hi, On Thu, Jun 27, 2019 at 06:57:15PM +0200, Paul Gevers wrote:
Source: init-system-helpers, chrony Control: found -1 init-system-helpers/1.57 Control: found -1 chrony/3.4-4 Severity: important X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-updateDear maintainers, With a recent upload of init-system-helpers the autopkgtest of chrony fails in testing when that autopkgtest is run with the binary packages of init-system-helpers from unstable. It passes when run with only packages from testing. In tabular form: pass fail init-system-helpers from testing 1.57 chrony from testing 3.4-4 all others from testing from testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of init-system-helpers to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? If needed, please change the bug's severity.
Actually, init-system-helpers is not responsible for the chrony test suite breakage. It would have happened with any package triggering the test. So this failure is solely chrony’s fault.
The cause is that the chrony upstream-simulation-test-suite test pulls clknetsim HEAD which introduces new debugging features unknown to chrony’s 111-knownclient and 112-port tests. I’ll have a fix for this soon!
Meanwhile, can the release team let migrate init-system-helpers before I fix chrony?
[snip…]
Cheers, Vincent
signature.asc
Description: PGP signature