On Fri Aug 30, 2024 at 8:29 PM CEST, Santiago Vila wrote:
It happens in testing already:
Yeah, I hadn't upgraded my packages since a few weeks.
I've ran a bisection with debbisect and it reported the following:
bisection finished successfully
last good timestamp: 20240809T084720Z
first bad timestamp: 20240809T144756Z
Additionally, diffing the build dependencies used by the two builds
I get the following:
$ diff good-pkgs bad-pkgs 75,76c75,76
< libaudit-common=1:3.1.2-4 < libaudit1:amd64=1:3.1.2-4+b1 --- > libaudit-common=1:4.0.1-1 > libaudit1:amd64=1:4.0.1-1 206c206 < nasm=2.16.01-1 --- > nasm=2.16.03-1I doubt libaudit caused the issue, since it is not a build dependency of xbyak (it is pulled in by apt), so it seems that nasm 2.16.03 changed something in its output which broke xbyak tests.
Thanks for the report! I'll now try to figure out if this is xbyak hardcoding something it shouldn't or if this is a legitimate issue introduced by the new nasm release.
signature.asc
Description: PGP signature
