From: skmpz <skmpz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] cava: update to 0.10.2.
Date: Thu, 16 May 2024 20:11:27 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50373@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
There is a new pull request by skmpz against master on the void-packages repository
https://github.com/skmpz/void-packages cava-0.10.2
https://github.com/void-linux/void-packages/pull/50373
cava: update to 0.10.2.
<!-- 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/50373.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cava-0.10.2-50373.patch --]
[-- Type: text/x-diff, Size: 1107 bytes --]
From 5072f766ff8ffdd3750b810b7ae7f983506eedbf Mon Sep 17 00:00:00 2001
From: skmpz <dem.procopiou@gmail.com>
Date: Thu, 16 May 2024 21:10:50 +0300
Subject: [PATCH] cava: update to 0.10.2.
---
srcpkgs/cava/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/cava/template b/srcpkgs/cava/template
index 6179fb552dddc2..102607733abb96 100644
--- a/srcpkgs/cava/template
+++ b/srcpkgs/cava/template
@@ -1,6 +1,6 @@
# Template file for 'cava'
pkgname=cava
-version=0.10.1
+version=0.10.2
revision=1
build_style=gnu-configure
hostmakedepends="autoconf-archive automake libtool pkg-config"
@@ -13,7 +13,7 @@ license="MIT"
homepage="https://github.com/karlstav/cava"
changelog="https://github.com/karlstav/cava/releases"
distfiles="https://github.com/karlstav/cava/archive/refs/tags/${version}.tar.gz"
-checksum=a3a60814326fa34b54e93ce0b1e66460d55f1007e576c5152fd47024d9ceaff9
+checksum=853ee78729ed3501d0cdf9c1947967ad3bfe6526d66a029b4ddf9adaa6334d4f
build_options="alsa jack pipewire pulseaudio sndio"
build_options_default="alsa jack pipewire pulseaudio sndio"
next reply other threads:[~2024-05-16 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 18:11 skmpz [this message]
2024-05-20 20:44 ` [PR PATCH] [Merged]: " cinerea0
-- strict thread matches above, loose matches on Subject: below --
2024-05-14 20:21 [PR PATCH] " tranzystorekk
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-50373@inbox.vuxu.org \
--to=skmpz@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).