Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] MultiMC: update to 0.6.7.
Date: Sat, 14 Sep 2019 23:10:02 +0200	[thread overview]
Message-ID: <20190914211002.4Yfcq2kjmYHetSaDznRriHIL4Hzt3PwSsKOaw-yUc5s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13900@inbox.vuxu.org>

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

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

https://github.com/pbui/void-packages MultiMC
https://github.com/void-linux/void-packages/pull/13900

MultiMC: update to 0.6.7.


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

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

From 2aae87b85edf3fdab54c609cbc50497c85b460fd Mon Sep 17 00:00:00 2001
From: Peter Bui <pbui@github.bx612.space>
Date: Fri, 23 Aug 2019 10:03:05 -0400
Subject: [PATCH] MultiMC: update to 0.6.7.

---
 srcpkgs/MultiMC/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/MultiMC/template b/srcpkgs/MultiMC/template
index 36e7b51497f..917cd3220d3 100644
--- a/srcpkgs/MultiMC/template
+++ b/srcpkgs/MultiMC/template
@@ -4,8 +4,8 @@ version=0.6.7
 revision=1
 wrksrc="${pkgname}5-${version}"
 _commithashnbt="4b305bbd2ac0e7a26987baf7949a484a87b474d4"
-_nbtversion="multimc-0.5.0"
-_quazipversion="multimc-2"
+_nbtversion="multimc-0.6.1"
+_quazipversion="multimc-3"
 build_style=cmake
 configure_args='-DMultiMC_BUILD_PLATFORM=Void -DMultiMC_LAYOUT=lin-system'
 hostmakedepends="openjdk xxd git"
@@ -19,8 +19,8 @@ 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
- bcefbdd905f10a04605cf9e8f768d0f60c972e9e219c800512a5fd9c5f7a8498
- 25e1b74f0edef5e09647f7b5344c08fad4eaebbc386b1f288b59286ecdfe07fa"
+ 36c816e6b1ef8ece52c57dfa9bfda3a23808d0c6c3288b25d8bcf49c7cdb5b07
+ ffa60368b1c196859691b637c740f4c60597b2ac47217995082ae8b2a3a9ac18"
 skip_extraction="${_nbtversion}.tar.gz ${_quazipversion}.tar.gz"
 
 pre_configure() {

  parent reply	other threads:[~2019-09-14 21:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13900@inbox.vuxu.org>
2019-09-14 21:10 ` voidlinux-github
2019-09-14 21:10 ` voidlinux-github [this message]
2019-10-02 19:49 ` voidlinux-github
2019-10-02 19:59 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-02 19:59 ` voidlinux-github
2019-10-02 20:00 ` voidlinux-github
2019-10-02 20:01 ` voidlinux-github
2019-10-02 20:16 ` [PR PATCH] [Merged]: " voidlinux-github

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=20190914211002.4Yfcq2kjmYHetSaDznRriHIL4Hzt3PwSsKOaw-yUc5s@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).