From: rc-05 <rc-05@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] nim: update to 1.4.0.
Date: Sat, 17 Oct 2020 11:48:59 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25676@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 298 bytes --]
There is a new pull request by rc-05 against master on the void-packages repository
https://github.com/rc-05/void-packages nim
https://github.com/void-linux/void-packages/pull/25676
nim: update to 1.4.0.
A patch file from https://github.com/void-linux/void-packages/pull/25676.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-nim-25676.patch --]
[-- Type: text/x-diff, Size: 1408 bytes --]
From 9cb571a3fdcd62087c296d934ccf3fb47d09c89f Mon Sep 17 00:00:00 2001
From: rc-05 <rc23@email.it>
Date: Sat, 17 Oct 2020 11:40:56 +0200
Subject: [PATCH] nim: update to 1.4.0.
---
srcpkgs/nim/template | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/nim/template b/srcpkgs/nim/template
index 56ac1dba6eb..672b6c67d80 100644
--- a/srcpkgs/nim/template
+++ b/srcpkgs/nim/template
@@ -1,9 +1,9 @@
# Template file for 'nim'
pkgname=nim
-version=1.2.6
-revision=2
+version=1.4.0
+revision=1
_cversion=0.20.0
-_nimbleversion=0.11.4
+_nimbleversion=0.12.0
create_wrksrc=yes
build_wrksrc="Nim-$version"
hostmakedepends="ed"
@@ -15,9 +15,9 @@ homepage="https://nim-lang.org/"
distfiles="https://github.com/nim-lang/Nim/archive/v${version}.tar.gz
https://github.com/nim-lang/csources/archive/v${_cversion}.tar.gz>csources-${_cversion}.tar.gz
https://github.com/nim-lang/nimble/archive/v${_nimbleversion}.tar.gz>nimble-${_nimbleversion}.tar.gz"
-checksum="dbd5f1784ab121071aa7c58bb6b361cca79d12ac7524c761e27200e0c946e359
+checksum="3918ff1834888cd3feec5002931d4052a354994a0355bf1ae950f2f17ba81417
5e6fd15d90df1a8cb7614c4ffc70aa8c4198cd854d7742016202b96dd0228d3c
- 63e0dbfa5c33f80d6f8f8156a609e11497ac5390b64dc8d68f5126c3bb8d5429"
+ 0b88d91a450f31641f85379f2d76afb0a013cf783e62144a6534525b9cb1cbac"
post_extract() {
mv csources-$_cversion $build_wrksrc/csources
next reply other threads:[~2020-10-17 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 9:48 rc-05 [this message]
2020-10-17 13:02 ` [PR PATCH] [Updated] " rc-05
2020-10-17 13:46 ` rc-05
2020-12-02 17:57 ` [PR REVIEW] " ericonr
2020-12-06 14:56 ` rc-05
2020-12-06 15:25 ` rc-05
2020-12-20 4:37 ` ahesford
2020-12-20 4:37 ` [PR PATCH] [Closed]: " ahesford
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-25676@inbox.vuxu.org \
--to=rc-05@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).