Github messages for voidlinux
 help / color / mirror / Atom feed
From: SevereOverfl0w <SevereOverfl0w@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] MultiMC: update to 0.6.11.
Date: Thu, 21 May 2020 10:53:58 +0200	[thread overview]
Message-ID: <20200521085358.-3-KOIhPrOwl7VtHFSqZiLhnHe4e-NocJjuPsoL-WnI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22015@inbox.vuxu.org>

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

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

https://github.com/SevereOverfl0w/void-packages sev/multimc
https://github.com/void-linux/void-packages/pull/22015

MultiMC: update to 0.6.11.
None

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

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

From 84ba246ea561582c896355fa9943ba8cd18d71fd Mon Sep 17 00:00:00 2001
From: Dominic Monroe <iam@dominic.io>
Date: Sat, 16 May 2020 15:32:34 +0100
Subject: [PATCH] MultiMC: update to 0.6.11.

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

diff --git a/srcpkgs/MultiMC/template b/srcpkgs/MultiMC/template
index eb4a23dd42f..6df1ad68516 100644
--- a/srcpkgs/MultiMC/template
+++ b/srcpkgs/MultiMC/template
@@ -1,7 +1,7 @@
 # Template file for 'MultiMC'
 pkgname=MultiMC
-version=0.6.7
-revision=2
+version=0.6.11
+revision=1
 wrksrc="${pkgname}5-${version}"
 _commithashnbt="4b305bbd2ac0e7a26987baf7949a484a87b474d4"
 _nbtversion="multimc-0.6.1"
@@ -18,13 +18,13 @@ homepage="http://multimc.org"
 distfiles="https://github.com/${pkgname}/${pkgname}5/archive/${version}.tar.gz
  https://github.com/${pkgname}/libnbtplusplus/archive/${_nbtversion}.tar.gz
  https://github.com/${pkgname}/quazip/archive/${_quazipversion}.tar.gz"
-checksum="3ec38a5f622048ba3926f0e20fb296d646c7848f8313143062b3e2bd273149ae
+checksum="7cad736f1fe3f2887aeaa7a7f3927930e16ed815c98e4cf3a7378a99c426a775
  36c816e6b1ef8ece52c57dfa9bfda3a23808d0c6c3288b25d8bcf49c7cdb5b07
  ffa60368b1c196859691b637c740f4c60597b2ac47217995082ae8b2a3a9ac18"
 skip_extraction="${_nbtversion}.tar.gz ${_quazipversion}.tar.gz"
 
-case $XBPS_TARGET_ARCH in
-	armv*) broken="https://build.voidlinux.org/builders/armv7l-musl_builder/builds/22077/steps/shell_3/logs/stdio";;
+case "$XBPS_TARGET_MACHINE" in
+	armv*) broken="https://build.voidlinux.org/builders/armv7l-musl_builder/builds/22077/steps/shell_3/logs/stdio\n GitHub issue: https://github.com/MultiMC/MultiMC5/issues/2895";;
 esac
 
 pre_configure() {

  parent reply	other threads:[~2020-05-21  8:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 14:33 [PR PATCH] " SevereOverfl0w
2020-05-21  0:05 ` fosslinux
2020-05-21  0:05 ` fosslinux
2020-05-21  0:05 ` fosslinux
2020-05-21  8:11 ` SevereOverfl0w
2020-05-21  8:53 ` SevereOverfl0w [this message]
2020-05-21  8:54 ` SevereOverfl0w
2020-05-21  9:52 ` fosslinux
2020-05-21 12:56 ` q66
2020-05-21 14:02 ` SevereOverfl0w
2020-05-21 14:10 ` q66
2020-05-21 16:18 ` [PR PATCH] [Updated] " SevereOverfl0w
2020-05-21 19:06 ` SevereOverfl0w
2020-05-21 20:28 ` [PR PATCH] [Merged]: " q66

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=20200521085358.-3-KOIhPrOwl7VtHFSqZiLhnHe4e-NocJjuPsoL-WnI@z \
    --to=severeoverfl0w@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).