• using R Under development (unstable) (2024-11-06 r87293)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     Debian clang version 19.1.2 (2)     Debian flang-new version 19.1.2 (2)
• running under: Debian GNU/Linux trixie/sid
• using session charset: UTF-8
• checking for file ‘rapport/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘rapport’ version ‘1.1’
• 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 serialization versions ... OK
• checking whether package ‘rapport’ can be installed ... OK See the install log for details.
• checking package directory ... OK
• checking for future file timestamps ... 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 ... [1s/1s] OK
• checking whether the package can be loaded with stated dependencies ... [1s/1s] OK
• checking whether the package can be unloaded cleanly ... [1s/1s] OK
• checking whether the namespace can be loaded with stated dependencies ... [1s/1s] OK
• checking whether the namespace can be unloaded cleanly ... [1s/1s] OK
• checking loading without being on the library search path ... [1s/1s] OK
• checking whether startup messages can be suppressed ... [1s/1s] 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 ... [12s/15s] OK
• checking Rd files ... [1s/1s] NOTE checkRd: (-1) rapport.inputs.Rd:26: Lost braces     26 | \item \emph{dataset inputs}, i.e. the inputs that refer to named element of an |code{R} object provided in \code{data} argument in \code{rapport} call. Currently, \code{rapport} supports only \code{data.frame} objects, but that may change in the (near) future.        | ^
• checking Rd metadata ... OK
• checking Rd line widths ... OK
• checking Rd cross-references ... NOTE Found the following Rd file(s) with Rd \link{} targets missing package anchors:   rapport-helpers.Rd: adj.rle, alike.integer, capitalise, catn, fml,     is.boolean, is.empty, is.number, is.string, is.tabular,     is.variable, messagef, pct, stopf, tocamel, trim.space, vgsub,     warningf, rp.desc, rp.freq, rp.iqr, rp.max, rp.mean, rp.median,     rp.min, rp.missing, rp.percent, rp.range, rp.sd, rp.se.mean,     rp.sum, rp.valid, rp.var, htest, htest.short, kurtosis, skewness,     lambda.test, rp.outlier Please provide package anchors for all Rd \link{} targets not in the package itself and the base packages.
• 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 ... [0s/1s] OK
• checking LazyData ... OK
• checking data for ASCII and uncompressed saves ... OK
• checking examples ... [1s/2s] OK
• checking PDF version of manual ... [6s/8s] OK
• checking HTML version of manual ... [2s/3s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 2 NOTEs