Re: Various d-i daily build failures: arm64, armhf, riscv64
Cyril Brulebois <[email protected]>
| Newsgroups | gmane.linux.debian.devel.boot,gmane.linux.debian.ports.arm,gmane.linux.debian.riscv |
|---|---|
| Organization | Debian |
| Message-ID | <[email protected]> |
Hi, Emanuele Rocca <[email protected]> (2026-01-06): > On 2026-01-06 02:21, Cyril Brulebois wrote: > > For some reason (possibly because of frequent errors while refreshing > > repositories from Salsa), the daily build overview task was commented > > out and the overview hadn't been updated since end of last month: > > https://d-i.debian.org/daily-images/daily-build-overview.html > > > > I've cronned it back, and logs are published again. It seems we have a > > few failures right now, namely: > > - arm64 > > - armhf > > - riscv64 > > Perhaps related to the recently introduced Breaks on armhf, arm64, and > riscv64? > https://salsa.debian.org/kernel-team/linux/-/commit/c660788db61eea9d22bc429b987441b05b9302bb I don't think that's /directly/ related (the fixed package is even in testing, and it's not listed in build logs AFAICT), but that hinted me into the right direction I think… A failure can look like this on arm64: make[2]: *** No rule to make target 'tmp/cdrom_grub/lib', needed by 'arm_grub_efi'. Stop. Before, that looked like this: Searching 'tmp/cdrom_grub/lib' for dtbs compatible with pattern 'google,.*'. which looks like it comes from depthcharge-tools. That's not used everywhere though (amd64 and arm64 only, and of course amd64 is not affected by dtb stuff), so not cc-ing its maintainers. Checking build/Makefile, we have: $(DTBS): $(TEMP_KERNEL) … Under build/config/* we have stuff like: DTBS = $(SOME_DEST)/$(EXTRANAME)README TEMP_KERNEL = $(foreach name,$(KERNELNAME),$(TEMP)/$(name)) TEMP_DTBS = $(TEMP)/lib or in build/config/arm.cfg: arm_grub_efi: $(TEMP_DTBS) or in build/config/riscv64.cfg: riscv64_grub_efi: $(TEMP_DTBS) so this really looks like some side-effect of the dtb move. Of course it would be easier if ARM/RISC-V porters would have a look, but the problem is likely in src:debian-installer, which probably need some config-related updates. Thanks, Emanuele! Cheers, -- Cyril Brulebois ([email protected]) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmldOKMACgkQ/5FK8MKz VSCMeg/+KnSoi/wgZe1AX0O+WiGplPHmmZcE7XsH9HsfxwAqAuKHWkaZ1CEHeH+t 7G1uv6swoC3leNH+WwN3pqEURW0y9EYEKv19GOkGCCRbNV8am6oFhGeXNUAu/ohU YPghaVu5gZFj9mADSseBU9w//+sGDXGpb6IxRaylT7VomQd6lx4buhHzTNfIBj6/ 4OFdSvbmgBGxQmlSIPzP479DbFEoDh5LLiFob6GB7PZdcIvnID45HZfScdZdYQH4 J4mmvX/tDPE3c7Zb5te7hcVFMXoCXx9igX3EnsdSrAFEBk3EHoT6SQe5xPkylig0 Ls0JHjQcIXbXKIdE5W/kRiVsOwAhQiR3SiS+xBfpAq/LDEj0noDLK0AzfO4WIBqj CkvXQlFKQMhzjvemPTHABuz5b7wAG1djqwYu1F+MBBvVq9Yh0DTXlzmf4ILIPjje +UCgPlvmtX3/wPKmz5jfpWajjcaApXxVw9Ikm5GMqWkYbCSo/o1emElCWC9SCYLC co+ko+9aqtU5e6W4/lpefBwLC2kFodwCtakqjupADo0sAPVkA77xsoHd8UC8JoS2 JlGZVlWi7Iumk/UBaiR7T/2UKxEpwZv8HxsxzK/aHMf15tEyAx+ggtqQK154iu6+ Y9UwyFdVB7rN980i40pRG/XxOleGAf28g0LRL4la/EYHekabeTA= =RDwR -----END PGP SIGNATURE-----