From: EliteTK <EliteTK@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] nim: update to 1.6.6
Date: Wed, 15 Jun 2022 03:31:23 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37567@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
There is a new pull request by EliteTK against master on the void-packages repository
https://github.com/EliteTK/void-packages nim-1.6.6
https://github.com/void-linux/void-packages/pull/37567
nim: update to 1.6.6
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/37567.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-nim-1.6.6-37567.patch --]
[-- Type: text/x-diff, Size: 1177 bytes --]
From 966f127dfe72c2a44ec8b78a8f945fbc80e12733 Mon Sep 17 00:00:00 2001
From: Tomasz Kramkowski <tomasz@kramkow.ski>
Date: Wed, 15 Jun 2022 01:58:49 +0100
Subject: [PATCH] nim: update to 1.6.6.
---
srcpkgs/nim/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/nim/template b/srcpkgs/nim/template
index d7534c97c223..60d344616c11 100644
--- a/srcpkgs/nim/template
+++ b/srcpkgs/nim/template
@@ -1,6 +1,6 @@
# Template file for 'nim'
pkgname=nim
-version=1.6.0
+version=1.6.6
revision=1
_c1version=561b417c65791cd8356b5f73620914ceff845d10
_nimbleversion=0.13.1
@@ -15,7 +15,7 @@ _ghsite="https://github.com/nim-lang"
distfiles="${_ghsite}/Nim/archive/v${version}.tar.gz
${_ghsite}/csources_v1/archive/${_c1version}.tar.gz>csources_v1-${_c1version}.tar.gz
${_ghsite}/nimble/archive/v${_nimbleversion}.tar.gz>nimble-${_nimbleversion}.tar.gz"
-checksum="c202cfd24a24480da1cf851e1265b87edb22710bb42286a57b1a99c83b6a8315
+checksum="59836a85c1291b59af699a121b0b765703d6a0e44ed9f3ede363ff2b3e09d527
71c823444c794a12da9027d19d6a717dd7759521ecbbe28190b08372142607ec
e6aa8d9ee4b3ed0321dca329b4a38fa546771b9729984482fb50fe73d3777f5d"
next reply other threads:[~2022-06-15 1:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 1:31 EliteTK [this message]
2022-06-28 18:32 ` [PR REVIEW] " classabbyamp
2022-06-30 11:29 ` [PR PATCH] [Closed]: " Duncaen
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-37567@inbox.vuxu.org \
--to=elitetk@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).