Control: tags -1 + upstream Control: forwarded -1 https://github.com/go-debos/debos/pull/390
Hello, On Tue, Jan 03, 2023 at 11:34:27AM +0100, Andreas Henriksson wrote: > Package: debos > Version: 1.1.1-2 > Severity: important > > Dear Maintainer, > > Using debos to build a recipe that uses bookworm or newer suite > gives a mysterious apt error that suggest running apt --fix-broken > install. > > This is a symptom of the workaround that was applied for > https://github.com/go-debos/debos/issues/361 > "New debootstrap is unable to bootstrap pre-bookworm debian derivatives" [...] For the record, this first problem was handled upstream at https://github.com/go-debos/debos/pull/390 [...] > 2023/01/03 01:19:51 apt | Setting up linux-image-6.0.0-6-arm64 (6.0.12-1) ... > 2023/01/03 01:19:55 apt | I: /vmlinuz.old is now a symlink to > boot/vmlinuz-6.0.0-6-arm64 > 2023/01/03 01:19:55 apt | I: /initrd.img.old is now a symlink to > boot/initrd.img-6.0.0-6-arm64 > 2023/01/03 01:19:55 apt | I: /vmlinuz is now a symlink to > boot/vmlinuz-6.0.0-6-arm64 > 2023/01/03 01:19:55 apt | I: /initrd.img is now a symlink to > boot/initrd.img-6.0.0-6-arm64 > 2023/01/03 01:19:56 apt | /etc/kernel/postinst.d/initramfs-tools: > 2023/01/03 01:19:56 apt | update-initramfs: Generating > /boot/initrd.img-6.0.0-6-arm64 > 2023/01/03 01:19:56 apt | W: No zstd in /usr/bin:/sbin:/bin, using gzip > 2023/01/03 01:30:32 apt | Container root terminated by signal KILL. > Powering off. > open /tmp/fakemachine-194296958/result: no such file or directory This second problem turned out to be because the default 2Gb memory setting for fakemachine/qemu is apparently no longer enough to run update-initramfs against the bookworm arm64 kernel modules in linux-image-arm64. Using `debos --memory=4Gb ...` resolved this issue for me. Maybe it would be useful to consider bumping the default memory setting? Regards, Andreas Henriksson