Control: severity -1 serious Control: forcemerge -1 1118261 Quoting Diederik de Haas (2025-10-18 11:12:05) > Thanks for that :-) > Because of that I realized my glob pattern was wrong. So I found which > pattern I should use and with that, all Arm Mali firmware was packaged. > > I've attached the patch and submitted it as MR here: > https://salsa.debian.org/kernel-team/firmware-nonfree/-/merge_requests/132 Perfect, thank you! I can now also confirm that the boot failures I reported in #1118261 are due to the mali firmware which was not getting shipped. I am thus raising the severity of this bug to RC and merge the other one into this one. Until this fix gets uploaded we are shipping a hotfix in our own repositories: https://source.mnt.re/reform/reform-debian-packages/-/commit/ 0947565403d2acd607eade57692bf4916a493c2b Do you know of a mechanism which would allow to find broken symlinks in the firmware-nonfree packages automatically in the future and abort the build if found? Lintian does not show broken symlinks because it cannot know whether the files maybe come from another package. Should the script generating the install files gain this feature or maybe a script can be added that is run after dh_installdeb which analyzes the generated binary packages? This problem was very frustrating for users on Debian unstable on the affected platforms as without being able to login, recovery is hard for users who are not very tech-savvy. And it also took me 3 hours before I found out that it was the changes firmware-misc-nonfree which resulted in gdm not showing up. I had suspected some changes in gnome, gtk, gsettings or whatnot but not this package. :D Thanks! cheers, josch
Attachment:
signature.asc
Description: signature