* using log directory 'd:/Rcompile/CRANpkg/local/4.6/colt.Rcheck' * using R version 4.6.1 (2026-06-24 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 14.3.0 GNU Fortran (GCC) 14.3.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * current time: 2026-08-12 17:46:45 UTC * checking for file 'colt/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'colt' version '0.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 hidden files and directories ... OK * checking for portable file names ... OK * checking whether package 'colt' 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 ... [0s] OK * checking whether the package can be loaded with stated dependencies ... [0s] OK * checking whether the package can be unloaded cleanly ... [0s] OK * checking whether the namespace can be loaded with stated dependencies ... [0s] OK * checking whether the namespace can be unloaded cleanly ... [0s] OK * checking loading without being on the library search path ... [0s] OK * checking whether startup messages can be suppressed ... [0s] OK * checking use of S3 registration ... OK * checking dependencies in R code ... NOTE Unexported object imported by a ':::' call: 'crayon:::mypaste' See the note in ?`:::` about the use of this operator. * checking S3 generic/method consistency ... OK * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... [2s] OK * checking Rd files ... [0s] OK * checking Rd metadata ... 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] OK * checking LazyData ... OK * checking data for ASCII and uncompressed saves ... OK * checking examples ... [0s] OK * checking PDF version of manual ... [20s] OK * checking HTML version of manual ... [2s] OK * DONE Status: 1 NOTE Check process probably crashed or hung up for 20 minutes ... killed Most likely this happened in the example checks (?), if not, ignore the following last lines of example output: This is an example text that showcases the most important elements of a colt theme. The design idea was to provide a package developer with all the theme elements he could need (but not more). For example, colt provides theme elements to style character (like this text) or numbers (12345) differently, but depending on the theme they can still be displayed in the same color. Indeed, too many colors can be distracting. Whether you agree or disagree with the statement above (or don't care) is up to you. It is very easy to create your own colt themes; they are just lists of functions that are created with the constructor colt_theme(). > > cat(clt_h1("Important")) Important> > set_theme(mytheme) > cat(clt_h1("Important")) Important> > set_theme(clt_theme_light) > cat(clt_h1("Important")) Important> > > > > ### *