Github messages for voidlinux
 help / color / mirror / Atom feed
From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] OpenRCT2: update to 0.4.3.
Date: Tue, 20 Dec 2022 02:33:10 +0100	[thread overview]
Message-ID: <20221220013310.gTUlhJJ3jVoCEhZHhT7JKlxdWi5Tti2UcpExIxolzWU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41083@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]

There is an updated pull request by TinfoilSubmarine against master on the void-packages repository

https://github.com/TinfoilSubmarine/void-packages update/OpenRCT2
https://github.com/void-linux/void-packages/pull/41083

OpenRCT2: update to 0.4.3.
<!-- 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/41083.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/OpenRCT2-41083.patch --]
[-- Type: text/x-diff, Size: 2698 bytes --]

From 2ece4d305f6e999e34ef40a24c42c3d46ec01a2b Mon Sep 17 00:00:00 2001
From: Joel Beckmeyer <joel@beckmeyer.us>
Date: Wed, 14 Dec 2022 08:17:25 -0500
Subject: [PATCH] OpenRCT2: update to 0.4.3.

---
 srcpkgs/OpenRCT2/template | 18 ++++++++++--------
 srcpkgs/OpenRCT2/update   |  2 ++
 2 files changed, 12 insertions(+), 8 deletions(-)
 create mode 100644 srcpkgs/OpenRCT2/update

diff --git a/srcpkgs/OpenRCT2/template b/srcpkgs/OpenRCT2/template
index 55152b2907fb..4201a9ca64ea 100644
--- a/srcpkgs/OpenRCT2/template
+++ b/srcpkgs/OpenRCT2/template
@@ -2,11 +2,12 @@
 # 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
-_objects_version=1.3.5
-_titles_version=0.4.0
-_replays_version=0.0.69
-version=0.4.2
+version=0.4.3
 revision=1
+# versions pulled from https://raw.githubusercontent.com/OpenRCT2/OpenRCT2/v${version}/CMakeLists.txt
+_objects_version=1.3.7
+_titles_version=0.4.0
+_replays_version=0.0.70
 build_style=cmake
 configure_args="
  -DOPENRCT2_VERSION_TAG=${version}
@@ -34,10 +35,10 @@ changelog="https://openrct2.org/changelog"
 distfiles="https://github.com/OpenRCT2/OpenRCT2/archive/v${version}.tar.gz
  https://github.com/OpenRCT2/objects/releases/download/v${_objects_version}/objects.zip
  https://github.com/OpenRCT2/title-sequences/releases/download/v${_titles_version}/title-sequences.zip"
-checksum="e313f29ad757d8c4870c166e7342accd642d1e6e7b245385d60e161ef4a0028f
- 4859b7a443d0969cb1c639202fe70f40ac4c2625830657c72645d987912258ff
+checksum="1269759b3a90717f379cd375f30629e3f24d3fdeb0c54cc1dca03676e64731ef
+ d6be9743c68f233674f5549204637b1f0304d7567a816d18e3f1576500a51d38
  6e7c7b554717072bfc7acb96fd0101dc8e7f0ea0ea316367a05c2e92950c9029"
-skip_extraction="objects.zip title-sequences.zip replays.zip"
+skip_extraction="objects.zip title-sequences.zip"
 
 replaces="OpenRCT2-data>=0"
 
@@ -71,7 +72,8 @@ if [ "$XBPS_CHECK_PKGS" ]; then
 	configure_args+=" -DWITH_TESTS=1 -DSYSTEM_GTEST=1"
 	# download replays, used in tests
 	distfiles+=" https://github.com/OpenRCT2/replays/releases/download/v${_replays_version}/replays.zip"
-	checksum+=" bf2184cc6ace156402a26d3e4693b6363b888fe3038daa59e33b202ce0efe0d9"
+	checksum+=" 89156436e51413f180a12d4647406193ac44a509b1ad64d57705f0ae5125b093"
+	skip_extraction+=" replays.zip"
 fi
 
 if [ "$XBPS_TARGET_NO_ATOMIC8" ]; then
diff --git a/srcpkgs/OpenRCT2/update b/srcpkgs/OpenRCT2/update
new file mode 100644
index 000000000000..70a48a70d5bd
--- /dev/null
+++ b/srcpkgs/OpenRCT2/update
@@ -0,0 +1,2 @@
+site="https://github.com/OpenRCT2/OpenRCT2/tags"
+pkgname="v"

  parent reply	other threads:[~2022-12-20  1:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 13:26 [PR PATCH] " TinfoilSubmarine
2022-12-14 18:22 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-12-18 11:38 ` [PR REVIEW] " paper42
2022-12-19  2:31 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-12-19 19:44 ` [PR REVIEW] " paper42
2022-12-20  1:33 ` TinfoilSubmarine [this message]
2022-12-24 23:30 ` [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=20221220013310.gTUlhJJ3jVoCEhZHhT7JKlxdWi5Tti2UcpExIxolzWU@z \
    --to=tinfoilsubmarine@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).