From: Roman Scherer <roman@burningswell.com>
To: 69174@debbugs.gnu.org
Cc: Roman Scherer <roman@burningswell.com>,
Leo Famulari <leo@famulari.name>,
Tobias Geerinckx-Rice <me@tobias.gr>, Wilko Meyer <w@wmeyer.eu>
Subject: [bug#69174] [PATCH] gnu: pipewire: Update to 1.0.3.
Date: Sun, 18 Feb 2024 18:53:30 +0100 [thread overview]
Message-ID: <c8ee6d091c94dd4ec61e804b25518e7f5ed880ea.1708278374.git.roman@burningswell.com> (raw)
* gnu/packages/linux.scm (pipewire): Update to 1.0.3.
Change-Id: I135d987bd33b4650f3fb38ca3f3a98238be106e8
---
gnu/packages/linux.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
index d798c44a8f..8af190bf25 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -9364,7 +9364,7 @@ (define-public inputattach
(define-public pipewire
(package
(name "pipewire")
- (version "1.0.0")
+ (version "1.0.3")
(source (origin
(method git-fetch)
(uri (git-reference
@@ -9373,7 +9373,7 @@ (define-public pipewire
(file-name (git-file-name name version))
(sha256
(base32
- "0a8wvsnbgqanp2vjdpkaxpny0k17hz720rd20zdi00s9xjbcrycr"))))
+ "10psfk260pqgi375d5q80yyzy2a1jabs3cgvrd0w18sdwi1knp21"))))
(build-system meson-build-system)
(arguments
(list
base-commit: 3cf199dbcf85a44fa8370e786e568fc3feb7067c
prerequisite-patch-id: 0250f6d992ee74e81797cb1266771a825226fa0b
prerequisite-patch-id: e03a4f63a64eda0c1f229e0b92d130a9beadefa5
prerequisite-patch-id: 09e6b4e8c70f5eb7996f78194c59245f38d3241b
prerequisite-patch-id: a12882ccf5bbef1edbd1110f128cd107f84a1377
prerequisite-patch-id: 2c83a46f3bcf9d3e153e2543fe9a57e5f33af286
prerequisite-patch-id: 3c1ca4618ff254748694208007768994f8f3f180
--
2.41.0
next reply other threads:[~2024-02-18 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 17:53 Roman Scherer [this message]
2024-03-01 6:21 ` bug#69174: [PATCH] gnu: pipewire: Update to 1.0.3 Hilton Chain via Guix-patches via
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c8ee6d091c94dd4ec61e804b25518e7f5ed880ea.1708278374.git.roman@burningswell.com \
--to=roman@burningswell.com \
--cc=69174@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=me@tobias.gr \
--cc=w@wmeyer.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.