From: jsbronder <jsbronder@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pipewire: update to 0.3.48.
Date: Fri, 25 Mar 2022 15:35:46 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36331@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
There is a new pull request by jsbronder against master on the void-packages repository
https://github.com/jsbronder/void-packages pipewire-0.3.48
https://github.com/void-linux/void-packages/pull/36331
pipewire: update to 0.3.48.
#### 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-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64
- x86_64-musl
A patch file from https://github.com/void-linux/void-packages/pull/36331.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pipewire-0.3.48-36331.patch --]
[-- Type: text/x-diff, Size: 1278 bytes --]
From 40657370b4bd0fe6a4f9af007887a08046e45ac1 Mon Sep 17 00:00:00 2001
From: Justin Bronder <jsbronder@cold-front.org>
Date: Fri, 25 Mar 2022 10:33:02 -0400
Subject: [PATCH] pipewire: update to 0.3.48.
---
srcpkgs/pipewire/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/pipewire/template b/srcpkgs/pipewire/template
index 0924ae71ba1f..5ed1ee1d3bd6 100644
--- a/srcpkgs/pipewire/template
+++ b/srcpkgs/pipewire/template
@@ -1,6 +1,6 @@
# Template file for 'pipewire'
pkgname=pipewire
-version=0.3.47
+version=0.3.48
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="8d70170a91ecba73746c1d83f95d54eee8ca71d0c3521926f05ed830d8b5a84e
+checksum="0d218be86b3d2b548c06259c47ad8d110ee1c09f071e17c4393eeef5c880fa6f
119c9216070b54018217552c7924f9888da270c3c4647c5e2b85ffa6b1574975"
make_dirs="/var/lib/pipewire 0755 _pipewire _pipewire"
system_accounts="_pipewire"
next reply other threads:[~2022-03-25 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 14:35 jsbronder [this message]
2022-03-25 21:59 ` [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-36331@inbox.vuxu.org \
--to=jsbronder@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).