* using log directory ‘/home/hornik/tmp/R.check/r-devel-clang/Work/PKGS/gjam.Rcheck’
* using R Under development (unstable) (2025-02-23 r87804)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    Debian clang version 19.1.7 (1+b1)
    Debian flang-new version 19.1.7 (1+b1)
* running under: Debian GNU/Linux trixie/sid
* using session charset: UTF-8
* checking for file ‘gjam/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘gjam’ version ‘2.6.2’
* 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 ‘gjam’ can be installed ... OK
See 'https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-clang/gjam-00install.html' for details.
* used C++ compiler: ‘Debian clang version 19.1.7 (1+b1)’
* checking C++ specification ... NOTE
  Specified C++11: please drop specification unless essential
* 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 ... [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/1s] 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 ... [62s/78s] OK
* checking Rd files ... [1s/1s] NOTE
checkRd: (-1) gjamCensorY.Rd:27: Lost braces; missing escapes or markup?
    27 |   \item{\code{y}}{n by S matrix updated with censored {values} substituted for
       |                                                       ^
checkRd: (-1) gjamFillMissingTimes.Rd:32: Lost braces
    32 | Missing times in the data occur where there are gaps in \code{timeCol} column of \code{xdata} and the initial time \code{0} for each sequence.  New versions of the data have \code{NA} (\code{xdata}) or prior values with appropriate weight (\code{ydata}).  Missing times are filled in \code{xdata, ydata, edata}, including a time \code{0} which serves as a prior mean for \code{ydata} for time code{1}.  The group and time indices in columns \code{groupCol} and \code{timeCol} of \code{xdata} reference the time for a given time series.  Missing values in the columns \code{groupVars} of \code{xdata} are filled automatically filled in.  This assumes that values for these variables are fixed for the group.  If \code{FILLMEANS}, the missing  values in \code{ydata} are filled with means for the group and given a low weight specified in \code{missingEffort}.
       |                                                                                                                                                                                                                                                                                                                                                                                                              ^
* 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 line endings in C/C++/Fortran sources/headers ... OK
* checking line endings in Makefiles ... OK
* checking compilation flags in Makevars ... OK
* checking for GNU extensions in Makefiles ... OK
* checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
* checking use of PKG_*FLAGS in Makefiles ... OK
* checking use of SHLIB_OPENMP_*FLAGS in Makefiles ... OK
* checking pragmas in C/C++ headers and code ... OK
* checking compilation flags used ... OK
* checking compiled code ... OK
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [1s/1s] OK
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes ... OK
* checking re-building of vignette outputs ... [0s/1s] OK
* checking PDF version of manual ... [7s/10s] OK
* checking HTML version of manual ... [1s/2s] OK
* checking for non-standard things in the check directory ... OK
* DONE
Status: 2 NOTEs