* using log directory 'd:/Rcompile/CRANpkg/local/4.5/CVST.Rcheck' * using R Under development (unstable) (2024-06-07 r86704 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 13.2.0 GNU Fortran (GCC) 13.2.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * checking for file 'CVST/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'CVST' version '0.2-3' * 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 hidden files and directories ... OK * checking for portable file names ... OK * checking whether package 'CVST' can be installed ... OK * checking installed package size ... OK * checking package 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 ... [2s] OK * checking whether the package can be loaded with stated dependencies ... [0s] WARNING It looks like this package (or one of its dependent packages) has an unstated dependence on a standard package. All dependencies must be declared in DESCRIPTION. See section 'The DESCRIPTION file' in the 'Writing R Extensions' manual. * checking whether the package can be unloaded cleanly ... [0s] WARNING Error: package 'kernlab' could not be loaded Execution halted * checking whether the namespace can be loaded with stated dependencies ... [0s] WARNING A namespace must be able to be loaded with just the base namespace loaded: otherwise if the namespace gets loaded by a saved object, the session will be unable to start. Probably some imports need to be declared in the NAMESPACE file. * checking whether the namespace can be unloaded cleanly ... [3s] OK * checking loading without being on the library search path ...