control: tags -1 + confirmed patch I disagree that this is a policy violation; the cause of error is clearly reported. Not sure how the script could be more resilient when a remote resource has disappeared: > Setting up firmware-b43-installer (1:019-13) ... > No chroot environment found. Starting normal installation > No known supported Broadcom 802.11 chips found. > No supported device found. > But firmware is installed unconditionally > Trying to install latest firmware 6.30.163.46 . > --2025-07-10 07:27:07-- https://www.lwfinger.com/b43-firmware/broadcom-wl-6.30.163.46.tar.bz2 > Resolving www.lwfinger.com (www.lwfinger.com)... 173.254.30.178 > Connecting to www.lwfinger.com (www.lwfinger.com)|173.254.30.178|:443... connected. > HTTP request sent, awaiting response... 302 Found > Location: https://www.lwfinger.com/cgi-sys/suspendedpage.cgi [following] > --2025-07-10 07:27:08-- https://www.lwfinger.com/cgi-sys/suspendedpage.cgi > Reusing existing connection to www.lwfinger.com:443. > HTTP request sent, awaiting response... 200 OK > Length: unspecified [text/html] > Saving to: ‘broadcom-wl-6.30.163.46.tar.bz2’ > > broadcom-wl-6.30.163.46.tar.bz2 [ <=> ] 891 --.-KB/s in 0s > > 2025-07-10 07:27:08 (32.3 MB/s) - ‘broadcom-wl-6.30.163.46.tar.bz2’ saved [891] > > broadcom-wl-6.30.163.46.tar.bz2: FAILED > sha512sum: WARNING: 1 computed checksum did NOT match > /var/lib/dpkg/info/firmware-b43-installer.postinst: Downloaded firmware did not match known SHA512 checksum, aborting. > dpkg: error processing package firmware-b43-installer (--configure): > installed firmware-b43-installer package post-installation script subprocess returned error exit status 1 I did find a mirror of the files on GitHub at https://github.com/minios-linux/b43-firmware/releases with matching SHA512 sums. I think an easy fix would be to point the install script to GitHub, which is probably more reliable long-term. Mathias
Attachment:
signature.asc
Description: This is a digitally signed message part