From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] DO NOT MERGE: rebar3: update to 3.11.0.
Date: Fri, 31 May 2019 23:35:59 +0200 [thread overview]
Message-ID: <20190531213559.VUDbD6kM429GLm-FUE1WoTyaQl5bENFm7dtP_ztKyxA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12059@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
There is an updated pull request by nilium against master on the void-packages repository
https://github.com/nilium/ecks-bops-packages rebar3
https://github.com/void-linux/void-packages/pull/12059
DO NOT MERGE: rebar3: update to 3.11.0.
Requires erlang>=22 now -- installing this while someone has a hold on
erlang for an older version will break rebar3.
A patch file from https://github.com/void-linux/void-packages/pull/12059.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rebar3-12059.patch --]
[-- Type: application/text/x-diff, Size: 1220 bytes --]
From 6c03d394d5ab06eaea9d1cf7c7e855660c4b3902 Mon Sep 17 00:00:00 2001
From: Noel Cower <ncower@gmail.com>
Date: Fri, 31 May 2019 10:12:17 -0700
Subject: [PATCH] rebar3: update to 3.11.0.
Requires erlang>=22 now -- without this, if someone installs rebar3
while erlang is held on an earlier release, this breaks rebar3 (because
no forward compatibility).
---
srcpkgs/rebar3/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/rebar3/template b/srcpkgs/rebar3/template
index b8e2061dc71..63702394812 100644
--- a/srcpkgs/rebar3/template
+++ b/srcpkgs/rebar3/template
@@ -1,16 +1,16 @@
# Template file for 'rebar3'
pkgname=rebar3
-version=3.10.0
+version=3.11.0
revision=1
archs=noarch
hostmakedepends=erlang
-depends=erlang
+depends="erlang>=22"
short_desc="Erlang build tool to compile, test, and release applications"
maintainer="Noel Cower <ncower@gmail.com>"
license="Apache-2.0"
homepage="https://www.rebar3.org/"
distfiles="https://github.com/erlang/rebar3/archive/${version}.tar.gz"
-checksum=656b4a0bd75f340173e67a33c92e4d422b5ccf054f93ba35a9d780b545ee827e
+checksum=d0f567bf5cfd60e16650b151a7caa24bf8164fb1c31359ce8b0452a683209421
do_build() {
./bootstrap
next prev parent reply other threads:[~2019-05-31 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 17:13 [PR PATCH] " voidlinux-github
2019-05-31 19:13 ` DO NOT MERGE: " voidlinux-github
2019-05-31 21:33 ` [PR PATCH] [Updated] " voidlinux-github
2019-05-31 21:33 ` voidlinux-github
2019-05-31 21:35 ` voidlinux-github
2019-05-31 21:35 ` voidlinux-github
2019-05-31 21:35 ` voidlinux-github
2019-05-31 21:35 ` voidlinux-github [this message]
2019-06-01 7:10 ` [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=20190531213559.VUDbD6kM429GLm-FUE1WoTyaQl5bENFm7dtP_ztKyxA@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).