From: klardotsh <klardotsh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] OpenRCT2: update to 0.4.6.
Date: Tue, 05 Sep 2023 17:38:41 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45922@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
There is a new pull request by klardotsh against master on the void-packages repository
https://github.com/klardotsh/void-packages klardotsh/update-orct2
https://github.com/void-linux/void-packages/pull/45922
OpenRCT2: update to 0.4.6.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
A patch file from https://github.com/void-linux/void-packages/pull/45922.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-klardotsh/update-orct2-45922.patch --]
[-- Type: text/x-diff, Size: 1958 bytes --]
From cc86c661850603039187d699f6cf1876bc6779a4 Mon Sep 17 00:00:00 2001
From: Josh Klar <josh@klar.sh>
Date: Tue, 5 Sep 2023 08:36:27 -0700
Subject: [PATCH] OpenRCT2: update to 0.4.6.
---
srcpkgs/OpenRCT2/template | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/OpenRCT2/template b/srcpkgs/OpenRCT2/template
index d737ebcd5c3fd..dd7e7c352e319 100644
--- a/srcpkgs/OpenRCT2/template
+++ b/srcpkgs/OpenRCT2/template
@@ -2,11 +2,11 @@
# based on https://raw.githubusercontent.com/AluisioASG/void-packages/openrct2/srcpkgs/OpenRCT2/template
# and https://github.com/void-linux/void-packages/issues/1014#issuecomment-417372421
pkgname=OpenRCT2
-version=0.4.5
-revision=3
+version=0.4.6
+revision=1
# versions pulled from https://raw.githubusercontent.com/OpenRCT2/OpenRCT2/v${version}/CMakeLists.txt
_objects_version=1.3.11
-_titles_version=0.4.0
+_titles_version=0.4.6
_replays_version=0.0.78
build_style=cmake
configure_args="
@@ -38,12 +38,12 @@ distfiles="https://github.com/OpenRCT2/OpenRCT2/archive/v${version}.tar.gz
https://github.com/OpenRCT2/OpenMusic/releases/download/v1.3.0/openmusic.zip
https://github.com/OpenRCT2/replays/releases/download/v${_replays_version}/replays.zip
https://github.com/OpenRCT2/title-sequences/releases/download/v${_titles_version}/title-sequences.zip"
-checksum="eb9e20dc0dcbf10b02b5f334a029983a0a2b43d931f95a2088a64e8b2657bab1
+checksum="80bfbf3a8756a8c98fdf15effcaac42c6cd92c07756c80d00b7dd56d0d0f282a
bf85d88e4fb11ca2e5915567390898747dc2459b3c7a057bdc32b829c91780b4
70be1b6ff8cc24ad8031a2e0cdd445b5dd3c52c886a8e5f70401f75152e4ae6c
b3423f574a969479d51dfa54f04edbe2557f37812409a9b5e5e52e59f71f4fb8
a6bdfdcc7d916ce060961c5fe7beaf43679fbfad9838cfdbd067617ae0ac0ddf
- 6e7c7b554717072bfc7acb96fd0101dc8e7f0ea0ea316367a05c2e92950c9029"
+ 24a189cdaf1f78fb6d6caede8f1ab3cedf8ab9f819cd2260a09b2cce4c710d98"
skip_extraction="objects.zip
opensound.zip
openmusic.zip
next reply other threads:[~2023-09-05 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 15:38 klardotsh [this message]
2023-09-06 23:09 ` [PR PATCH] [Closed]: " classabbyamp
2023-09-06 23:09 ` classabbyamp
-- strict thread matches above, loose matches on Subject: below --
2023-09-03 20:03 [PR PATCH] " TinfoilSubmarine
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-45922@inbox.vuxu.org \
--to=klardotsh@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).