Github messages for voidlinux
 help / color / mirror / Atom feed
From: amak79 <amak79@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] snapcast: update to 0.26.0
Date: Tue, 06 Sep 2022 01:52:58 +0200	[thread overview]
Message-ID: <20220905235258.cg7gobFROeReIpw2HH5JaHtoZRKhZvbDhyulen1jSxU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39095@inbox.vuxu.org>

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

There is an updated pull request by amak79 against master on the void-packages repository

https://github.com/amak79/void-packages snapcast
https://github.com/void-linux/void-packages/pull/39095

snapcast: update to 0.26.0
<!-- 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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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, (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/39095.patch is attached

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

From 1438ad7063c9237f04841e13dd1661d5bb6b92b2 Mon Sep 17 00:00:00 2001
From: amak <amak.git@outlook.com>
Date: Sun, 4 Sep 2022 19:28:29 +1000
Subject: [PATCH] snapcast: update to 0.26.0

---
 .../patches/meta_mpd.py-permission-fix.patch  | 19 +++++++++++++++++++
 srcpkgs/snapcast/template                     |  5 +++--
 2 files changed, 22 insertions(+), 2 deletions(-)
 create mode 100644 srcpkgs/snapcast/patches/meta_mpd.py-permission-fix.patch

diff --git a/srcpkgs/snapcast/patches/meta_mpd.py-permission-fix.patch b/srcpkgs/snapcast/patches/meta_mpd.py-permission-fix.patch
new file mode 100644
index 000000000000..ebff8013f574
--- /dev/null
+++ b/srcpkgs/snapcast/patches/meta_mpd.py-permission-fix.patch
@@ -0,0 +1,19 @@
+This patch fixes an issue where meta_mpd.py is installed with executable
+permissions only. This results in a 'Permission denied' message for
+03-rewrite-python-shebang, and a fatal error for xbps-create when processing
+the file hash. Fixed upstream in 7ab3daa.
+
+https://github.com/badaix/snapcast/issues/1021
+
+diff --git a/server/CMakeLists.txt b/server/CMakeLists.txt
+index e1271b80..25432cd5 100644
+--- a/server/CMakeLists.txt
++++ b/server/CMakeLists.txt
+@@ -117,6 +117,6 @@ else()
+     install(FILES etc/snapserver.conf COMPONENT server DESTINATION ${CMAKE_INSTALL_SYSCONFDIR})
+     install(FILES etc/index.html COMPONENT server DESTINATION ${CMAKE_INSTALL_DATADIR}/snapserver)
+     install(DIRECTORY etc/snapweb/ DESTINATION ${CMAKE_INSTALL_DATADIR}/snapserver/snapweb)
+-    install(FILES etc/plug-ins/meta_mpd.py PERMISSIONS OWNER_EXECUTE GROUP_EXECUTE WORLD_EXECUTE DESTINATION ${CMAKE_INSTALL_DATADIR}/snapserver/plug-ins/)
++    install(FILES etc/plug-ins/meta_mpd.py PERMISSIONS OWNER_READ OWNER_WRITE OWNER_EXECUTE GROUP_READ GROUP_EXECUTE WORLD_READ WORLD_EXECUTE DESTINATION ${CMAKE_INSTALL_DATADIR}/snapserver/plug-ins/)
+     #install(FILES ../debian/snapserver.service DESTINATION ${SYSTEMD_SERVICES_INSTALL_DIR})
+ endif()
diff --git a/srcpkgs/snapcast/template b/srcpkgs/snapcast/template
index 918f02061082..e330653723ed 100644
--- a/srcpkgs/snapcast/template
+++ b/srcpkgs/snapcast/template
@@ -1,6 +1,6 @@
 # Template file for 'snapcast'
 pkgname=snapcast
-version=0.25.0
+version=0.26.0
 revision=1
 build_style=cmake
 configure_args="-DCMAKE_INSTALL_SYSCONFDIR=/etc -DBUILD_WITH_TREMOR=OFF
@@ -14,8 +14,9 @@ short_desc="Synchronous multi-room audio player"
 maintainer="amak <amak.git@outlook.com>"
 license="GPL-3.0-or-later"
 homepage="https://github.com/badaix/snapcast"
+changelog="https://raw.githubusercontent.com/badaix/snapcast/master/changelog.md"
 distfiles="https://github.com/badaix/snapcast/archive/v${version}.tar.gz"
-checksum=c4e449cb693e091261727421f4965492be049632537e034fa9c59c92d091a846
+checksum=166353267a5c461a3a0e7cbd05d78c4bfdaebeda078801df3b76820b54f27683
 
 build_options="avahi pulseaudio"
 build_options_default="avahi pulseaudio"

  parent reply	other threads:[~2022-09-05 23:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04  9:30 [PR PATCH] " amak79
2022-09-05 15:56 ` [PR REVIEW] " classabbyamp
2022-09-05 23:52 ` amak79 [this message]
2022-09-06  0:02 ` [PR PATCH] [Merged]: " classabbyamp

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=20220905235258.cg7gobFROeReIpw2HH5JaHtoZRKhZvbDhyulen1jSxU@z \
    --to=amak79@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).