aboutsummaryrefslogtreecommitdiffhomepage
path: root/internal/rosa/package/pipewire/fcc8d79b6b5e1bc21ff7ea6353f3cd230e9243ee.patch
diff options
context:
space:
mode:
authorOphestra <cat@gensokyo.uk>2026-10-25 06:46:26 +0900
committerOphestra <cat@gensokyo.uk>2026-10-25 06:46:26 +0900
commitcd222556e67004b37544cf5f2a25c5e9518201c1 (patch)
tree60650faccc19c2a893066baeff073c52f83b10c5 /internal/rosa/package/pipewire/fcc8d79b6b5e1bc21ff7ea6353f3cd230e9243ee.patch
parent408c2149b3ff6858ef164e98359184ef28079fad (diff)
internal/rosa: update packages
The elfutils fix has entered a release, the backport patch has been removed. The libconfig patch has been updated to remove newly added broken glibc-dependent tests. Kernel headers remain unchanged. Kernel configuration was updated via the new cross-compilation infrastructure. The toolchain was updated, causing a large amount of rebuilds. QEMU riscv64 cross compilation still crashes clang. PipeWire is updated, however WirePlumber remains vulnerable. The PipeWire maintainers are not treating this vulnerability as a vulnerability, and an upstream release is not coming. This change backports the fix for now. The included patch is slopped by its author, but there is nothing I can do to change that fact. Signed-off-by: Ophestra <cat@gensokyo.uk>
Diffstat (limited to 'internal/rosa/package/pipewire/fcc8d79b6b5e1bc21ff7ea6353f3cd230e9243ee.patch')
-rw-r--r--internal/rosa/package/pipewire/fcc8d79b6b5e1bc21ff7ea6353f3cd230e9243ee.patch40
1 files changed, 40 insertions, 0 deletions
diff --git a/internal/rosa/package/pipewire/fcc8d79b6b5e1bc21ff7ea6353f3cd230e9243ee.patch b/internal/rosa/package/pipewire/fcc8d79b6b5e1bc21ff7ea6353f3cd230e9243ee.patch
new file mode 100644
index 00000000..c5318f4f
--- /dev/null
+++ b/internal/rosa/package/pipewire/fcc8d79b6b5e1bc21ff7ea6353f3cd230e9243ee.patch
@@ -0,0 +1,40 @@
+From fcc8d79b6b5e1bc21ff7ea6353f3cd230e9243ee Mon Sep 17 00:00:00 2001
+From: Julian Bouzas <julian.bouzas@collabora.com>
+Date: Fri, 16 Oct 2026 14:44:36 -0400
+Subject: [PATCH] m-lua-scripting: fix the values of the Perm constants
+
+Lua does not support octal literals, so the permission values were
+parsed as decimal numbers and did not match the PipeWire ones. This
+gave restricted and flatpak clients write and link permissions. Use
+hexadecimal values instead.
+
+Fixes: #1044
+Assisted-by: Claude:claude-opus-5-5
+---
+ modules/module-lua-scripting/api/api.lua | 10 +++++-----
+ 1 file changed, 5 insertions(+), 5 deletions(-)
+
+diff --git a/modules/module-lua-scripting/api/api.lua b/modules/module-lua-scripting/api/api.lua
+index aafa49d98..0ca8c4155 100644
+--- a/modules/module-lua-scripting/api/api.lua
++++ b/modules/module-lua-scripting/api/api.lua
+@@ -184,11 +184,11 @@ local Feature = {
+ },
+ }
+
+-PERM_R_VAL = 0400
+-PERM_W_VAL = 0200
+-PERM_X_VAL = 0100
+-PERM_M_VAL = 0010
+-PERM_L_VAL = 0020
++PERM_R_VAL = 0x100
++PERM_W_VAL = 0x080
++PERM_X_VAL = 0x040
++PERM_M_VAL = 0x008
++PERM_L_VAL = 0x010
+
+ local Perm = {
+ NONE = 0,
+--
+GitLab
+