* using log directory ‘/home/hornik/tmp/R.check/r-release-gcc/Work/PKGS/bootSVD.Rcheck’
* using R version 4.4.2 (2024-10-31)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    gcc-14 (Debian 14.2.0-16) 14.2.0
    GNU Fortran (Debian 14.2.0-16) 14.2.0
* running under: Debian GNU/Linux trixie/sid
* using session charset: UTF-8
* checking for file ‘bootSVD/DESCRIPTION’ ... OK
* this is package ‘bootSVD’ version ‘1.1’
* 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 ‘bootSVD’ can be installed ... OK
See 'https://www.r-project.org/nosvn/R.check/r-release-linux-x86_64/bootSVD-00install.html' 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 ... [0s/1s] OK
* checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
* checking whether the package can be unloaded cleanly ... [0s/0s] OK
* checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK
* checking whether the namespace can be unloaded cleanly ... [0s/1s] OK
* checking loading without being on the library search path ... [0s/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 ... [5s/7s] OK
* checking Rd files ... [0s/1s] NOTE
checkRd: (-1) bootSVD.Rd:13: Lost braces; missing escapes or markup?
    13 | \item{Y}{initial data sample, which can be either a matrix or a \code{\link{ff}} matrix. \code{Y} can be either tall (\eqn{p} by \eqn{n}) or wide (\eqn{n} by \eqn{p}). If \code{Y} is entered and \code{V}, \code{d} and \code{U} (see definitions below) are not entered, then \code{bootSVD} will also compute the SVD of \code{Y}. In this case where the SVD is computed, \code{bootSVD} will assume that the larger dimension of \code{Y} is \eqn{p}, and the smaller dimension of code {Y} is \eqn{n} (i.e. \code{bootSVD} assumes that (\eqn{p>n}). This assumption can be overriden by manually entering \code{V}, \code{U} and \code{d}.\cr
       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               ^
* 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 ... [0s/0s] OK
* checking LazyData ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking examples ... [8s/10s] OK
* checking PDF version of manual ... [5s/7s] OK
* checking HTML version of manual ... [1s/2s] OK
* checking for non-standard things in the check directory ... OK
* DONE
Status: 1 NOTE