Last updated on 2024-11-21 19:53:11 CET.
Package | NOTE | OK |
---|---|---|
DendroSync | 10 | 3 |
Current CRAN status: NOTE: 10, OK: 3
Version: 0.1.4
Check: Rd files
Result: NOTE
checkRd: (-1) conifersIP.Rd:9: Lost braces; missing escapes or markup?
9 | \code{conifersIP} {has following variables:}
| ^
checkRd: (-1) conifersIP.Rd:11: Lost braces in \itemize; meant \describe ?
checkRd: (-1) conifersIP.Rd:12: Lost braces in \itemize; meant \describe ?
checkRd: (-1) conifersIP.Rd:13: Lost braces in \itemize; meant \describe ?
checkRd: (-1) conifersIP.Rd:14: Lost braces in \itemize; meant \describe ?
checkRd: (-1) conifersIP.Rd:15: Lost braces in \itemize; meant \describe ?
checkRd: (-1) sync.Rd:22: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) sync.Rd:23: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) sync.Rd:24: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) sync.Rd:25: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) sync.Rd:26: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) sync.Rd:27: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) sync.Rd:28: Lost braces in \itemize; \value handles \item{}{} directly
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
Version: 0.1.4
Check: Rd cross-references
Result: NOTE
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
dendro.varcov.Rd: varFunc, varIdent, lmeObject
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
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.