CRAN Package Check Results for Package colordistance

Last updated on 2025-05-22 03:50:32 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.1.2 3.55 119.17 122.72 NOTE
r-devel-linux-x86_64-debian-gcc 1.1.2 2.56 87.51 90.07 NOTE
r-devel-linux-x86_64-fedora-clang 1.1.2 182.78 NOTE
r-devel-linux-x86_64-fedora-gcc 1.1.2 197.73 NOTE
r-devel-windows-x86_64 1.1.2 6.00 178.00 184.00 NOTE
r-patched-linux-x86_64 1.1.2 4.14 113.95 118.09 NOTE
r-release-linux-x86_64 1.1.2 3.71 110.53 114.24 NOTE
r-release-macos-arm64 1.1.2 66.00 NOTE
r-release-macos-x86_64 1.1.2 137.00 NOTE
r-release-windows-x86_64 1.1.2 6.00 186.00 192.00 NOTE
r-oldrel-macos-arm64 1.1.2 68.00 NOTE
r-oldrel-macos-x86_64 1.1.2 119.00 NOTE
r-oldrel-windows-x86_64 1.1.2 7.00 178.00 185.00 NOTE

Check Details

Version: 1.1.2
Check: Rd files
Result: NOTE checkRd: (-1) getHistList.Rd:32: Lost braces; missing escapes or markup? 32 | ({FALSE})? If a bin is empty, the center of the bin is returned as the | ^ checkRd: (-1) imageClusterPipeline.Rd:82: Lost braces; missing escapes or markup? 82 | of the bin ({FALSE})? If a bin is empty, the center of the bin is returned | ^ 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: 1.1.2
Check: dependencies in R code
Result: NOTE Namespaces in Imports field not imported from: ‘magrittr’ ‘qpdf’ All declared Imports should be used. Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 1.1.2
Check: LazyData
Result: NOTE 'LazyData' is specified without a 'data' directory Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-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.