Package: release.debian.org Severity: normal The upload of glibc 2.28-4 has trigger the pacemaker autopkgtest, which failed due to bug#917801, caused by the migration of corosync 3.0.0-1 to testing on 2018-12-26:
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pacemaker/1613604/log.gz It is considered as a regression introduced by the glibc upload, as the reference used is the following from 2018-12-24, which still uses corosync 2.4.4-3. https://ci.debian.net/data/autopkgtest/testing/amd64/p/pacemaker/1581332/log.gz I believe the autopkgtests should not assume that a package still works in testing if it has worked at some point in the past. The best would be to retry the tests purely in testing if the one from testing + tested package fail. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
