From: Emru1 <Emru1@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] runelite-launcher: update to 2.7.1, adopt
Date: Sat, 30 Mar 2024 16:53:35 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49609@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
There is a new pull request by Emru1 against master on the void-packages repository
https://github.com/Emru1/void-packages runelite-2.7.1
https://github.com/void-linux/void-packages/pull/49609
runelite-launcher: update to 2.7.1, adopt
<!-- 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/49609.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-runelite-2.7.1-49609.patch --]
[-- Type: text/x-diff, Size: 1180 bytes --]
From 600ad7e646547206d413fec604d12a42c35c9d4d Mon Sep 17 00:00:00 2001
From: Emil Tomczyk <emil.tomczyk@skni.umcs.pl>
Date: Sat, 30 Mar 2024 16:45:33 +0100
Subject: [PATCH] runelite-launcher: update to 2.7.1.
---
srcpkgs/runelite-launcher/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/runelite-launcher/template b/srcpkgs/runelite-launcher/template
index 419b1440521b25..e6fe6b69c7e287 100644
--- a/srcpkgs/runelite-launcher/template
+++ b/srcpkgs/runelite-launcher/template
@@ -1,15 +1,15 @@
# Template file for 'runelite-launcher'
pkgname=runelite-launcher
-version=2.6.9
+version=2.7.1
revision=1
hostmakedepends="apache-maven openjdk11"
depends="virtual?java-runtime"
short_desc="Open source Old School RuneScape client"
-maintainer="Orphaned <orphan@voidlinux.org>"
+maintainer="Emil Tomczyk <emru@emru.xyz>"
license="BSD-2-Clause"
homepage="https://runelite.net"
distfiles="https://github.com/runelite/launcher/archive/${version}.tar.gz"
-checksum=cc5375f9e41669fcd22dfa68f6e17b80cc90b0db385d27dfcdd9f3e18e1c5100
+checksum=2b5e5f07b5961eeb419b275613ed9008cfcd62768604bca637a5ef37e54e722a
do_build() {
mvn package
next reply other threads:[~2024-03-30 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 15:53 Emru1 [this message]
2024-06-18 13:32 ` [PR PATCH] [Updated] " Emru1
2024-06-18 15:25 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49609@inbox.vuxu.org \
--to=emru1@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).