Dear community, I've been trying to submit an update to my GPvecchia package recently. This morning I was notified that my package didn't pass incoming checks. When I looked at the log this was the problem: * checking package dependencies ... ERROR Packages required but not available: 'sparseinv', 'GpGp'* checking package dependencies ... ERROR Packages required but not available: 'sparseinv', 'GpGp' Like my package, these have been on CRAN for a while now and still seem to be. However they both report an error in their respective CRAN checks, but it's a weird one. This is taken from GpGp checks but it's similar for sparseinv: Result: ERROR Packages required but not available: 'Rcpp', 'FNN', 'RcppArmadillo' Packages suggested but not available for checking: 'fields', 'rmarkdown', 'testthat', 'maptools' See section ?The DESCRIPTION file? in the ?Writing R Extensions? I'm not sure how to proceed. I know the maintainer of the GpGp package but I'm not sure what to alert him to if Rcpp does not work. I really appreciate your help. Marcin
[R-pkg-devel] failing CRAN checks due to problems with dependencies
4 messages · Marcin Jurek, Ivan Krylov, Dirk Eddelbuettel
1 day later
? Wed, 7 Feb 2024 08:40:44 -0600 Marcin Jurek <marcinjurek1988 at gmail.com> ?????:
Packages required but not available: 'Rcpp', 'FNN', 'RcppArmadillo' Packages suggested but not available for checking: 'fields', 'rmarkdown', 'testthat', 'maptools'
One of the machines running the incoming checks was having problems. If you followed the failing dependency chain by looking at the CRAN check results of the packages described as "not available", you could eventually find a package needing compilation (Rcpp or stringi or something else), look at the installation log and see Make trying to run commands that are completely wrong. It looked like the path to the compiler was empty: https://web.archive.org/web/20240208191430/https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-clang/Rcpp-00install.html I think that the problems are solved now, so it should be safe to increment the version and submit it again.
Best regards, Ivan
Ok, this makes sense! I saw that Rcpp was failing the checks too but I wasn't sure if I should resubmit or wait. Thanks!
On Thu, Feb 8, 2024 at 1:17?PM Ivan Krylov <ikrylov at disroot.org> wrote:
? Wed, 7 Feb 2024 08:40:44 -0600 Marcin Jurek <marcinjurek1988 at gmail.com> ?????:
Packages required but not available: 'Rcpp', 'FNN', 'RcppArmadillo' Packages suggested but not available for checking: 'fields', 'rmarkdown', 'testthat', 'maptools'
One of the machines running the incoming checks was having problems. If you followed the failing dependency chain by looking at the CRAN check results of the packages described as "not available", you could eventually find a package needing compilation (Rcpp or stringi or something else), look at the installation log and see Make trying to run commands that are completely wrong. It looked like the path to the compiler was empty: https://web.archive.org/web/20240208191430/https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-clang/Rcpp-00install.html I think that the problems are solved now, so it should be safe to increment the version and submit it again. -- Best regards, Ivan
On 8 February 2024 at 13:28, Marcin Jurek wrote:
| Ok, this makes sense! I saw that Rcpp was failing the checks too but I | wasn't sure if I should resubmit or wait. Thanks! For completeness, it was not caused by Rcpp but rather by a mix on new clang and gcc versions which somehow got into each other's way on that machine; and this has by now been fixed. Dirk
dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org