Control: clone -1 -2 Control: reassign -2 installation-report Control: retitle -2 installation-report: store and report firmware information
Cyril Brulebois <k...@debian.org> (2023-01-28):
> hw-detect already has some finish-install hooks, so it would only need
> to generate something like /var/log/installer/firmware-packages from
> it, with “$package $component” on each line?
>
> And maybe “# no firmware packages” (with a leading # to signal a
> comment), so that people can easily iterate over it if they so wish?
Trying to balance informative header, appearance, and machine-readability
I'm about to implement something like this when some packages are found:
#Package Component Reason
firmware-linux-nonfree non-free-firmware modalias
firmware-realtek non-free-firmware dmesg
(I was about to use column -t, but that's bsdextrautils, so I'm using a
format string with printf, allowing 30-character worth of package name.)
and otherwise:
# No firmware/microcode packages deployed by the installer
which means people can grep -v ^# to get to the actual data (if any) and
do stuff with it, while humans have a decent-ish table.
I'm also adding the firmware summary file to the installation report via
the bug script.
I'll test this shortly with patched hw-detect and installation-report on
a netinst ISO, on baremetal then report actual results, instead of the
mockup above.
> I don't think that's a blocker for the next d-i release, that might be
> considered a blocker for Bookworm though; debian-release@ in Cc can
> comment and raise severity if that's desired.
Cc dropped since we're implementing this right now.
Cheers,
--
Cyril Brulebois (k...@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
