Your message dated Sat, 03 Jun 2023 00:23:08 +0200
with message-id <8225857.T7Z3S40VBb@bagend>
and subject line Close bugs I'm no longer interested in
has caused the Debian Bug report #1023741,
regarding raspi-firmware: Please transfer brcmfmac43456-sdio.* files to
firmware-brcm80211 package
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1023741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: raspi-firmware
Version: 1.20220830+ds-1
Severity: normal
X-Debbugs-Cc: 999...@bugs.debian.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
In https://bugs.debian.org/999485#10 you (Gunnar Wolf) wrote:
============================================
Please note I'm currenlty shipping the required files in
raspi-firmware -- I believe their right place is in
firmware-brcm80211, so please just ping me (or better, raise a bug on
raspi-firmware) whent they are added to this package.
============================================
I completely agree that firmware-brcm80211 is the right place and
raspi-firmware is the wrong place as this is about firmware for wifi
devices which are f.e. also used on Pine64 devices.
It doesn't make sense to install the raspi-firmware on those non-RPi
devices and AFAIK the package also makes assumptions about being run
*on* a RPi (with a /boot/firmware dir?), so it may even fail
installation on non-RPi devices.
So hereby the request to do and coordinate the move of those firmware
files to the firmware-brcm80211 package, which likely will need to be
coordinated with a Breaks/Replace construct.
It would be great if it could be done ASAP, but at least before the
Bookworm release.
TIA,
Diederik
- -- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages raspi-firmware depends on:
ii dosfstools 4.2-1
ii dpkg 1.21.9+b1
raspi-firmware recommends no packages.
Versions of packages raspi-firmware suggests:
ii bluez-firmware 1.2-7
pn firmware-brcm80211 <none>
ii firmware-misc-nonfree 20221012-1
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCY2uYvAAKCRDXblvOeH7b
brzrAP4wMDJZQ7uBPrr5BzA5kMCp9Rta/5/ENNQUc5zfUHCITQD+IT4k+rZ9L6rC
D/7fSkwV3kEO4JbNwbAHOBuC9Sya6gA=
=p/QT
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
