* using log directory ‘/srv/hornik/tmp/CRAN/rpostgis.Rcheck’
* using R Under development (unstable) (2023-10-11 r85316)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    Debian clang version 16.0.6 (15)
    GNU Fortran (Debian 13.2.0-4) 13.2.0
* running under: Debian GNU/Linux trixie/sid
* using session charset: UTF-8
* checking for file ‘rpostgis/DESCRIPTION’ ... OK
* this is package ‘rpostgis’ version ‘1.5.0’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [4s/5s] NOTE
Maintainer: ‘Adrián Cidre González <adrian.cidre@gmail.com>’

New maintainer:
  Adrián Cidre González <adrian.cidre@gmail.com>
Old maintainer(s):
  David Bucklin <david.bucklin@gmail.com>
* 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 ‘rpostgis’ can be installed ... [14s/14s] OK
* 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 R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... [4s/4s] OK
* checking whether the package can be loaded with stated dependencies ... [4s/4s] OK
* checking whether the package can be unloaded cleanly ... [4s/4s] OK
* checking whether the namespace can be loaded with stated dependencies ... [4s/4s] OK
* checking whether the namespace can be unloaded cleanly ... [4s/4s] OK
* checking loading without being on the library search path ... [4s/4s] OK
* checking whether startup messages can be suppressed ... [4s/4s] 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 ... [21s/21s] OK
* checking Rd files ... [0s/0s] NOTE
checkRd: (-1) pgInsert.Rd:144: Lost braces
   144 | Use this function with code{df.mode = TRUE} to save data frames from
       |                            ^
checkRd: (-1) pgWriteGeom.Rd:147: Lost braces
   147 | Use this function with code{df.mode = TRUE} to save data frames from
       |                            ^
* 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 ... NOTE
Documented arguments not in \usage in Rd file 'pgCheckGeom.Rd':
  ‘namechar’

Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking examples ... [8s/8s] OK
* checking PDF version of manual ... [3s/3s] OK
* checking HTML version of manual ... [1s/1s] OK
* checking for non-standard things in the check directory ... OK
* checking for detritus in the temp directory ... OK
* DONE
Status: 3 NOTEs