Github messages for voidlinux
 help / color / mirror / Atom feed
From: SolitudeSF <SolitudeSF@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] freeorion: update to 0.4.10
Date: Mon, 27 Jul 2020 18:49:28 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23873@inbox.vuxu.org> (raw)

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

There is a new pull request by SolitudeSF against master on the void-packages repository

https://github.com/SolitudeSF/void-packages freeorion
https://github.com/void-linux/void-packages/pull/23873

freeorion: update to 0.4.10


A patch file from https://github.com/void-linux/void-packages/pull/23873.patch is attached

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

From 8b682b70e336adb76c76fe56cef8bb0513c896c4 Mon Sep 17 00:00:00 2001
From: SolitudeSF <solitudesf@protonmail.com>
Date: Mon, 27 Jul 2020 18:19:29 +0300
Subject: [PATCH] freeorion: update to 0.4.10

---
 srcpkgs/freeorion/template | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/freeorion/template b/srcpkgs/freeorion/template
index 3078bee0d7b..62c8ef70df9 100644
--- a/srcpkgs/freeorion/template
+++ b/srcpkgs/freeorion/template
@@ -1,13 +1,13 @@
 # Template file for 'freeorion'
 pkgname=freeorion
-version=0.4.9
+version=0.4.10
 revision=1
-_release=${version}_2020-02-02.db53471
+_release=${version}_2020-07-10.f3d403e
 wrksrc=src-tarball
 build_style=cmake
-hostmakedepends="cppcheck doxygen python-pycodestyle"
+hostmakedepends="cppcheck doxygen python3-pycodestyle"
 makedepends="boost-devel libvorbis-devel
- freetype-devel glew-devel libopenal-devel python-devel SDL2-devel"
+ freetype-devel glew-devel libopenal-devel python3-devel SDL2-devel"
 depends="${pkgname}-data desktop-file-utils hicolor-icon-theme"
 short_desc="Turn-based space empire and galactic conquest (4X) computer game"
 maintainer="Orphaned <orphan@voidlinux.org>"
@@ -15,7 +15,7 @@ license="GPL-2.0-or-later"
 homepage="https://freeorion.org/index.php/Main_Page"
 changelog="https://raw.githubusercontent.com/freeorion/freeorion/master/ChangeLog.md"
 distfiles="https://github.com/freeorion/freeorion/releases/download/v${version}/FreeOrion_v${_release}_Source.tar.gz"
-checksum=5689b3a6cab9e6cfbc83d8e82ef325bb9e00711262d26b046f083ea5fdc4d6e1
+checksum=e72ab42cba1ee8842507340931ef389e64011e040a4adc74add5f4997bbcba8b
 
 post_extract() {
 	_build_no=${_release/*_/}

             reply	other threads:[~2020-07-27 16:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 16:49 SolitudeSF [this message]
2020-10-02  5:52 ` SolitudeSF
2020-10-02  5:58 ` ericonr
2020-10-02  6:11 ` [PR PATCH] [Updated] " SolitudeSF
2020-10-02  6:12 ` SolitudeSF
2020-10-02  7:01 ` ericonr
2020-10-02  7:30 ` [PR PATCH] [Closed]: " ericonr
2020-10-02  7:31 ` ericonr

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-23873@inbox.vuxu.org \
    --to=solitudesf@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).