From: ftrvxmtrx <ftrvxmtrx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] pipewire: update to 0.3.53
Date: Thu, 07 Jul 2022 14:47:55 +0200 [thread overview]
Message-ID: <20220707124755.B3RzUbP80VP3dGo5ULeJlemNKdrH5uKU-Icc-BspR5w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37840@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
There is an updated pull request by ftrvxmtrx against master on the void-packages repository
https://github.com/ftrvxmtrx/void-packages pipewire-0.3.53
https://github.com/void-linux/void-packages/pull/37840
pipewire: update to 0.3.53
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64, aarch64-musl)
A patch file from https://github.com/void-linux/void-packages/pull/37840.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pipewire-0.3.53-37840.patch --]
[-- Type: text/x-diff, Size: 1307 bytes --]
From 69e5f6f6d1a88de616493ecf622a5e40197b8c3d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Sigrid=20Solveig=20Hafl=C3=ADnud=C3=B3ttir?=
<sigrid@ftrv.se>
Date: Mon, 4 Jul 2022 17:25:19 +0200
Subject: [PATCH] pipewire: update to 0.3.54
---
srcpkgs/pipewire/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/pipewire/template b/srcpkgs/pipewire/template
index 92d7b65434a9..c71faf1061ac 100644
--- a/srcpkgs/pipewire/template
+++ b/srcpkgs/pipewire/template
@@ -1,6 +1,6 @@
# Template file for 'pipewire'
pkgname=pipewire
-version=0.3.52
+version=0.3.54
revision=1
_pms_version=0.4.1
build_style=meson
@@ -34,7 +34,7 @@ homepage="https://pipewire.org/"
changelog="https://gitlab.freedesktop.org/pipewire/pipewire/-/raw/master/NEWS"
distfiles="https://gitlab.freedesktop.org/pipewire/pipewire/-/archive/${version}/pipewire-${version}.tar.gz
https://gitlab.freedesktop.org/pipewire/media-session/-/archive/${_pms_version}/media-session-${_pms_version}.tar.gz"
-checksum="024ec4b2f77e6049ba3acb569250943f736a366a05f4b8fce42e09e678b43039
+checksum="11a856ac3eb70b7cbeef12407f50d240d212016b6de3bb692e462251571f050e
119c9216070b54018217552c7924f9888da270c3c4647c5e2b85ffa6b1574975"
make_dirs="/var/lib/pipewire 0755 _pipewire _pipewire"
system_accounts="_pipewire"
next prev parent reply other threads:[~2022-07-07 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 15:26 [PR PATCH] " ftrvxmtrx
2022-07-04 17:07 ` Duncaen
2022-07-04 21:53 ` ftrvxmtrx
2022-07-04 21:53 ` ftrvxmtrx
2022-07-07 12:47 ` ftrvxmtrx [this message]
2022-07-07 14:18 ` pipewire: update to 0.3.54 ftrvxmtrx
2022-07-09 21:14 ` [PR PATCH] [Merged]: " Johnnynator
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=20220707124755.B3RzUbP80VP3dGo5ULeJlemNKdrH5uKU-Icc-BspR5w@z \
--to=ftrvxmtrx@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).