From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] pipewire: update to 0.3.41.
Date: Tue, 14 Dec 2021 11:21:53 +0100 [thread overview]
Message-ID: <20211214102153.bNxYyZy7xhcjx9TuOBpQHDL6g3F8Mn9CzNNPEZWa_CA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34524@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
There is an updated pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages pipewire
https://github.com/void-linux/void-packages/pull/34524
pipewire: update to 0.3.41.
#### Testing the changes
- I tested the changes in this PR: YES, I am currently using it on my system and its working until the moment flawlessly
(tried Bluetooth and Laptop Speakers)
#### Local build testing
I built this PR locally for my native architecture, (x86_64-musl)
@st3r4g
Since you are more active in updating this packages, how does it look ?
A patch file from https://github.com/void-linux/void-packages/pull/34524.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pipewire-34524.patch --]
[-- Type: text/x-diff, Size: 1898 bytes --]
From 37dc1a9b3e6bed137d5f747bdcb7a7a6f76efe6a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Tue, 14 Dec 2021 10:10:17 +0000
Subject: [PATCH] pipewire: update to 0.3.41.
---
srcpkgs/pipewire/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/pipewire/template b/srcpkgs/pipewire/template
index 67ffc1882f3e..62d392db1b6c 100644
--- a/srcpkgs/pipewire/template
+++ b/srcpkgs/pipewire/template
@@ -1,6 +1,6 @@
# Template file for 'pipewire'
pkgname=pipewire
-version=0.3.40
+version=0.3.41
revision=1
_pms_version=0.4.1
build_style=meson
@@ -21,7 +21,7 @@ makedepends="$(vopt_if sdl2 SDL2-devel) gst-plugins-base1-devel jack-devel
sbc-devel v4l-utils-devel libva-devel libbluetooth-devel ncurses-devel
libfreeaptx-devel libusb-devel fdk-aac-devel libsndfile-devel Vulkan-Headers
vulkan-loader pulseaudio-devel avahi-libs-devel webrtc-audio-processing-devel
- readline-devel"
+ readline-devel openssl-devel lilv-devel "
depends="libspa-alsa>=${version}_${revision} libspa-audioconvert>=${version}_${revision}
libspa-audiomixer>=${version}_${revision} libspa-control>=${version}_${revision}
libspa-v4l2>=${version}_${revision}"
@@ -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="a2c8176d757a2ac6db445c61a50802ff1c26f49f5a28174f5eb0278609a887cf
+checksum="665dd941c37f96b2709871ac594d21850b39038eb69a99ae77a7954ad3c35f4e
119c9216070b54018217552c7924f9888da270c3c4647c5e2b85ffa6b1574975"
make_dirs="/var/lib/pipewire 0755 _pipewire _pipewire"
system_accounts="_pipewire"
next prev parent reply other threads:[~2021-12-14 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 10:14 [PR PATCH] " motorto
2021-12-14 10:21 ` motorto [this message]
2021-12-14 16:14 ` [PR PATCH] [Merged]: " Duncaen
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=20211214102153.bNxYyZy7xhcjx9TuOBpQHDL6g3F8Mn9CzNNPEZWa_CA@z \
--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).