Hi Martin, Martin Michlmayr <t...@cyrius.com> (2022-06-09): > I became aware recently that this was never fixed. Rick Thomas has > two OpenRD (Ultimate and Client) and could test the images. > > Since bullseye is the last release to support these devices (I think? > I never know what the status of armel is), I wonder if it would make > sense to add the images back to d-i in a point release. > > Basically to revert the change to build/config/armel/kirkwood/netboot.cfg > from commit e799d626f45e9c706d05003e3112d481db2870a9 > > Vagrant, do you think you could do a bullseye d-i checkout, make that > change and make the OpenRD images available for Rick to test? > (I don't have any ARM machines)
Tried that, building in bullseye_armel-dchroot on amdahl (following instructions at https://dsa.debian.org/doc/schroot/); but it fails to build since openrd bits are missing from the u-boot package? Providing u-boot binaries for dockstar ... Providing u-boot binaries for dreamplug ... Providing u-boot binaries for guruplug ... Providing u-boot binaries for sheevaplug ... Providing u-boot binaries for openrd-base ... cp: cannot stat '/usr/lib/u-boot/openrd_base/u-boot.kwb': No such file or directory make[7]: *** [config/armel/kirkwood/u-boot.cfg:8: u-boot-binaries] Error 1 and indeed: $ find /usr/lib/u-boot/ -type f|sort /usr/lib/u-boot/dockstar/u-boot.kwb /usr/lib/u-boot/dockstar/uboot.elf /usr/lib/u-boot/dreamplug/u-boot.kwb /usr/lib/u-boot/dreamplug/uboot.elf /usr/lib/u-boot/guruplug/u-boot.kwb /usr/lib/u-boot/guruplug/uboot.elf /usr/lib/u-boot/sheevaplug/u-boot.kwb /usr/lib/u-boot/sheevaplug/uboot.elf For the avoidance of doubt, that chroot has those u-boot packages: ii u-boot:armel 2021.01+dfsg-5 ii u-boot-tools 2021.01+dfsg-5 Please let me know if I can be of more assistance regarding building, backporting, etc. Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
