CRAN Package Check Results for Package RApiDatetime

Last updated on 2025-12-20 17:50:38 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.0.9 3.55 19.68 23.23 NOTE
r-devel-linux-x86_64-debian-gcc 0.0.9 2.71 16.13 18.84 NOTE
r-devel-linux-x86_64-fedora-clang 0.0.9 6.00 28.97 34.97 NOTE
r-devel-linux-x86_64-fedora-gcc 0.0.9 35.12 NOTE
r-patched-linux-x86_64 0.0.9 3.75 17.23 20.98 OK
r-release-linux-x86_64 0.0.9 3.73 17.23 20.96 OK
r-release-macos-arm64 0.0.9 OK
r-release-macos-x86_64 0.0.9 3.00 27.00 30.00 OK
r-oldrel-macos-arm64 0.0.9 OK
r-oldrel-macos-x86_64 0.0.9 3.00 19.00 22.00 OK
r-oldrel-windows-x86_64 0.0.8 8.00 39.00 47.00 NOTE

Check Details

Version: 0.0.9
Check: CRAN incoming feasibility
Result: NOTE Maintainer: ‘Dirk Eddelbuettel <edd@debian.org>’ No Authors@R field in DESCRIPTION. Please add one, modifying Authors@R: person(given = "Dirk", family = "Eddelbuettel", role = c("aut", "cre"), email = "edd@debian.org") as necessary. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc

Version: 0.0.9
Check: compiled code
Result: NOTE File ‘RApiDatetime/libs/RApiDatetime.so’: Found non-API calls to R: ‘ATTRIB’, ‘SET_ATTRIB’ 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: Rd contents
Result: NOTE Auto-generated content requiring editing in Rd file 'RApiDatetime-package.Rd': \references: 'This optional section can contain literature or other refere...' \seealso: 'Optional links to other man pages' \examples: '# Optional simple examples of the most important functions' Flavor: r-oldrel-windows-x86_64