Control: tag -1 + patch Hi, On Thu, 16 Oct 2025 15:17:57 +0200 Diederik de Haas <didi.debian@cknow.org> wrote: > I tried if the following patch would fix it: > > ``` > diff --git a/debian/config/misc-nonfree/defines b/debian/config/misc-nonfree/defines > index 71a7ae3..86ca756 100644 > --- a/debian/config/misc-nonfree/defines > +++ b/debian/config/misc-nonfree/defines > @@ -32,7 +32,7 @@ files: > 3com/typhoon.bin > advansys/* > amphion/vpu/* > - arm/mali/arch10.8/mali_csffw.bin > + arm/mali/* > brcm/BCM-0a5c-6410.hcd > brcm/BCM-0bb4-0306.hcd > cadence/mhdp8546.bin I tried this patch: --- a/debian/config/misc-nonfree/defines +++ b/debian/config/misc-nonfree/defines @@ -32,7 +32,7 @@ files: 3com/typhoon.bin advansys/* amphion/vpu/* - arm/mali/arch10.8/mali_csffw.bin + arm/mali/arch10.*/mali_csffw.bin brcm/BCM-0a5c-6410.hcd brcm/BCM-0bb4-0306.hcd cadence/mhdp8546.bin And with that, the resulting package (built on salsa) has: drwxr-xr-x root/root 0 2025-10-15 16:02 ./usr/lib/firmware/arm/ drwxr-xr-x root/root 0 2025-10-15 16:02 ./usr/lib/firmware/arm/mali/ drwxr-xr-x root/root 0 2025-10-15 16:02 ./usr/lib/firmware/arm/mali/arch10.10/ -rw-r--r-- root/root 282624 2025-10-15 16:02 ./usr/lib/firmware/arm/mali/arch10.10/mali_csffw.bin drwxr-xr-x root/root 0 2025-10-15 16:02 ./usr/lib/firmware/arm/mali/arch10.12/ lrwxrwxrwx root/root 0 2025-10-15 16:02 ./usr/lib/firmware/arm/mali/arch10.12/mali_csffw.bin -> ../arch10.10/mali_csffw.bin drwxr-xr-x root/root 0 2025-10-15 16:02 ./usr/lib/firmware/arm/mali/arch10.8/ lrwxrwxrwx root/root 0 2025-10-15 16:02 ./usr/lib/firmware/arm/mali/arch10.8/mali_csffw.bin -> ../arch10.10/mali_csffw.bin I also wonder whether it would make sense to add some mechanism which would check after dh_builddeb whether the created binary packages contain any broken symlinks. Does a tool to do such a thing already exist? Lintian does not warn about this (probably because the link target might come from one of the Depends) and dh_missing also does not complain that some files do not get installed. Any ideas of how to prevent this sort of bug in the long-term? Thanks! cheers, josch
Attachment:
signature.asc
Description: signature