• using R Under development (unstable) (2024-11-15 r87338)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     Debian clang version 19.1.3 (2)     Debian flang-new version 19.1.3 (2)
• running under: Debian GNU/Linux trixie/sid
• using session charset: UTF-8
• checking for file ‘RNCEP/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘RNCEP’ version ‘1.0.10’
• 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 ‘RNCEP’ can be installed ... OK See the install log 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 ... [2s/3s] OK
• checking whether the package can be loaded with stated dependencies ... [2s/3s] OK
• checking whether the package can be unloaded cleanly ... [2s/2s] OK
• checking whether the namespace can be loaded with stated dependencies ... [2s/2s] OK
• checking whether the namespace can be unloaded cleanly ... [2s/3s] OK
• checking loading without being on the library search path ... [2s/3s] OK
• checking use of S3 registration ... OK
• checking dependencies in R code ... NOTE Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified
• checking S3 generic/method consistency ... WARNING Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified See section ‘Generic functions and methods’ in the ‘Writing R Extensions’ manual.
• checking replacement functions ... WARNING Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified The argument of a replacement function which corresponds to the right hand side must be named ‘value’.
• checking foreign function calls ... NOTE Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified See chapter ‘System and foreign language interfaces’ in the ‘Writing R Extensions’ manual.
• checking R code for possible problems ... [31s/43s] NOTE Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified
• checking Rd files ... [1s/1s] NOTE checkRd: (-1) NCEP.track2kml.Rd:36: Lost braces     36 | There are several options for specifying \code{col.scheme}. A single color may be specified for all points (using e.g. \code{'red'}, \code{2}, or \code{"#FF0000"}), specific colors may be given for each point (e.g. \code{c('red','blue','green', etc.)} or code{c('#FF0000','#0000FF','#00FF00', etc.)}), or the function can automatically assign colors, according to the values in \code{clo.variable}, if \code{col.scheme} is any color palette in \code{\link[RColorBrewer]{display.brewer.all}} or one of the recognizezd R color palettes (i.e. \code{'rainbow'}, \code{'heat.colors'}, \code{'terrain.colors'}, \code{'topo.colors'}, \code{'cm.colors'}, or \code{'bpy.colors'}). An alpha value (0-255) may be supplied to \code{point.alpha} to adjust transparencies.        | ^
• checking Rd metadata ... OK
• checking Rd line widths ... OK
• checking Rd cross-references ... NOTE Found the following Rd file(s) with Rd \link{} targets missing package anchors:   NCEP.bind.Rd: abind Please provide package anchors for all Rd \link{} targets not in the package itself and the base packages.
• checking for missing documentation entries ... WARNING Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified All user-level objects in a package should have documentation entries. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual.
• checking for code/documentation mismatches ... WARNING Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified
• checking Rd \usage sections ... NOTE Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified The \usage entries for S3 methods should use the \method markup and not their full name. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual.
• 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 ... [2s/3s] OK
• checking PDF version of manual ... [6s/8s] OK
• checking HTML version of manual ... [2s/3s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 4 WARNINGs, 6 NOTEs