From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] rosegarden: update to 22.06
Date: Sun, 12 Jun 2022 22:09:17 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37536@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
There is a new pull request by newbluemoon against master on the void-packages repository
https://github.com/newbluemoon/void-packages rosegarden
https://github.com/void-linux/void-packages/pull/37536
rosegarden: update to 22.06
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x86_64-musl
- i686
- armv7l-musl
A patch file from https://github.com/void-linux/void-packages/pull/37536.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rosegarden-37536.patch --]
[-- Type: text/x-diff, Size: 1130 bytes --]
From 4e062e9c3056a79713d28f72a1dac26516de6afd Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Sun, 12 Jun 2022 21:42:37 +0200
Subject: [PATCH] rosegarden: update to 22.06
---
srcpkgs/rosegarden/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/rosegarden/template b/srcpkgs/rosegarden/template
index e909cd4173b5..d9bf2c26cd76 100644
--- a/srcpkgs/rosegarden/template
+++ b/srcpkgs/rosegarden/template
@@ -1,6 +1,6 @@
# Template file for 'rosegarden'
pkgname=rosegarden
-version=21.12
+version=22.06
revision=1
build_style=cmake
hostmakedepends="pkg-config shared-mime-info"
@@ -12,7 +12,7 @@ maintainer="newbluemoon <blaumolch@mailbox.org>"
license="GPL-2.0-or-later"
homepage="http://rosegardenmusic.com/"
distfiles="${SOURCEFORGE_SITE}/rosegarden/rosegarden/${version/*.*.*/${version%.*}}/rosegarden-${version}.tar.bz2"
-checksum=dc3ed3db064e754de9fe830b69df40a53dc7157fbfa8a206ca82e5e41c262809
+checksum=9024825155ebb1be8b4af567f3502026957398fdefd086e23fe399f1d033fadb
if [ -n "${CROSS_BUILD}" ]; then
hostmakedepends+=" qt5-devel qt5-host-tools"
next reply other threads:[~2022-06-12 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 20:09 newbluemoon [this message]
2022-06-24 20:44 ` [PR PATCH] [Merged]: " paper42
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-37536@inbox.vuxu.org \
--to=newbluemoon@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).