home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   linux.debian.kernel      Debian kernel discussions      2,884 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 1,060 of 2,884   
   Johannes Schauer Marin Rodrigues to All   
   Bug#1118195: firmware-misc-nonfree: no l   
   18 Oct 25 14:10:01   
   
   XPost: linux.debian.bugs.dist   
   From: josch@debian.org   
      
   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   
   --==============C00657442243096775=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+EFAmjzgMQACgkQ8sulx4+9   
   g+HKsQ//YbqQE85SjYGnqRflcDROPEuSYteh5Q7YMYWwrd9y0qGtnSvO8vStfCrx   
   cjjwlvVIbkv+bu8Jkv0JjzqsydWn8E5yRBX/ryG6dfzGvy5hOM8JN+Q75AJ1SNZj   
   4uBHsvc7txgGMdu64632AVNBVC6Sn7emnI6uEPpxqulQmhg+MJ9szbnL1rjh4yDG   
   DSzzljNZJy6Y71kre6QObKBo015GdozbqMkvySCg+QhCDVqmnrIFblQUHPplOOUD   
   C7jrdOJB2C+5YxTwg1hhd5ovApXuQ/BEchVWO8gqzXRd64wqaaSyacaRzBa+34Wh   
   J0HJc+l5PwijXCok6ueBYuF/KYvFwFciPizb5WfiuTk9s6u1MaaX3/tc57Gg4pYM   
   J91FOzuAXSx02aAhlr5i7wMptrBjHr8MwuzGC0xvBNXSvkf6kQmqSTOkNJCmIakW   
   UkzqpvhaxftLADVoxptEuI5tzaAzVZY8gqPceK6spZ9fcbg8X3CXsfhoLt0R3mWB   
   wLczE56H1IHVJ+9HP3htgT+XTgBzC3nKBbG3XbfYGz1WZXIImxO5rScGD0vvRknu   
   SijwPILZFqCspg7zXnnNFLgq8fiz0ohuqwnumzDlcG2hFauP/YXTD6ddwFrdikf+   
   Mg3bE2CpN1O4Fw8htbQBWNWIdfosCIa/jaFMceE68QIlTUw1pDM=   
   =Faeq   
   -----END PGP SIGNATURE-----   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca