Github messages for voidlinux
 help / color / mirror / Atom feed
From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pipewire: update to 0.3.28
Date: Thu, 20 May 2021 13:26:41 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31012@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3912 bytes --]

There is a new pull request by st3r4g against master on the void-packages repository

https://github.com/st3r4g/void-packages pipewire-0.3.28
https://github.com/void-linux/void-packages/pull/31012

pipewire: update to 0.3.28
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->

- The main change here is the move of default configs to `/usr/share`. `xbps` handled this well in my case (I had all default configs, which were deleted as expected). Can anyone verify that modified configs are left?
- I have briefly tried the filter-chains (`pipewire -c filter-chain/<X>.conf` runs a pipewire client that creates these "effect nodes") and they require ladspa plugins (one is not even packaged I think) but I don't think they should be hard dependencies. Also, some are borked still (e.g. `demonic.conf` currently only works with a `audio.channels = 1` workaround).

File diff for package `pipewire`:
```
--- /tmp/old    2021-05-20 01:30:21.627554276 +0200
+++ /tmp/new    2021-05-20 01:30:37.523553285 +0200
@@ -1,14 +1,3 @@
-/etc/pipewire/client-rt.conf
-/etc/pipewire/client.conf
-/etc/pipewire/jack.conf
-/etc/pipewire/media-session.d/alsa-monitor.conf
-/etc/pipewire/media-session.d/bluez-monitor.conf
-/etc/pipewire/media-session.d/media-session.conf
-/etc/pipewire/media-session.d/v4l2-monitor.conf
-/etc/pipewire/pipewire-pulse.conf
-/etc/pipewire/pipewire.conf
-/etc/pipewire/media-session.d/with-jack
-/etc/pipewire/media-session.d/with-pulseaudio
 /usr/bin/pipewire
 /usr/bin/pipewire-media-session
 /usr/bin/pipewire-pulse
@@ -165,6 +154,22 @@
 /usr/share/man/man1/pw-mon.1
 /usr/share/man/man1/pw-profiler.1
 /usr/share/man/man5/pipewire.conf.5
+/usr/share/pipewire/client-rt.conf
+/usr/share/pipewire/client.conf
+/usr/share/pipewire/filter-chain/demonic.conf
+/usr/share/pipewire/filter-chain/sink-dolby-surround.conf
+/usr/share/pipewire/filter-chain/sink-eq6.conf
+/usr/share/pipewire/filter-chain/sink-matrix-spatialiser.conf
+/usr/share/pipewire/filter-chain/source-rnnoise.conf
+/usr/share/pipewire/jack.conf
+/usr/share/pipewire/media-session.d/alsa-monitor.conf
+/usr/share/pipewire/media-session.d/bluez-monitor.conf
+/usr/share/pipewire/media-session.d/media-session.conf
+/usr/share/pipewire/media-session.d/v4l2-monitor.conf
+/usr/share/pipewire/media-session.d/with-jack
+/usr/share/pipewire/media-session.d/with-pulseaudio
+/usr/share/pipewire/pipewire-pulse.conf
+/usr/share/pipewire/pipewire.conf
 /usr/bin/pw-midiplay -> /usr/bin/pw-cat
 /usr/bin/pw-midirecord -> /usr/bin/pw-cat
 /usr/bin/pw-play -> /usr/bin/pw-cat
```


A patch file from https://github.com/void-linux/void-packages/pull/31012.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pipewire-0.3.28-31012.patch --]
[-- Type: text/x-diff, Size: 1182 bytes --]

From 27e685d073878961911054a9138e235d00f026c0 Mon Sep 17 00:00:00 2001
From: Stefano Ragni <stefano.ragni@outlook.com>
Date: Thu, 20 May 2021 13:13:52 +0200
Subject: [PATCH] pipewire: update to 0.3.28

---
 srcpkgs/pipewire/template | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/pipewire/template b/srcpkgs/pipewire/template
index a38a16e3e975..43e3c1cfc9b4 100644
--- a/srcpkgs/pipewire/template
+++ b/srcpkgs/pipewire/template
@@ -1,6 +1,6 @@
 # Template file for 'pipewire'
 pkgname=pipewire
-version=0.3.27
+version=0.3.28
 revision=1
 build_style=meson
 configure_args="-Dman=enabled -Dgstreamer=enabled -Ddocs=enabled -Dsystemd=disabled
@@ -18,8 +18,7 @@ license="MIT"
 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"
-checksum=657db1b9a29ae17a9f1d9782a45bda2ba5a893fef55e1ca26453e8f7f2d4e64e
-conf_files="/etc/pipewire/*.conf /etc/pipewire/media-session.d/*.conf"
+checksum=1d9271e121a5049aef379e9bb7c50524faa6f971e668806637d7b9df1b7cab88
 
 build_options="sdl2"
 

             reply	other threads:[~2021-05-20 11:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20 11:26 st3r4g [this message]
2021-05-20 18:25 ` [PR PATCH] [Updated] " st3r4g
2021-05-20 18:29 ` st3r4g
2021-05-21  0:05 ` ericonr
2021-05-21  7:39 ` [PR PATCH] [Updated] " st3r4g
2021-05-21 19:02 ` [PR PATCH] [Merged]: " ericonr

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-31012@inbox.vuxu.org \
    --to=st3r4g@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).