Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make compatible with CRAN again #2

Open
tretherington opened this issue Jun 7, 2021 · 0 comments
Open

Make compatible with CRAN again #2

tretherington opened this issue Jun 7, 2021 · 0 comments

Comments

@tretherington
Copy link
Member

I received the following email on 23/05/2021, but haven't been able to address as yet, so virtualNicheR is no longer available on CRAN, and would be good to fix this when a moment presents itself:

Dear maintainer,

Please see the problems shown on
https://cran.r-project.org/web/checks/check_results_virtualNicheR.html.

Specifically, please see the problems for the Debian-based checks for r-devel.

These are from

  \item \code{matrix(x, n, m)} now warns in more cases where
  \code{length(x)} differs from than \code{n * m}; suggested by Abby
  Spurdle and Wolfgang Huber in Feb 2021 on the R-devel mailing
  list.

  This warning can be turned into an error by setting environment
  variable \env{_R_CHECK_MATRIX_DATA_} to \samp{TRUE}: \command{R
    CMD check --as-cran} does so unless it is already set.

in current r-devel, where the Debian-based checks are now performed with R_CHECK_MATRIX_DATA=TRUE.

Please correct before 2021-06-05 to safely retain your package on CRAN.

Best,
-k

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant