From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pipewire: update to 0.3.42.
Date: Sat, 18 Dec 2021 12:02:47 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34602@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
There is a new pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages pipewire0.3.4.2
https://github.com/void-linux/void-packages/pull/34602
pipewire: update to 0.3.42.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: Yes
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, x86_64-musl
Its a small update ... But once again @st3r4g could you test it on your machine as well ?
A patch file from https://github.com/void-linux/void-packages/pull/34602.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pipewire0.3.4.2-34602.patch --]
[-- Type: text/x-diff, Size: 1297 bytes --]
From 59bc1690695d507780eb637b3abe8f05482556c5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Sat, 18 Dec 2021 11:00:21 +0000
Subject: [PATCH] pipewire: update to 0.3.42.
---
srcpkgs/pipewire/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/pipewire/template b/srcpkgs/pipewire/template
index 62d392db1b6c..668b4989bbec 100644
--- a/srcpkgs/pipewire/template
+++ b/srcpkgs/pipewire/template
@@ -1,6 +1,6 @@
# Template file for 'pipewire'
pkgname=pipewire
-version=0.3.41
+version=0.3.42
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="665dd941c37f96b2709871ac594d21850b39038eb69a99ae77a7954ad3c35f4e
+checksum="726d1f2faed6f1e93c1499cd20ff0d6461bc698166bea3b98d46c291794e6e1c
119c9216070b54018217552c7924f9888da270c3c4647c5e2b85ffa6b1574975"
make_dirs="/var/lib/pipewire 0755 _pipewire _pipewire"
system_accounts="_pipewire"
next reply other threads:[~2021-12-18 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 11:02 motorto [this message]
2021-12-18 23:20 ` [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-34602@inbox.vuxu.org \
--to=motorto@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).