* using log directory ‘/home/hornik/tmp/R.check/r-devel-gcc/Work/PKGS/geotopbricks.Rcheck’ * using R Under development (unstable) (2025-02-28 r87840) * using platform: x86_64-pc-linux-gnu * R was compiled by gcc-14 (Debian 14.2.0-16) 14.2.0 GNU Fortran (Debian 14.2.0-16) 14.2.0 * running under: Debian GNU/Linux trixie/sid * using session charset: UTF-8 * checking for file ‘geotopbricks/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘geotopbricks’ version ‘1.5.8.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 ‘geotopbricks’ can be installed ... OK See 'https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-gcc/geotopbricks-00install.html' 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 ... [6s/7s] OK * checking whether the package can be loaded with stated dependencies ... [6s/7s] OK * checking whether the package can be unloaded cleanly ... [7s/9s] OK * checking whether the namespace can be loaded with stated dependencies ... [7s/8s] OK * checking whether the namespace can be unloaded cleanly ... [6s/7s] OK * checking loading without being on the library search path ... [7s/9s] 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 ... [29s/34s] OK * checking Rd files ... [0s/0s] OK * 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: GeotopRasterBrick-class.Rd: Raster-class KML-methods.Rd: projectRaster bondone.Rd: zoo brick-methods.Rd: RasterBrick-class, raster brick.decimal.formatter.Rd: raster, RasterBrick-class brickFromOutputSoil3DTensor.Rd: RasterLayer-class, RasterBrick-class, Raster-class geotopbrick.Rd: RasterBrick-class get.geotop.inpts.keyword.value.Rd: Raster-class, raster, zoo get.geotop.points.Rd: sf get.geotop.recovery.state.Rd: raster read.ascii.vectorized.brick.Rd: raster, RasterBrick-class read.raster.from.url.Rd: raster read.vectorized.geotop.recovery.Rd: raster write.ascii.vectorized.brick.Rd: RasterBrick-class, writeRaster write.vectorized.geotop.recovery.Rd: writeRaster writeRasterxGEOtop.Rd: writeRaster, RasterBrick-class Please provide package anchors for all Rd \link{} targets not in the package itself and the base packages. * 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/1s] OK * checking data for ASCII and uncompressed saves ... OK * checking examples ... [8s/15s] OK Examples with CPU (user + system) or elapsed time > 5s user system elapsed get.geotop.inpts.keyword.value 0.714 0.102 5.748 * checking PDF version of manual ... [4s/6s] OK * checking HTML version of manual ... [1s/2s] OK * checking for non-standard things in the check directory ... OK * DONE Status: 1 NOTE