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.35
Date: Sat, 11 Sep 2021 16:30:49 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32927@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1594 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.35
https://github.com/void-linux/void-packages/pull/32927

pipewire: update to 0.3.35
<!-- 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
-->


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

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

From 0dd88c19b6c78ecccdaee95c0704755be8b4c1ba Mon Sep 17 00:00:00 2001
From: Stefano Ragni <stefano.ragni@outlook.com>
Date: Sat, 11 Sep 2021 16:28:01 +0200
Subject: [PATCH] pipewire: update to 0.3.35

---
 srcpkgs/pipewire/patches/autostart-media-session.patch | 8 +++++---
 srcpkgs/pipewire/template                              | 6 +++---
 2 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/srcpkgs/pipewire/patches/autostart-media-session.patch b/srcpkgs/pipewire/patches/autostart-media-session.patch
index 87ab20765488..a5c1168ae6ec 100644
--- a/srcpkgs/pipewire/patches/autostart-media-session.patch
+++ b/srcpkgs/pipewire/patches/autostart-media-session.patch
@@ -2,13 +2,15 @@ Upstream's config does not autostart pipewire-media-session anymore, which
 is an essential component. It's not easy to start it externally in a script
 since it needs the pipewire socket up, and Void doesn't have a mechanism to
 ensure it (systemd socket activation).
---- a/src/daemon/pipewire.conf.in
+diff --git a/src/daemon/pipewire.conf.in.orig b/src/daemon/pipewire.conf.in
+index 95632c2..ab0b097 100644
+--- a/src/daemon/pipewire.conf.in.orig
 +++ b/src/daemon/pipewire.conf.in
-@@ -234,7 +234,7 @@
+@@ -235,7 +235,7 @@ context.exec = [
      # but it is better to start it as a systemd service.
      # Run the session manager with -h for options.
      #
--    @comment@{ path = "@session_manager_path@"  args = "@session_manager_args@" }
+-    @sm_comment@{ path = "@session_manager_path@"  args = "@session_manager_args@" }
 +    { path = "@session_manager_path@"  args = "@session_manager_args@" }
      #
      # You can optionally start the pulseaudio-server here as well
diff --git a/srcpkgs/pipewire/template b/srcpkgs/pipewire/template
index 8346d6097bc4..add876541b82 100644
--- a/srcpkgs/pipewire/template
+++ b/srcpkgs/pipewire/template
@@ -1,6 +1,6 @@
 # Template file for 'pipewire'
 pkgname=pipewire
-version=0.3.34
+version=0.3.35
 revision=1
 build_style=meson
 configure_args="
@@ -14,7 +14,7 @@ configure_args="
  -Dudevrulesdir=/usr/lib/udev/rules.d
  -Dvulkan=enabled
 "
-hostmakedepends="doxygen graphviz pkg-config xmltoman gettext"
+hostmakedepends="doxygen graphviz pkg-config python3-docutils gettext"
 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
@@ -27,7 +27,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=7934dd634fa2c6ef7f30c28bc33c102ac39e510dfbbbb4388906590b80b8c991
+checksum=390ac706e2e3edf8c95ffeeb8e1115dc5a2dd89d5275dce923bba75f944bea7e
 make_dirs="/var/lib/pipewire 0755 _pipewire _pipewire"
 system_accounts="_pipewire"
 

             reply	other threads:[~2021-09-11 14:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-11 14:30 st3r4g [this message]
2021-09-13 17:27 ` [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-32927@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).