Your message dated Tue, 20 Feb 2024 13:57:43 +0100
with message-id <15880867.LhoEdJJz2m@bagend>
and subject line Re: firmware-carl9170: Should nonfree-firmware exclude
'carl9170fw' dir from linux-firmware?
has caused the Debian Bug report #1063577,
regarding firmware-carl9170: Should nonfree-firmware exclude 'carl9170fw' dir
from linux-firmware?
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 [email protected]
immediately.)
--
1063577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063577
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: firmware-carl9170
Version: 1.9.9-399-gcd480b9-1
Severity: minor
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
has a directory ``carl9170fw`` which is also the source name of this
package. When I check this package Homepage I see the following:
```
Firmware binary
The firmware can be obtained from firmware tree.
```
And 'firmware tree' is a link to firmware-nonfree's repo (via a
redirect). Looking through this package git repo, I found this URL:
https://github.com/chunkeey/carl9170fw/
And a casual comparison with the ``carl9170fw`` dir in linux-firmware
repo shows a LOT of similarities. But it's not the same.
It appears that this package's upstream is a fork of linux-firmware?
In any case, I'm confused about the relation between the ``carl9170fw``
dir in linux-firmware and this package.
Can you tell me if the ``carl9170fw`` dir should be excluded in
firmware-nonfree, just like ``ath9k_htc`` is excluded as it's packaged
in ``open-ath9k-htc-firmware``?
- -- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.6.13-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:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZcZVTgAKCRDXblvOeH7b
bkmaAP99nTma9WFJeFzfFEGpZfTyIf0KmTNxJBX2XkEq0QM7cAD9G9eRc+UG31Hg
J9CXEtwGbWnEbEfvUug3waKiwrSpWw4=
=1zzV
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On 09 Feb 2024 17:39:50 +0100 Diederik de Haas <[email protected]> wrote:
> Package: firmware-carl9170
> Version: 1.9.9-399-gcd480b9-1
> Severity: minor
>
> Can you tell me if the ``carl9170fw`` dir should be excluded in
> firmware-nonfree, just like ``ath9k_htc`` is excluded as it's packaged
> in ``open-ath9k-htc-firmware``?
I'm going to exclude that dir as ``carl9170-1.fw`` is part of firmware-free and
``carl9170fw`` installs its output (according to ``autogen.sh``) at
``../carl9170-$CONFIG_CARL9170FW_RELEASE_VERSION.fw``
CARL9170FW_RELEASE_VERSION is a Kconfig option with a default value of 1, so in
the default case that means ``carl9170-1.fw``.
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
