CRAN Package Check Results for Package Rnmr1D

Last updated on 2026-04-14 04:51:37 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.3.2 34.63 151.00 185.63 OK
r-devel-linux-x86_64-debian-gcc 1.3.2 24.36 105.91 130.27 OK
r-devel-linux-x86_64-fedora-clang 1.3.2 51.00 245.88 296.88 NOTE
r-devel-linux-x86_64-fedora-gcc 1.3.2 58.00 236.71 294.71 NOTE
r-devel-macos-arm64 1.3.2 7.00 51.00 58.00 OK
r-devel-windows-x86_64 1.3.2 38.00 197.00 235.00 OK
r-patched-linux-x86_64 1.3.2 26.80 142.73 169.53 NOTE
r-release-linux-x86_64 1.3.2 27.03 138.43 165.46 OK
r-release-macos-arm64 1.3.2 OK
r-release-macos-x86_64 1.3.2 18.00 165.00 183.00 OK
r-release-windows-x86_64 1.3.2 35.00 0.00 35.00 OK
r-oldrel-macos-arm64 1.3.2 OK
r-oldrel-macos-x86_64 1.3.2 21.00 206.00 227.00 OK
r-oldrel-windows-x86_64 1.3.2 44.00 267.00 311.00 OK

Check Details

Version: 1.3.2
Check: dependencies in R code
Result: NOTE Namespace in Imports field not imported from: ‘impute’ All declared Imports should be used. Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 1.3.2
Check: compiled code
Result: NOTE File ‘Rnmr1D/libs/Rnmr1D.so’: Found non-API call to R: ‘R_UnboundValue’ 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-patched-linux-x86_64