CRAN Package Check Results for Package tibble

Last updated on 2024-12-23 19:50:23 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 3.2.1 7.72 155.49 163.21 NOTE
r-devel-linux-x86_64-debian-gcc 3.2.1 4.78 107.84 112.62 NOTE
r-devel-linux-x86_64-fedora-clang 3.2.1 278.56 NOTE
r-devel-linux-x86_64-fedora-gcc 3.2.1 267.57 NOTE
r-devel-windows-x86_64 3.2.1 12.00 157.00 169.00 NOTE
r-patched-linux-x86_64 3.2.1 11.03 143.50 154.53 OK
r-release-linux-x86_64 3.2.1 6.95 144.23 151.18 OK
r-release-macos-arm64 3.2.1 74.00 OK
r-release-macos-x86_64 3.2.1 120.00 OK
r-release-windows-x86_64 3.2.1 11.00 145.00 156.00 OK
r-oldrel-macos-arm64 3.2.1 84.00 OK
r-oldrel-macos-x86_64 3.2.1 151.00 OK
r-oldrel-windows-x86_64 3.2.1 13.00 184.00 197.00 OK

Check Details

Version: 3.2.1
Check: Rd cross-references
Result: NOTE Found the following Rd file(s) with Rd \link{} targets missing package anchors: deprecated.Rd: quasiquotation formatting.Rd: tbl_format_setup frame_matrix.Rd: !!, !!!, quasiquotation lst.Rd: !!, !!!, .data, .env subsetting.Rd: vec_slice tibble.Rd: !!, !!!, .data, .env, quasiquotation tribble.Rd: !!, !!!, quasiquotation 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: 3.2.1
Check: compiled code
Result: NOTE File ‘tibble/libs/tibble.so’: Found non-API call to R: ‘SET_S4_OBJECT’ 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: 3.2.1
Check: compiled code
Result: NOTE File 'tibble/libs/x64/tibble.dll': Found non-API call to R: 'SET_S4_OBJECT' 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