XPost: linux.debian.bugs.dist   
   From: josch@debian.org   
      
   Control: tag -1 + patch   
      
   Hi,   
      
   On Thu, 16 Oct 2025 15:17:57 +0200 Diederik de Haas    
   wrote:   
   > I tried if the following patch would fix it:   
   >    
   > ```   
   > diff --git a/debian/config/misc-nonfree/defines b/debian/confi   
   /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/firmwa   
   e/arm/mali/arch10.10/   
   -rw-r--r-- root/root 282624 2025-10-15 16:02 ./usr/lib/firmwa   
   e/arm/mali/arch10.10/mali_csffw.bin   
   drwxr-xr-x root/root 0 2025-10-15 16:02 ./usr/lib/firmwa   
   e/arm/mali/arch10.12/   
   lrwxrwxrwx root/root 0 2025-10-15 16:02 ./usr/lib/firmwa   
   e/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/firmwa   
   e/arm/mali/arch10.8/   
   lrwxrwxrwx root/root 0 2025-10-15 16:02 ./usr/lib/firmwa   
   e/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   
   --==============Q69829973179211040=MIME-Version: 1.0   
   Content-Transfer-Encoding: 7bit   
   Content-Description: signature   
   Content-Type: application/pgp-signature; name="signature.asc"; c   
   arset="us-ascii"   
      
   -----BEGIN PGP SIGNATURE-----   
      
   iQIzBAABCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmjysLUACgkQ8sulx4+9   
   g+HFyQ//Xto+yAqJX5y4BfFjKfJpgJCsKvLKDMRLvsXbAp1VPijB44qIPnirGUUP   
   Ep2HeHShJ6JosHV1lZdeWNDIeBzqTgJAKxp9BHOuO4G+WcpmjLc0dOVgD0lnbb0w   
   YRIGR9JanM/4R6JPHFlv5zqNXlbIHJiwwJFTrQMyz/QCurbzu4H8Ut5350hLJRiz   
   j1KO6AKIF9P/cfHXLRUZLulgOGk4XU9cTzPu7/ZORLGHs0RyPbGDS4mjWVyLiWyR   
   dmRqqA1o1+exRWuPpuPF6ORjp9lA9LKV5+YYAt3i6I8pJykZr70UjuLsdrCtRk6L   
   DOC5itgM/tuLQdyrv+SKCVtOX+H7M44AejawR0TJ5l2fSoOTUJP9PoIiBv1rLgS7   
   RHgMtn0eBG483FvJg/HpkuFN/RwGH0Su/uBY5ahHnchD4fii5nXAzqdABJ4F0Sfv   
   RtMjirN4kDhE3T3AW7eCpE1voiCvvSQOUzGS4q7E563EN2ix26GWF3yX0GKDdnGH   
   GT3wVSOdh4HY3XsmFm7pO31U/PtCRpibzOTCkhG6jty2S4mESDqYsTF1netD8Am/   
   SQN8fdlFW9u6biph8La/+qHGVlGfQCMIYD4Vxmu0JhpHDWfxjVE6ctelWNAnE7x8   
   AdXRgwaB2ioP2RZIQ69qSohWddwHFUP+32IyvG54ZxzrD5HzDl0=   
   =KMCP   
   -----END PGP SIGNATURE-----   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|