Hi, On Tue, 2026-01-06 at 17:41 +0000, [email protected] wrote: > A new failure has been detected on builder elfutils-snapshots-coverage while > building elfutils. > > Full details are available at: > https://builder.sourceware.org/buildbot/#/builders/250/builds/294 > > Build state: failed 'autoreconf -f ...' (failure) > Revision: 0f858ac95fc7296f85d95f9b0ab7d6a70085123a > Worker: snapshots > Build Reason: (unknown) > Blamelist: Mark Wielaard <[email protected]> > > Steps: > > - 0: worker_preparation ( success ) > > - 1: git checkout ( success ) > Logs: > - stdio: > https://builder.sourceware.org/buildbot/#/builders/250/builds/294/steps/1/logs/stdio > > - 2: autoreconf ( failure ) > Logs: > - stdio: > https://builder.sourceware.org/buildbot/#/builders/250/builds/294/steps/2/logs/stdio
Which says: > xz: Failed to enable the sandbox > tar: This does not look like a tar archive > tar: gettext-0.23.1: Not found in archive > tar: Exiting with failure status due to previous errors > autopoint: *** infrastructure files for version 0.23.1 not found; this is > autopoint from GNU gettext-tools 0.23.1 > autopoint: *** Stop. > autoreconf: error: autopoint failed with exit status: 1 This is somewhat annoying. It is a conflict between the host kernel (almalinux 5.14.0-611.16.1.el9_7.x86_64) and the debian stable container xz-utils (5.8.1-1). https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121085 For now we just have to wait till either the almalinux kernel is fixed or the xz-utils in debian stable is updated. Sigh, Mark
