From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] jamulus: update to 3.9.1
Date: Sun, 11 Jun 2023 13:25:16 +0200 [thread overview]
Message-ID: <20230611112516.phlOD0PgYjYCeZ0osa4EYtmmUjbmc7X3SRIHFLo6UZ8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42687@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
There is an updated pull request by classabbyamp against master on the void-packages repository
https://github.com/astralchan/void-packages jamulus
https://github.com/void-linux/void-packages/pull/42687
jamulus: update to 3.9.1
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
supersedes [#40204](https://github.com/void-linux/void-packages/pull/40204)
A patch file from https://github.com/void-linux/void-packages/pull/42687.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-jamulus-42687.patch --]
[-- Type: text/x-diff, Size: 1176 bytes --]
From 7eec685e28a4c06897a433a6a638378b7bb52203 Mon Sep 17 00:00:00 2001
From: astral <astral@astralchan.xyz>
Date: Fri, 10 Mar 2023 02:47:30 -0700
Subject: [PATCH] jamulus: update to 3.9.1
---
srcpkgs/jamulus/template | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/jamulus/template b/srcpkgs/jamulus/template
index db577f6dd83a..452d9d6f513d 100644
--- a/srcpkgs/jamulus/template
+++ b/srcpkgs/jamulus/template
@@ -1,6 +1,6 @@
# Template file for 'jamulus'
pkgname=jamulus
-version=3.9.0
+version=3.9.1
revision=1
_version=r${version//./_}
build_style=qmake
@@ -11,5 +11,6 @@ short_desc="Play music online. With friends. For free"
maintainer="astralchan <astral@astralchan.xyz>"
license="GPL-2.0-or-later"
homepage="https://jamulus.io"
-distfiles="https://github.com/corrados/jamulus/archive/${_version}.tar.gz"
-checksum=742b1954111c55b39ea7b2863c762d6731359e2b4793ef2409b150096fb196a5
+changelog="https://raw.githubusercontent.com/jamulussoftware/jamulus/main/ChangeLog"
+distfiles="https://github.com/jamulussoftware/jamulus/archive/${_version}.tar.gz"
+checksum=758381a92ff7b264534773b71b6bf8e098bbeb6d693efdc2916609f2ff842889
next prev parent reply other threads:[~2023-06-11 11:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 9:49 [PR PATCH] " astralchan
2023-03-10 19:54 ` [PR REVIEW] " paper42
2023-03-10 19:54 ` paper42
2023-03-11 1:20 ` astralchan
2023-03-11 1:26 ` [PR PATCH] [Updated] " astralchan
2023-03-11 1:27 ` [PR REVIEW] " astralchan
2023-03-11 6:28 ` classabbyamp
2023-03-11 8:26 ` astralchan
2023-03-11 8:27 ` astralchan
2023-03-11 8:29 ` paper42
2023-03-12 2:13 ` astralchan
2023-03-12 2:19 ` astralchan
2023-03-12 2:21 ` astralchan
2023-06-11 2:09 ` github-actions
2023-06-11 11:25 ` classabbyamp [this message]
2023-06-11 11:31 ` [PR PATCH] [Merged]: " classabbyamp
-- strict thread matches above, loose matches on Subject: below --
2022-10-28 14:12 [PR PATCH] Update Jamulus 3.9.0 -> 3.9.1 38github
2022-11-02 22:35 ` [PR PATCH] [Updated] jamulus: update to 3.9.1 38github
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=20230611112516.phlOD0PgYjYCeZ0osa4EYtmmUjbmc7X3SRIHFLo6UZ8@z \
--to=classabbyamp@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).