Bug#786882: debian-installer: FTBFS on arm64: can't find dtbs
Package: debian-installer
Severity: serious
Hi,
The daily build FTBFS this way on arm64:
| # These files are used to build special kernel images for some
| # subarchitectures. Move them out of the way.
| if [ -d ./tmp/device-tree/tree/usr/lib/kernel-image-4.0.0-1-arm64 ]; then mv ./tmp/device-tree/tree/usr/lib/kernel-image-4.0.0-1-arm64 ./tmp/device-tree/lib; fi; if [ -d ./tmp/device-tree/tree/usr/lib/linux-image-4.0.0-1-arm64 ]; then mv ./tmp/device-tree/tree/usr/lib/linux-image-4.0.0-1-arm64 ./tmp/device-tree/lib; fi;
| # Move the kernel image out of the way.
| mv -f ./tmp/device-tree/tree/boot/vmlinuz ./tmp/device-tree/vmlinuz;
| test -e ./tmp/device-tree/tree/boot/zfs || rmdir ./tmp/device-tree/tree/boot/
| # Create an lsb release file.
| if [ ! -e ./tmp/device-tree/tree/etc/lsb-release ]; then \
| set -e; \
| mkdir -p ./tmp/device-tree/tree/etc; \
| echo 'DISTRIB_ID=Debian' > ./tmp/device-tree/tree/etc/lsb-release; \
| echo 'DISTRIB_DESCRIPTION="Debian GNU/Linux installer"' >> ./tmp/device-tree/tree/etc/lsb-release; \
| echo 'DISTRIB_RELEASE="9 (stretch) - installer build 20150526-09:48"' >> ./tmp/device-tree/tree/etc/lsb-release; \
| echo 'X_INSTALLATION_MEDIUM=device-tree' >> ./tmp/device-tree/tree/etc/lsb-release; \
| fi
| mkdir -p ./dest/device-tree/
| set -ex ; for dtb in ./tmp/device-tree/lib/*.dtb ; do \
| tgt=./dest/device-tree/$(basename $dtb); \
| cp $dtb $tgt ; \
| update-manifest $tgt "Device Tree Blob: $(basename $dtb)";\
| done
| + basename ./tmp/device-tree/lib/*.dtb
| + tgt=./dest/device-tree/*.dtb
| + cp ./tmp/device-tree/lib/*.dtb ./dest/device-tree/*.dtb
| cp: cannot stat './tmp/device-tree/lib/*.dtb': No such file or directory
| Makefile:772: recipe for target 'dest/device-tree/README' failed
| make[2]: *** [dest/device-tree/README] Error 1
| Makefile:284: recipe for target '_build' failed
| make[1]: *** [_build] Error 2
| Makefile:278: recipe for target 'build_device-tree' failed
| make: *** [build_device-tree] Error 2
There seems to be some dtb dance here, and I think the src:linux's
having relocated the dtbs under subdirectories is responsible for the
FTBFS. Comparing some recent kernels:
| kibi@wodi:/tmp/linux-kernel$ debdiff binary-kernel-image-3.16.0-4-arm64-di/kernel-image-3.16.0-4-arm64-di_3.16.7-ckt9-2_arm64.udeb binary-kernel-image-4.0.0-1-arm64-di/kernel-image-4.0.0-1-arm64-di_4.0.2-1_arm64.udeb
| [The following lists of changes regard files as different if they have
| different names, permissions or owners.]
|
| Files in second .deb but not in first
| -------------------------------------
| -rw-r--r-- root/root /lib/modules/4.0.0-1-arm64/modules.builtin
| -rw-r--r-- root/root /lib/modules/4.0.0-1-arm64/modules.order
| -rw-r--r-- root/root /usr/lib/linux-image-4.0.0-1-arm64/apm/apm-mustang.dtb
| -rw-r--r-- root/root /usr/lib/linux-image-4.0.0-1-arm64/arm/foundation-v8.dtb
| -rw-r--r-- root/root /usr/lib/linux-image-4.0.0-1-arm64/arm/juno.dtb
| -rw-r--r-- root/root /usr/lib/linux-image-4.0.0-1-arm64/arm/rtsm_ve-aemv8a.dtb
|
| Files in first .deb but not in second
| -------------------------------------
| -rw-r--r-- root/root /lib/modules/3.16.0-4-arm64/modules.builtin
| -rw-r--r-- root/root /lib/modules/3.16.0-4-arm64/modules.order
| -rw-r--r-- root/root /usr/lib/linux-image-3.16.0-4-arm64/apm-mustang.dtb
| -rw-r--r-- root/root /usr/lib/linux-image-3.16.0-4-arm64/foundation-v8.dtb
| -rw-r--r-- root/root /usr/lib/linux-image-3.16.0-4-arm64/rtsm_ve-aemv8a.dtb
→ Besides the ABI bump, one can see apm/ and arm/ being introduced here.
src:debian-installer likely needs to learn how to handle this.
(Letting debian-arm@ know through x-d-cc.)
Mraw,
KiBi.
Reply to: