Hi, Cyril Brulebois <[email protected]> (2026-03-09): > We have a single target failing on arm64: build_cdrom_grub, presumably > following the latest linux update. > > Verifying built depthcharge image: > Keyblock: > Signature: valid > Size: 0x4b8 > Flags: 23 !DEV DEV !REC !MINIOS > Data key algorithm: 4 RSA2048 SHA256 > Data key version: 1 > Data key sha1sum: d6170aa480136f1f29cf339a5ab1b960585fa444 > Preamble: > Size: 0xfb48 > Header version: 2.2 > Kernel version: 1 > Body load address: 0x100000 > Body size: 0x2004000 > Bootloader address: 0x2103000 > Bootloader size: 0x1000 > Flags : 0 > Body verification succeeded. > Config: > kern_guid=%U --- quiet > > Image with compression 'lzma' is too big for this board. > Couldn't build a small enough image for this board. This is usually > solvable by making the initramfs smaller, check your OS's documentation on > how to do so. > stat: cannot statx './tmp/cdrom_grub/depthcharge/gru.kernel.img': No such > file or directory > /bin/sh: 11: arithmetic expression: expecting primary: " / 512 + 2048" > > Full build log: > > https://d-i.debian.org/daily-images/arm64/20260309-01:19/build_cdrom_grub.log
Ping? With the other issues (src:at-spi2-core/src:libxres, src:zlib) out the way, we're back to this single-target FTBFS on arm64. Cheers, -- Cyril Brulebois ([email protected]) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
