From: Tsu-gu <Tsu-gu@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] audacious: update to 4.2
Date: Sat, 19 Nov 2022 13:52:36 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40612@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]
There is a new pull request by Tsu-gu against master on the void-packages repository
https://github.com/Tsu-gu/void-packages Audacious-4.2-update
https://github.com/void-linux/void-packages/pull/40612
audacious: update to 4.2
I've changed the version, alongside the checksum, and succesfully compiled and run the package. It will not launch without audacious-plugins, which I have also updated and succesfully compiled.
<!-- 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**
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
-->
A patch file from https://github.com/void-linux/void-packages/pull/40612.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-Audacious-4.2-update-40612.patch --]
[-- Type: text/x-diff, Size: 1343 bytes --]
From 0a00c8e1a445f97eb77587a370af474ca543b096 Mon Sep 17 00:00:00 2001
From: Tsu-gu <108401269+Tsu-gu@users.noreply.github.com>
Date: Sat, 19 Nov 2022 11:24:17 +0000
Subject: [PATCH] Update audacious to 4.2
I've changed the version, alongside the checksum, and succesfully compiled and run the package. It will not launch without audacious-plugins, which I have also updated and succesfully compiled.
---
srcpkgs/audacious/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/audacious/template b/srcpkgs/audacious/template
index ebeca48a6171..7df759a2f29a 100644
--- a/srcpkgs/audacious/template
+++ b/srcpkgs/audacious/template
@@ -1,7 +1,7 @@
# Template file for 'audacious'
#Keep in sync with audacious-plugins!
pkgname=audacious
-version=4.1
+version=4.2
revision=1
build_style=gnu-configure
configure_args="$(vopt_enable gtk) $(vopt_enable qt) --enable-libarchive"
@@ -14,7 +14,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="BSD-2-Clause"
homepage="https://audacious-media-player.org/"
distfiles="https://distfiles.${pkgname}-media-player.org/${pkgname}-${version}.tar.bz2"
-checksum=1f58858f9789e867c513b5272987f13bdfb09332b03c2814ad4c6e29f525e35c
+checksum=feb304e470a481fe2b3c4ca1c9cb3b23ec262540c12d0d1e6c22a5eb625e04b3
build_options="gtk qt"
build_options_default="qt"
next reply other threads:[~2022-11-19 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 12:52 Tsu-gu [this message]
2022-11-19 13:00 ` paper42
2022-11-19 13:00 ` [PR PATCH] [Closed]: " paper42
-- strict thread matches above, loose matches on Subject: below --
2022-09-23 11:19 [PR PATCH] " usernamer-git
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-40612@inbox.vuxu.org \
--to=tsu-gu@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).