Your message dated Sun, 30 Jun 2024 22:21:09 +0200
with message-id <74779691.Lv8qgiQ7IQ@bagend>
and subject line Re: firmware-nonfree: Important changes coming up with
upstream version 20230919
has caused the Debian Bug report #1061321,
regarding firmware-nonfree: Important changes coming up with upstream version
20230919
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.)
--
1061321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firmware-nonfree
Version: 20230625-2
Severity: important
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I'm currently working on an update for upstream version 20230919, based
upon MR86 (Release 20230804) [1], which itself is based upon MR85
(Update to 20230625) [2] and I'm running into some major issues:
1) Salsa's CI now always fails as the (archive) size is now too big for
it to handle it.
2) Upstream introduced a new keyword RawFile to 'list files that must
not be compressed'. I'm guessing one or more script files need to be
updated for it?
3) Upstream commit a0142c57045701b7557c3060af5c4246c420e4d8 titled
"ath10k/WCN3990: move wlanmdsp to qcom/sdm845" would mean moving
entries from ``debian/config/atheros`` to ``debian/config/qcom-soc``
and adding a 'recommends' field to ``atheros``'s ``defines`` file.
Which means that qcom-soc recommends atheros and atheros recommends
qcom-soc. Technically doable, but it raises the question whether this
separation still makes sense.
[1] https://salsa.debian.org/kernel-team/firmware-nonfree/-/merge_requests/86
[2] https://salsa.debian.org/kernel-team/firmware-nonfree/-/merge_requests/85
- -- 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.11-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/XblvOeH7bbgUCZa5+3wAKCRDXblvOeH7b
br9tAQCbvKeLqadcQE0fBigvlCW66k55+X76p0gd+R45PUc6ngEAqjJuUSHra5Jd
Liswzmc7gOnYa8DEg4Y2ZXzl8xep0wc=
=33X+
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Note: I'm doing this from memory, so some details may be off a bit.
On Sunday, 30 June 2024 21:14:12 CEST Ben Hutchings wrote:
> On Mon, 22 Jan 2024 15:42:48 +0100 Diederik de Haas
>
> <didi.deb...@cknow.org> wrote:
> > I'm currently working on an update for upstream version 20230919,
> > ...
> > and I'm running into some major issues:
> >
> > 1) Salsa's CI now always fails as the (archive) size is now too big
> > for it to handle it.
>
> I've addressed this for now by excluding:
>
> - Many firmware versions that are no longer referenced
> - All atomisp2 firmware
> - All mlxsw firmware
> - Some new Qualcomm SoC firmware
By excluding non-distributable firmware I was able to push it back to 202311NN
but then I hit nvidia including a RISC-V OS in their firmware (I'm sticking to
my speculation here)
> > 3) Upstream commit a0142c57045701b7557c3060af5c4246c420e4d8 titled
> > "ath10k/WCN3990: move wlanmdsp to qcom/sdm845" would mean moving
> > entries from ``debian/config/atheros`` to ``debian/config/qcom-soc``
> > and adding a 'recommends' field to ``atheros``'s ``defines`` file.
> > Which means that qcom-soc recommends atheros and atheros
> > recommends qcom-soc. Technically doable, but it raises the question
> > whether this separation still makes sense.
>
> I think only the qcom-soc -> atheros recommendation is needed.
Yeah IIRC that's what I did too.
I don't know the details anymore, but I recently ran into an interesting
problem though as the 'physical' firmware file was put in the atheros packages
instead of a link to the place of the qcom-soc package. Could be a PEBKAC
issue, but you might verify whether it's doing the right thing.
And (IIRC) it also invokes commands via ``sh -c "<command-you-want-to-run"``
and apparently there's a size limit to that. As the cirrus has a huge number
of (small) firmware files, I'd hit that limit in 202402 or 202403.
I was thinking of working around it by skipping a release as after the
problematic release, a large number of cirrus firmware files were deleted.
But if you ran into that problem, I'm sure you'd find a proper solution.
Closing the bug as I'm not interested in it anymore.
Good luck
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
