From: ALEX11BR <ALEX11BR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] openttd: update to 1.10.3.
Date: Sun, 04 Oct 2020 20:37:24 +0200 [thread overview]
Message-ID: <20201004183724.DbLXwJ0-1lJYZXLULVLYWPxE7Bhw59B96onKknlv_I4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25335@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 317 bytes --]
There is an updated pull request by ALEX11BR against master on the void-packages repository
https://github.com/ALEX11BR/void-packages master
https://github.com/void-linux/void-packages/pull/25335
openttd: update to 1.10.3.
A patch file from https://github.com/void-linux/void-packages/pull/25335.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-25335.patch --]
[-- Type: text/x-diff, Size: 1883 bytes --]
From 521d0fb9f0c2a057c19afb7f5f3f97cb77c65d6c Mon Sep 17 00:00:00 2001
From: Popa Ioan Alexandru <alexioanpopa11@gmail.com>
Date: Sun, 4 Oct 2020 17:34:52 +0300
Subject: [PATCH 1/2] openttd: update to 1.10.3.
---
srcpkgs/openttd/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/openttd/template b/srcpkgs/openttd/template
index 47df4a01b56..c768213a19e 100644
--- a/srcpkgs/openttd/template
+++ b/srcpkgs/openttd/template
@@ -1,6 +1,6 @@
# Template file for 'openttd'
pkgname=openttd
-version=1.10.2
+version=1.10.3
revision=1
_gfxver=0.6.0
_sfxver=0.2.3
@@ -16,7 +16,7 @@ homepage="https://www.openttd.org/"
distfiles="https://proxy.binaries.openttd.org/openttd-releases/${version}/openttd-${version}-source.tar.xz
https://cdn.openttd.org/opengfx-releases/${_gfxver}/opengfx-${_gfxver}-all.zip
https://cdn.openttd.org/opensfx-releases/${_sfxver}/opensfx-${_sfxver}-all.zip"
-checksum="939c55d259fb13cb47dfb3244e8f7b9e2f723883ebb2119410d8a282724eb6f5
+checksum="c11601ef547eb1f6d4f9a035bd19e0a760b47872ce7d9b4117aaa45ac377b53b
d419c0f5f22131de15f66ebefde464df3b34eb10e0645fe218c59cbc26c20774
6831b651b3dc8b494026f7277989a1d757961b67c17b75d3c2e097451f75af02"
From 62e714f9bb704913ecb1c4fcedb715ba59fcc043 Mon Sep 17 00:00:00 2001
From: Popa Ioan Alexandru <alexioanpopa11@gmail.com>
Date: Sun, 4 Oct 2020 21:36:24 +0300
Subject: [PATCH 2/2] openttd: update to 1.10.3 and removed noarch from
openttd-data
---
srcpkgs/openttd/template | 1 -
1 file changed, 1 deletion(-)
diff --git a/srcpkgs/openttd/template b/srcpkgs/openttd/template
index c768213a19e..ea8a756549d 100644
--- a/srcpkgs/openttd/template
+++ b/srcpkgs/openttd/template
@@ -45,7 +45,6 @@ do_configure() {
openttd-data_package() {
short_desc+=" - data files"
- archs=noarch
pkg_install() {
vmove usr/share/openttd
vmkdir usr/share/openttd/data
next prev parent reply other threads:[~2020-10-04 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 11:42 [PR PATCH] " ALEX11BR
2020-10-04 18:37 ` ALEX11BR [this message]
2020-10-09 5:37 ` ALEX11BR
2020-10-09 11:50 ` Duncaen
2020-10-09 18:49 ` [PR PATCH] [Updated] " ALEX11BR
2020-10-18 16:59 ` [PR PATCH] [Closed]: " ALEX11BR
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=20201004183724.DbLXwJ0-1lJYZXLULVLYWPxE7Bhw59B96onKknlv_I4@z \
--to=alex11br@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).