From: luhann <luhann@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: R: update to 4.1.0.
Date: Fri, 11 Jun 2021 16:20:02 +0200 [thread overview]
Message-ID: <20210611142002.stZxamQVPh9HMqNyTGHkqdeA3RCOoYKjp1EXeu-2mQQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31398@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
New comment by luhann on void-packages repository
https://github.com/void-linux/void-packages/pull/31398#issuecomment-859615860
Comment:
I haven't tested all of the system `R-cran` packages, but the ones I did test (`data.table`, `ggplot2`, `lifecycle`, `dplyr`) worked without issue. All of the packages in my user library were built with R 4.0.3 and I haven't had any issues.
Rstudio says "In general, there are no issues with subminor version upgrades, like going from 3.3.2 to 3.3.3, **but there can be** compatibility problems when there is a major or minor version upgrade." Looking at the commit history it doesn't look like void has rebuilt all cran packages on minor version upgrades.
So everything should work but it is possible that something breaks, to save resources we could just rebuild the packages that break should anything break.
next prev parent reply other threads:[~2021-06-11 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 13:45 [PR PATCH] " luhann
2021-06-10 17:30 ` ericonr
2021-06-11 14:20 ` luhann [this message]
2021-06-11 14:44 ` ericonr
2021-06-11 14:45 ` ericonr
2021-06-11 18:20 ` ericonr
2021-06-11 20:47 ` luhann
2021-06-11 21:05 ` [PR PATCH] [Updated] " luhann
2021-06-12 1:43 ` [PR PATCH] [Merged]: " ericonr
2021-07-06 10:21 ` wagnerflo
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=20210611142002.stZxamQVPh9HMqNyTGHkqdeA3RCOoYKjp1EXeu-2mQQ@z \
--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).