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

R-hub builder error: there is no package called 'rlang' #367

Closed
DivadNojnarg opened this issue Apr 30, 2020 · 4 comments
Closed

R-hub builder error: there is no package called 'rlang' #367

DivadNojnarg opened this issue Apr 30, 2020 · 4 comments

Comments

@DivadNojnarg
Copy link

While preparing for a CRAN update, I had an error with devtools::check_rhub():

* installing *source* package 'shinyMobile' ...
** using staged installation
** R
** inst
** byte-compile and prepare package for lazy loading
Error in loadNamespace(i, c(lib.loc, .libPaths()), versionCheck = vI[[i]]) : 
  there is no package called 'rlang'
Calls: <Anonymous> ... loadNamespace -> withRestarts -> withOneRestart -> doWithOneRestart
Execution halted
ERROR: lazy loading failed for package 'shinyMobile'
* removing 'C:/Users/USERlJFmSgyduQ/R/shinyMobile'

Full log here

and also this:

* using log directory ‘/home/docker/shinyMobile.Rcheck’
* using R version 3.6.1 (2019-07-05)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--as-cran’
* checking for file ‘shinyMobile/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘shinyMobile’ version ‘0.7.0’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... Note_to_CRAN_maintainers
Maintainer: ‘David Granjon <dgranjon@ymail.com>’
* checking package namespace information ... OK
* checking package dependencies ... ERROR
Packages suggested but not available: 'plotly', 'V8', 'golem'

The suggested packages are required for a complete check.
Checking can be attempted without them by setting the environment
variable _R_CHECK_FORCE_SUGGESTS_ to a false value.

See section ‘The DESCRIPTION file’ in the ‘Writing R Extensions’
manual.
* DONE
Status: 1 ERROR

Full log here

devtools::check_win_devel() as well as local checking are OK.

Session info

R version 3.4.4 (2018-03-15)
Platform: x86_64-apple-darwin15.6.0 (64-bit)
Running under: macOS  10.15.3

Matrix products: default
BLAS: /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/3.4/Resources/lib/libRlapack.dylib

locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base     

other attached packages:
[1] devtools_2.3.0 usethis_1.6.1 

loaded via a namespace (and not attached):
 [1] rstudioapi_0.11   magrittr_1.5      pkgload_1.0.2    
 [4] R6_2.4.1          rlang_0.4.5       fansi_0.4.1      
 [7] tools_3.4.4       pkgbuild_1.0.7    sessioninfo_1.1.1
[10] cli_2.0.2         withr_2.2.0       ellipsis_0.3.0   
[13] remotes_2.1.1     assertthat_0.2.1  digest_0.6.25    
[16] rprojroot_1.3-2   crayon_1.3.4      processx_3.4.2   
[19] callr_3.4.3       fs_1.4.1          ps_1.3.2         
[22] testthat_2.3.2    memoise_1.1.0     glue_1.4.0       
[25] compiler_3.4.4    desc_1.2.0        backports_1.1.6  
[28] prettyunits_1.1.1 jsonlite_1.6.1   
@gaborcsardi
Copy link
Collaborator

The full log is under the link named "log": https://builder.r-hub.io/status/original/shinyMobile_0.7.0.tar.gz-419e621e79b945cc9473a4217ba9202d

This is the error, slightly garbled:

Packages which are only available in source form, and may need
  These will not be installed
  'dplyr' 'purrr' 'tidyr' 'data.table'
  'tibble' 'ellipsis' 'fansi' 'vctrs' 'utf8' 'processx' 'ps' 'curl'
  compilation of C/C++/Fortran: 'Rcpp' 'rlang' 'glue' 'stringi'

CRAN does not currently distribute binaries for R-devel packages, e.g.: https://cran.r-project.org/web/packages/rlang/index.html

They only have binaries for internal use.

@gaborcsardi
Copy link
Collaborator

A possible workaround is to set the R_COMPILE_AND_INSTALL_PACKAGES env var to always, using the env_vars argument.

@gaborcsardi
Copy link
Collaborator

I just tried and this works for a package with a bunch of dependencies that need compilation:

rhub::check(
  platform="windows-x86_64-devel",
  env_vars=c(R_COMPILE_AND_INSTALL_PACKAGES = "always")
)

@DivadNojnarg
Copy link
Author

Perfect! Thanks

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

2 participants