Github messages for voidlinux
 help / color / mirror / Atom feed
From: luhann <luhann@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] R: update to 4.1.3.
Date: Sat, 12 Mar 2022 02:35:40 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36104@inbox.vuxu.org> (raw)

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

There is a new pull request by luhann against master on the void-packages repository

https://github.com/luhann/void-packages R
https://github.com/void-linux/void-packages/pull/36104

R: update to 4.1.3.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->

#### Local build testing
- I built this PR locally for my native architecture, (x86_64)

Minor version update with no changes to build process and some minor bugfixes.



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

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

From 2eb9131f630774da89d1b40d3844861c1ba0f429 Mon Sep 17 00:00:00 2001
From: Luke Hannan <luke@lukehannan.com>
Date: Fri, 11 Mar 2022 23:17:55 +0200
Subject: [PATCH] R: update to 4.1.3.

---
 srcpkgs/R/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/R/template b/srcpkgs/R/template
index 8190ac146535..d506d02764b0 100644
--- a/srcpkgs/R/template
+++ b/srcpkgs/R/template
@@ -1,7 +1,7 @@
 # Template file for 'R'
 pkgname=R
-version=4.1.2
-revision=2
+version=4.1.3
+revision=1
 build_style=gnu-configure
 configure_args="--docdir=/usr/share/doc/R rdocdir=/usr/share/doc/R
  --with-blas$(vopt_if openblas '=openblas') --with-lapack
@@ -22,7 +22,7 @@ license="GPL-2.0-or-later"
 homepage="https://www.r-project.org/"
 changelog="https://cran.r-project.org/doc/manuals/r-release/NEWS.html"
 distfiles="https://cran.r-project.org/src/base/R-4/${pkgname}-${version}.tar.gz"
-checksum=2036225e9f7207d4ce097e54972aecdaa8b40d7d9911cd26491fac5a0fab38af
+checksum=15ff5b333c61094060b2a52e9c1d8ec55cc42dd029e39ca22abdaa909526fed6
 nocross=yes
 shlib_provides="libR.so"
 make_check=extended

             reply	other threads:[~2022-03-12  1:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-12  1:35 luhann [this message]
2022-03-13  5:34 ` CameronNemo
2022-03-13 10:05 ` [PR PATCH] [Merged]: " paper42

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-36104@inbox.vuxu.org \
    --to=luhann@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).