On 2026-06-16, Kris Van Hees wrote: > The reproduced reports failure for the dtrace-tests deb due to the kernel > version string that is included in the USDT ELF notes. The kernel versions > on the two systems (orginal and comparison system) are not the same, and > thus this is flagged as a failure and it also affects the build-id which is > therefore different. > > 6.12.88+deb13-arm64 > #1 SMP Debian 6.12.88-1 (2026-05-15) > > vs > > 6.12.90+deb13-cloud-arm64 > #1 SMP Debian 6.12.90-1 (2026-05-22)
This is highly unlikely to be arm specific, just you happened to get the same kernel on the other tested architectures. Most likely this is due to GNUmakefile:KERNELS ?= $(shell uname -r) ... or various other calls to "uname -r" which somehow get embedded in the binaries. Ideally this can be patched out of your package, as relying on the kernel version matching is unlikely to be the same over the course of days, months or years as security updates for the kernel come out. I will take a quick stab at patches... live well, vagrant
signature.asc
Description: PGP signature
