Your message dated Wed, 4 Sep 2024 10:16:08 +0200
with message-id <b8d9a53f-50e5-41aa-bee7-3a434dd5f...@rclobus.nl>
and subject line A new version was released
has caused the Debian Bug report #1068753,
regarding live-build: Should not install raspi-firmware on x86_64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1068753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: live-build
Version: 1:20230502
Severity: important
Dear Maintainer,
Built the live image for bookworm using live build (on bookworm as well as from
unstable). The built
image incldes raspi-firmware which is not meant for x86_64. I was installing
some dkms module which
will regenerate initrd etc and that failed with below error
update-initramfs: Generating /boot/initrd.img-6.1.0-13-amd64
W: Couldn't identify type of root file system for fsck hook
live-boot: core filesystems dm-verity devices utils udev blockdev dns.
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return
code 1
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned
error exit status 1
Processing triggers for libc-bin (2.36-9+deb12u2) ...
Errors were encountered while processing:
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
The only way to fix this situation was to remove raspi-firmware in the live
image. For now I'm working
around the situation using following hook file which I use during live image
build
#!/bin/sh
set -eu
raspi_installed=$(apt-cache policy raspi-firmware | grep Installed: | awk
'{print $NF}')
if [ "$raspi_installed" != "(none)" ]; then
apt-get remove --purge -y raspi-firmware
fi
Can we avoid installing it on x86 architecture by default. If some one needs it
they can pull
it.
It was claimed to be fixed by 12.2 in this [1] but it probably only fixed
official live images
but not the live build? There is also another ticket [2] but does not give
proper details so created
a new one
Let me know if any other information is needed from my side.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035382
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065640
Thanks and Regards,
Vasudev Kamath
-- Package-specific info:
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.9-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages live-build depends on:
ii debootstrap 1.0.134
Versions of packages live-build recommends:
ii apt-utils 2.7.11
ii bzip2 1.0.8-5.1
ii cpio 2.15+dfsg-1
ii cryptsetup 2:2.7.1-1
ii file 1:5.45-2+b1
ii live-boot-doc 1:20230131
ii live-config-doc 11.0.4
ii live-manual-html [live-manual] 2:20151217.2
ii rsync 3.2.7-1+b2
ii systemd-container 255.4-1+b1
ii wget 1.24.5-1
ii xz-utils 5.6.1+really5.4.5-1
Versions of packages live-build suggests:
ii e2fsprogs 1.47.0-2+b1
pn mtd-utils <none>
ii parted 3.6-3
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:20240810
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
