From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Packages up for grabs: sys-firmware/broadcom-bt-firmware
Date: Thu, 23 Mar 2023 09:10:32 +0100 [thread overview]
Message-ID: <09731d4c-2e7d-ea18-9e2b-c4b728926173@gentoo.org> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 507 bytes --]
I've dropped
sys-firmware/broadcom-bt-firmware
to maintainer needed, as I do not longer have compatible hardware.
From a security perspective, the firmware in this package could be
considered dubious. Personally, I would recommend users to by newer
bluetooth hardware [1].
The package has one open bug, requesting USE=savedconfig support:
https://bugs.gentoo.org/buglist.cgi?quicksearch=broadcom-bt-firmware
- Flow
1: I now have a TP-Link UB500, and I am quite happy with it.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 17273 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next reply other threads:[~2023-03-23 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 8:10 Florian Schmaus [this message]
2023-03-24 8:39 ` [gentoo-dev] Packages up for grabs: sys-firmware/broadcom-bt-firmware Azamat Hackimov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09731d4c-2e7d-ea18-9e2b-c4b728926173@gentoo.org \
--to=flow@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox