Github messages for voidlinux
 help / color / mirror / Atom feed
From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] supertux2: update to 0.6.2.
Date: Mon, 18 May 2020 16:55:44 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22085@inbox.vuxu.org> (raw)

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

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

https://github.com/abenson/void-packages st2_0.6.2
https://github.com/void-linux/void-packages/pull/22085

supertux2: update to 0.6.2.


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

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

From 3f773b3ea401ed70abba9f554850321253aff396 Mon Sep 17 00:00:00 2001
From: Andrew Benson <abenson+void@gmail.com>
Date: Mon, 18 May 2020 09:52:53 -0500
Subject: [PATCH] supertux2: update to 0.6.2.

---
 srcpkgs/supertux2/patches/endian.patch | 19 -------------------
 srcpkgs/supertux2/template             |  4 ++--
 2 files changed, 2 insertions(+), 21 deletions(-)
 delete mode 100644 srcpkgs/supertux2/patches/endian.patch

diff --git a/srcpkgs/supertux2/patches/endian.patch b/srcpkgs/supertux2/patches/endian.patch
deleted file mode 100644
index 93d6ed3d95b..00000000000
--- a/srcpkgs/supertux2/patches/endian.patch
+++ /dev/null
@@ -1,19 +0,0 @@
-commit ab3daa606e215f43aa3077daad82cd2d55c38908
-Author: q66 <daniel@octaforge.org>
-Date:   Mon Jan 6 03:02:59 2020 +0100
-
-    Fix build on big endian
-
-diff --git src/audio/wav_sound_file.cpp src/audio/wav_sound_file.cpp
-index c4036b1..e056f50 100644
---- src/audio/wav_sound_file.cpp
-+++ src/audio/wav_sound_file.cpp
-@@ -150,7 +150,7 @@ WavSoundFile::read(void* buffer, size_t buffer_size)
-     throw SoundError("read error while reading samples");
- 
- #ifdef WORDS_BIGENDIAN
--  if (bits_per_sample != 16)
-+  if (m_bits_per_sample != 16)
-     return readsize;
-   char *tmp = (char*)buffer;
- 
diff --git a/srcpkgs/supertux2/template b/srcpkgs/supertux2/template
index b58e7f27e68..4b7053c6b95 100644
--- a/srcpkgs/supertux2/template
+++ b/srcpkgs/supertux2/template
@@ -1,6 +1,6 @@
 # Template file for 'supertux2'
 pkgname=supertux2
-version=0.6.1.1
+version=0.6.2
 revision=1
 wrksrc="SuperTux-v${version}-Source"
 build_style=cmake
@@ -18,7 +18,7 @@ maintainer="beefcurtains <beefcurtains@voidlinux.org>"
 license="GPL-3.0-or-later, GPL-2.0-or-later, CC-BY-SA-3.0, CC-BY-SA-4.0, CC-BY-3.0"
 homepage="https://supertux.github.io/"
 distfiles="https://github.com/SuperTux/supertux/releases/download/v${version}/SuperTux-v${version}-Source.tar.gz"
-checksum=2e8df0637b6e17534f7d7c2bd9b4f0f99aaf92389afc1abb9eb44d2a79c76658
+checksum=26a9e56ea2d284148849f3239177d777dda5b675a10ab2d76ee65854c91ff598
 
 supertux2-data_package() {
 	short_desc+=" - data files"

             reply	other threads:[~2020-05-18 14:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18 14:55 abenson [this message]
2020-05-18 15:32 ` [PR PATCH] [Merged]: " abenson

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