Dear Maintainer, (self-reporting, I intent to do the upload myself) Please consider backporting version 1.6.9-2 which has reached testing. The current version in trixie-backports (1.4.2-1) is quite out of date and providing the latest version would also have the benefit of fixing one minor CVE. Thanks, Agathe.
Backport 1.6.9-2~bpo13+1 considered ready on my side, the git work currently lives in my fork on salsa as I do not have the rights to push to the upstream salsa repo for debian/trixie-backport branch. Info: * tested on a local system running trixie, audio playback is fine; * salsa-ci run is OK: https://salsa.debian.org/gagath/pipewire/-/pipelines/1178890 Will upload shortly. Attached pipewire_1.6.9-2_bpo13_1.debdiff for reference against testing.
Backport 1.6.9-2~bpo13+1 considered ready on my side, the git work currently lives in my fork on salsa as I do not have the rights to push to the upstream salsa repo for debian/trixie-backport branch. Info: * tested on a local system running trixie, audio playback is fine; * salsa-ci run is OK: https://salsa.debian.org/gagath/pipewire/-/pipelines/1178890 Will upload shortly. Attached pipewire_1.6.9-2_bpo13_1.debdiff for reference against testing.
Uploaded, proposed PR to upstream repo on salsa here: https://salsa.debian.org/utopia-team/pipewire/-/merge_requests/38
Accepted pipewire 1.6.9-2~bpo13+1 (source) into stable-backports https://tracker.debian.org/news/1804350/accepted-pipewire-169-2bpo131-source-into-stable-backports/
Hello,
I don't know what happened but the i386 flavor of this backports seems
broken (not published).
armel, i386 and riscv64 are missing (see: https://packages.debian.org/trixie-backports/libspa-0.2-modules)
Unsatisfied dependencies:
libspa-0.2-modules : Breaks: libspa-0.2-modules:i386 (!= 1.6.9-2~bpo13+1) but 1.4.9-1~bpo13+2 is to be installed
libspa-0.2-modules:i386 : Breaks: libspa-0.2-modules (!= 1.4.9-1~bpo13+2) but 1.6.9-2~bpo13+1 is to be installed
Error: Unable to correct problems, you have held broken packages.
Error: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:
1. libspa-0.2-modules:i386=1.4.9-1~bpo13+2 is selected for install because:
1. libspa-0.2-modules:i386 is selected for install
2. libspa-0.2-modules:i386 is available in versions 1.4.9-1~bpo13+2, 1.4.2-1
[selected libspa-0.2-modules:i386]
For context, additional choices that could not be installed:
* In libspa-0.2-modules:i386 is available in versions 1.4.9-1~bpo13+2, 1.4.2-1:
- libspa-0.2-modules:i386=1.4.2-1 is not selected for install
2. libspa-0.2-modules:i386=1.4.9-1~bpo13+2 is not selected for install because:
1. libspa-0.2-modules:amd64=1.6.9-2~bpo13+1 is selected as an upgrade
2. libspa-0.2-modules:amd64=1.6.9-2~bpo13+1 Breaks libspa-0.2-modules:i386 (!= 1.6.9-2~bpo13+1)
[selected libspa-0.2-modules:amd64=1.6.9-2~bpo13+1]
Hi, While riscv64 is still in a "Needs-Build" state, armel and i386 are stuck because of a missing build dependency: onnxruntime https://buildd.debian.org/status/package.php?p=pipewire&suite=trixie-backports I would totally disable the onnxruntime plugin for trixie-backports. It's not really useful and it pulls many new dependencies, see #1130264. Best regards, Dylan
You find me confused. Why does the i386 flavor gets stucks while amd64 does not? onnxruntime is not being backported, is it? Far be it from me to add to your workload; therefore, if it is indeed the easier path, I would encourage you to do so.