CRAN Package Check Results for Maintainer ‘Lionel Henry <lionel at rstudio.com>’

Last updated on 2024-11-21 19:53:12 CET.

Package NOTE OK
fontLiberation 8 5
fontquiver 8 5
ggstance 13
magrittr 5 8
purrrlyr 13

Package fontLiberation

Current CRAN status: NOTE: 8, OK: 5

Version: 0.1.0
Check: LazyData
Result: NOTE 'LazyData' is specified without a 'data' directory Flavors: r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64

Version: 0.1.0
Check: installed package size
Result: NOTE installed size is 6.2Mb sub-directories of 1Mb or more: fonts 6.1Mb Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64

Package fontquiver

Current CRAN status: NOTE: 8, OK: 5

Version: 0.2.1
Check: LazyData
Result: NOTE 'LazyData' is specified without a 'data' directory Flavors: r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64

Package ggstance

Current CRAN status: OK: 13

Package magrittr

Current CRAN status: NOTE: 5, OK: 8

Version: 2.0.3
Check: compiled code
Result: NOTE File ‘magrittr/libs/magrittr.so’: Found non-API calls to R: ‘Rf_findVarInFrame3’, ‘SET_ENCLOS’, ‘SET_PRCODE’, ‘SET_PRENV’, ‘SET_PRVALUE’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 2.0.3
Check: compiled code
Result: NOTE File 'magrittr/libs/x64/magrittr.dll': Found non-API calls to R: 'Rf_findVarInFrame3', 'SET_ENCLOS', 'SET_PRCODE', 'SET_PRENV', 'SET_PRVALUE' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-devel-windows-x86_64

Package purrrlyr

Current CRAN status: NOTE: 13

Version: 0.0.8
Check: C++ specification
Result: NOTE Specified C++11: please drop specification unless essential Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64

Version: 0.0.8
Check: Rd cross-references
Result: NOTE Found the following Rd file(s) with Rd \link{} targets missing package anchors: by_row.Rd: invoke, lift Please provide package anchors for all Rd \link{} targets not in the package itself and the base packages. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64

Version: 0.0.8
Check: compiled code
Result: NOTE File ‘purrrlyr/libs/purrrlyr.so’: Found non-API call to R: ‘STRING_PTR’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 0.0.8
Check: compiled code
Result: NOTE File 'purrrlyr/libs/x64/purrrlyr.dll': Found non-API call to R: 'STRING_PTR' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-devel-windows-x86_64

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.