Script 'mail_helper' called by obssrc Hello community, here is the log from the commit of package pipewire for openSUSE:Factory checked in at 2025-12-04 11:22:01 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/pipewire (Old) and /work/SRC/openSUSE:Factory/.pipewire.new.1939 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "pipewire" Thu Dec 4 11:22:01 2025 rev:145 rq:1320942 version:1.5.84 Changes: -------- --- /work/SRC/openSUSE:Factory/pipewire/pipewire.changes 2025-12-01 11:11:49.806722004 +0100 +++ /work/SRC/openSUSE:Factory/.pipewire.new.1939/pipewire.changes 2025-12-04 11:27:04.739022433 +0100 @@ -1,0 +2,6 @@ +Tue Dec 2 11:24:42 UTC 2025 - pallas wept <[email protected]> + +- Add patch from upstream to fix linking in older clients: + * remove-mappable.patch + +------------------------------------------------------------------- New: ---- remove-mappable.patch ----------(New B)---------- New:- Add patch from upstream to fix linking in older clients: * remove-mappable.patch ----------(New E)---------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ pipewire.spec ++++++ --- /var/tmp/diff_new_pack.OTboFI/_old 2025-12-04 11:27:05.495054425 +0100 +++ /var/tmp/diff_new_pack.OTboFI/_new 2025-12-04 11:27:05.499054594 +0100 @@ -79,6 +79,8 @@ Source99: baselibs.conf # PATCH-FIX-OPENSUSE reduce-meson-dependency.patch Patch0: reduce-meson-dependency.patch +# PATCH-FIX-UPSTREAM remove-mappable.patch -- based on commit 0d7cb9b39f5b23610ecee75fb3080f6b3dfa26c7 +Patch1: remove-mappable.patch BuildRequires: docutils %if 0%{suse_version} > 1500 ++++++ remove-mappable.patch ++++++ >From 0d7cb9b39f5b23610ecee75fb3080f6b3dfa26c7 Mon Sep 17 00:00:00 2001 From: Wim Taymans <[email protected]> Date: Tue, 2 Dec 2025 12:03:35 +0100 Subject: [PATCH] client-node: remove the MAPPABLE flag for MemPtr data af3ad7bf9f861d6b3ca0446d90e47e526bc6f807 set the fd and MAPPABLE flag on buffer data when it was allocated inline in shared mem, even for MemPtr data. In the client-node however we don't pass along this fd and so we also should not pass the MAPPABLE flag for MemPtr data. This fixes an issue in older clients that blindly try to map the fd when the MAPPABLE flag is set, even when there is no fd (and there is already a data pointer). Fixes #5003 --- src/modules/module-client-node/client-node.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/modules/module-client-node/client-node.c b/src/modules/module-client-node/client-node.c index a17dc87ceb..0253591cfd 100644 --- a/src/modules/module-client-node/client-node.c +++ b/src/modules/module-client-node/client-node.c @@ -894,6 +894,7 @@ do_port_use_buffers(struct impl *impl, case SPA_DATA_MemPtr: spa_log_debug(impl->log, "mem %d %zd", j, SPA_PTRDIFF(d->data, baseptr)); b->datas[j].data = SPA_INT_TO_PTR(SPA_PTRDIFF(d->data, baseptr)); + SPA_FLAG_CLEAR(b->datas[j].flags, SPA_DATA_FLAG_MAPPABLE); break; default: b->datas[j].type = SPA_ID_INVALID; -- GitLab
