From: ftrvxmtrx <ftrvxmtrx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pipewire: update to 0.3.51
Date: Thu, 28 Apr 2022 18:14:23 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36899@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
There is a new pull request by ftrvxmtrx against master on the void-packages repository
https://github.com/ftrvxmtrx/void-packages pipewire-0.3.51
https://github.com/void-linux/void-packages/pull/36899
pipewire: update to 0.3.51
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (aarch64-musl)
- I built this PR locally for these architectures:
- x86_64
A patch file from https://github.com/void-linux/void-packages/pull/36899.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pipewire-0.3.51-36899.patch --]
[-- Type: text/x-diff, Size: 1313 bytes --]
From 3fcbbcfccdf5cc4b724f62a69058c3a0f7220601 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Sigrid=20Solveig=20Hafl=C3=ADnud=C3=B3ttir?=
<ftrvxmtrx@gmail.com>
Date: Thu, 28 Apr 2022 18:13:25 +0200
Subject: [PATCH] pipewire: update to 0.3.51
---
srcpkgs/pipewire/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/pipewire/template b/srcpkgs/pipewire/template
index 6427e0b66e77..4cf367d32675 100644
--- a/srcpkgs/pipewire/template
+++ b/srcpkgs/pipewire/template
@@ -1,6 +1,6 @@
# Template file for 'pipewire'
pkgname=pipewire
-version=0.3.50
+version=0.3.51
revision=1
_pms_version=0.4.1
build_style=meson
@@ -32,7 +32,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="a4bd81e9046f0bd19ecc18402b44199c6c4c54305670e43111c7fbdfe4d17bdf
+checksum="f18e7a2cd2fcd75482c3df4e736e01435bd20779ddf63da63b0a086d3a9735ac
119c9216070b54018217552c7924f9888da270c3c4647c5e2b85ffa6b1574975"
make_dirs="/var/lib/pipewire 0755 _pipewire _pipewire"
system_accounts="_pipewire"
next reply other threads:[~2022-04-28 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 16:14 ftrvxmtrx [this message]
2022-04-29 10:33 ` [PR PATCH] [Merged]: " paper42
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36899@inbox.vuxu.org \
--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).