• using R version 4.4.1 Patched (2024-08-05 r86980)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     gcc-14 (Debian 14.2.0-8) 14.2.0     GNU Fortran (Debian 14.2.0-8) 14.2.0
• running under: Debian GNU/Linux trixie/sid
• using session charset: UTF-8
• using option ‘--no-vignettes’
• checking for file ‘ctmm/DESCRIPTION’ ... OK
• this is package ‘ctmm’ version ‘1.2.0’
• package encoding: UTF-8
• checking package namespace information ... OK
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... OK
• checking for executable files ... OK
• checking for hidden files and directories ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking whether package ‘ctmm’ can be installed ... OK See the install log for details.
• checking package directory ... OK
• checking for future file timestamps ... OK
• checking ‘build’ directory ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level files ... OK
• checking for left-over files ... OK
• checking index information ... OK
• checking package subdirectories ... OK
• checking code files for non-ASCII characters ... OK
• checking R files for syntax errors ... OK
• checking whether the package can be loaded ... [17s/20s] OK
• checking whether the package can be loaded with stated dependencies ... [16s/20s] OK
• checking whether the package can be unloaded cleanly ... [17s/23s] OK
• checking whether the namespace can be loaded with stated dependencies ... [16s/22s] OK
• checking whether the namespace can be unloaded cleanly ... [17s/21s] OK
• checking loading without being on the library search path ... [9s/12s] OK
• checking whether startup messages can be suppressed ... [17s/20s] OK
• checking use of S3 registration ... OK
• checking dependencies in R code ... OK
• checking S3 generic/method consistency ... OK
• checking replacement functions ... OK
• checking foreign function calls ... OK
• checking R code for possible problems ... [172s/211s] OK
• checking Rd files ... [1s/1s] NOTE checkRd: (-1) ctmm-FAQ.Rd:28-30: Lost braces     28 | {These are the packages I needed in Ubuntu:        | ^ checkRd: (-1) ctmm-FAQ.Rd:34: Lost braces     34 | {Make sure that you have the correct \code{timezone} and \code{timeformat} arguments specified. Also, see \code{\link{outlie}}.}        | ^ checkRd: (-1) ctmm-FAQ.Rd:38: Lost braces     38 | {\code{R} might not have installed or loaded the package correctly---e.g., some files may have failed to overwrite previous versions---or the workspace/session might be corrupted. Uninstall \code{ctmm}, restart \code{R} without saving the workspace/session, and install \code{ctmm} again.}        | ^ checkRd: (-1) ctmm-FAQ.Rd:43-48: Lost braces     43 | {\code{ctmm} has no recursive functions, so I am not exactly sure what causes this error, but it only occurs with certain versions of \code{R} on certain computer architectures. There are several solutions that have worked for people, including restarting \code{R} in a fresh session and updating their software. Alternatively:        | ^ checkRd: (-1) ctmm-FAQ.Rd:52: Lost braces     52 | {Namespace collision sometimes occurs between \code{raster}, \code{sp}, \code{move}, and \code{ctmm}. Either restart \code{R} and only load the \code{ctmm} package, or run \code{ctmm::plot} instead of \code{plot}.}        | ^ checkRd: (-1) ctmm-FAQ.Rd:56: Lost braces     56 | {The default projection in \code{ctmm} does not preserve the direction of North, but better preserves distances for elongated distributions. See the \code{projection} argument in \code{\link{as.telemetry}} and the example in \code{\link[ctmm]{projection}}. The \code{\link{compass}} function is also useful for pointing north.}        | ^ checkRd: (-1) ctmm-FAQ.Rd:60: Lost braces     60 | {Namespace collision can occur between \code{raster} and \code{ctmm}. Either restart \code{R} and only load the \code{ctmm} package, or run \code{ctmm::projection} instead of \code{projection}.}        | ^ checkRd: (-1) ctmm-FAQ.Rd:64: Lost braces; missing escapes or markup?     64 | {Maximize the plot window and/or increase your screen resolution.}        | ^ checkRd: (-1) ctmm-FAQ.Rd:68: Lost braces; missing escapes or markup?     68 | {Click the gear icon in the upper-left corner of the plot window.}        | ^ checkRd: (-1) ctmm-FAQ.Rd:72: Lost braces     72 | {Recent versions of \code{manipulate} and/or RStudio seem to have some issues. Sometimes the gear icon does not render unless you re-run the function 2-5 times.}        | ^ checkRd: (-1) ctmm-FAQ.Rd:76: Lost braces     76 | {You probably have an outdated copy of the \code{manipulate} package installed. Update \code{R} to the latest version and then update all of your packages. This seems to happen frequently with the MacOS release of \code{R}.}        | ^ checkRd: (-1) sigfig.Rd:20: Lost braces; missing escapes or markup?     20 | \item{est}{Can be either confidence-interval estimates with rows {(lower-limit,point-estimate,upper-limit)} or point estimates (with \code{VAR} or \code{SD} also specified).}        | ^
• checking Rd metadata ... OK
• checking Rd line widths ... OK
• checking Rd cross-references ... OK
• checking for missing documentation entries ... OK
• checking for code/documentation mismatches ... OK
• checking Rd \usage sections ... OK
• checking Rd contents ... OK
• checking for unstated dependencies in examples ... OK
• checking contents of ‘data’ directory ... OK
• checking data for non-ASCII characters ... [9s/11s] OK
• checking data for ASCII and uncompressed saves ... OK
• checking installed files from ‘inst/doc’ ... OK
• checking files in ‘vignettes’ ... OK
• checking examples ... [18s/22s] OK
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes ... OK
• checking running R code from vignettes ... SKIPPED
• checking re-building of vignette outputs ... SKIPPED
• checking PDF version of manual ... [8s/11s] OK
• checking HTML version of manual ... [4s/6s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 1 NOTE