From: jnbr <jnbr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: R: update to 4.0.2.
Date: Sat, 15 Aug 2020 16:47:44 +0200 [thread overview]
Message-ID: <20200815144744.DPAusQGfqQoRScdpFF9ND9Lwo-fSZMSHZ_hNFhXqjl4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24126@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2502 bytes --]
There's a closed pull request on the void-packages repository
R: update to 4.0.2.
https://github.com/void-linux/void-packages/pull/24126
Description:
This is a major version update to R with some breaking changes for older R packages/scripts. Although the problems with most CRAN packages should be resolved as CRAN gave package authors a deadline to submit fixes. I've been using R 4.0 for a couple of months now and not experienced any problems.
## Breaking Changes
- Packages need to be (re-)installed under this version (4.0.2) of R.
- R now uses a stringsAsFactors = FALSE default, and hence by default no longer converts strings to factors in calls to data.frame() and read.table(). A large number of packages relied on the previous behaviour and so have needed/will need updating.
## Build Changes
- This version of R is built against the PCRE2 library for Perl-like regular expressions, if available.
- Enable memory profiling by building with --enable-memory-profiling flag, this is the default on all binaries provided by upstream, and several other distros.
## Dependencies to Build and Check
Some R-cran-* packages failed xlint, so I've changed those where appropriate.
- [x] R-cran-R6
- [x] R-cran-RColorBrewer
- [x] R-cran-Rcpp
- [x] R-cran-assertthat
- [x] R-cran-backports
- [x] R-cran-callr
- [x] R-cran-cli
- [x] R-cran-colorspace
- [x] R-cran-crayon
- [x] R-cran-data.table
- [x] R-cran-desc
- [x] R-cran-dichromat
- [x] R-cran-digest
- [x] R-cran-ellipsis
- [x] R-cran-evaluate
- [x] R-cran-fansi
- [x] R-cran-farver
- [x] R-cran-generics
- [x] R-cran-ggplot2
- [x] R-cran-glue
- [x] R-cran-gsubfn
- [x] R-cran-gtable
- [x] R-cran-isoband
- [x] R-cran-labeling
- [x] R-cran-lazyeval
- [x] R-cran-lifecycle
- [x] R-cran-lubridate
- [x] R-cran-magrittr
- [x] R-cran-munsell
- [x] R-cran-nloptr
- [x] R-cran-pillar
- [x] R-cran-pkgbuild
- [x] R-cran-pkgconfig
- [x] R-cran-pkgload
- [x] R-cran-plyr
- [x] R-cran-praise
- [x] R-cran-prettyunits
- [x] R-cran-processx
- [x] R-cran-proto
- [x] R-cran-ps
- [x] R-cran-reshape2
- [x] R-cran-rlang
- [x] R-cran-rprojroot
- [x] R-cran-rstudioapi
- [x] R-cran-scales
- [x] R-cran-stringi
- [x] R-cran-stringr
- [x] R-cran-testthat
- [x] R-cran-tibble
- [x] R-cran-utf8
- [x] R-cran-vctrs
- [x] R-cran-viridisLite
- [x] R-cran-withr
- [x] R-cran-zeallot
- [x] R-cran-zoo
- [x] emacs-ess
- [x] rstudio (this takes a while to build, will probably be a separate PR)
prev parent reply other threads:[~2020-08-15 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 10:40 [PR PATCH] [WIP] " luhann
2020-08-07 12:24 ` [PR PATCH] [Updated] " luhann
2020-08-07 13:30 ` luhann
2020-08-07 16:15 ` luhann
2020-08-07 21:56 ` luhann
2020-08-09 12:34 ` luhann
2020-08-12 10:22 ` [PR PATCH] [Updated] " luhann
2020-08-14 20:14 ` jnbr
2020-08-14 21:19 ` [PR PATCH] [Updated] " luhann
2020-08-14 21:19 ` luhann
2020-08-15 14:47 ` jnbr
2020-08-15 14:47 ` jnbr [this message]
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=20200815144744.DPAusQGfqQoRScdpFF9ND9Lwo-fSZMSHZ_hNFhXqjl4@z \
--to=jnbr@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).