* using log directory ‘/data/gannet/ripley/R/packages/tests-devel/udpipe.Rcheck’ * using R Under development (unstable) (2024-04-20 r86457) * using platform: x86_64-pc-linux-gnu * R was compiled by gcc-13 (GCC) 13.2.0 GNU Fortran (GCC) 13.2.0 * running under: Fedora Linux 36 (Workstation Edition) * using session charset: UTF-8 * using option ‘--no-stop-on-test-error’ * checking for file ‘udpipe/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘udpipe’ version ‘0.8.11’ * 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 ‘udpipe’ can be installed ... [220s/166s] OK See 'https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-fedora-gcc/udpipe-00install.html' for details. * used C++ compiler: ‘g++-13 (GCC) 13.2.0’ * checking C++ specification ... NOTE Specified C++11: please drop specification unless essential * checking package directory ... 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 ... OK * checking whether the package can be loaded with stated dependencies ... OK * checking whether the package can be unloaded cleanly ... OK * checking whether the namespace can be loaded with stated dependencies ... OK * checking whether the namespace can be unloaded cleanly ... OK * checking loading without being on the library search path ... 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 ... [15s/15s] OK * checking Rd files ... NOTE checkRd: (-1) predict.LDA.Rd:50-56: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) predict.LDA.Rd:57-58: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) txt_tagsequence.Rd:14: Lost braces in \itemize; meant \describe ? checkRd: (-1) txt_tagsequence.Rd:15-16: Lost braces in \itemize; meant \describe ? checkRd: (-1) udpipe.Rd:12: Lost braces in \itemize; meant \describe ? checkRd: (-1) udpipe.Rd:13: Lost braces in \itemize; meant \describe ? checkRd: (-1) udpipe.Rd:14: Lost braces in \itemize; meant \describe ? checkRd: (-1) udpipe.Rd:36: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:37: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:38: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:39: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:40: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:41: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:42: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:43: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:44: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:45: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:46: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:47: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:48: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:49: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:50: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:51: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe.Rd:52: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_accuracy.Rd:29: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_accuracy.Rd:30: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_annotate.Rd:51: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_annotate.Rd:52-53: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_annotate.Rd:54: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_download_model.Rd:84: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_download_model.Rd:85: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_download_model.Rd:86: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_download_model.Rd:87: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_download_model.Rd:88: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_load_model.Rd:15: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_load_model.Rd:16: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_train.Rd:45: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_train.Rd:46: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_train.Rd:47: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_train.Rd:48: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) udpipe_train.Rd:49-50: Lost braces in \itemize; \value handles \item{}{} directly * 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 ... OK * checking data for ASCII and uncompressed saves ... 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 ... [33s/35s] OK * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking re-building of vignette outputs ... [190s/190s] OK * checking PDF version of manual ... OK * checking HTML version of manual ... OK * checking for non-standard things in the check directory ... OK * checking for detritus in the temp directory ... OK * DONE Status: 2 NOTEs