* using log directory ‘/srv/hornik/tmp/CRAN_pretest/redatam.Rcheck’
* using R Under development (unstable) (2024-10-08 r87214)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    Debian clang version 18.1.8 (9)
    Debian flang-new version 18.1.8 (9)
* running under: Debian GNU/Linux trixie/sid
* using session charset: UTF-8
* checking for file ‘redatam/DESCRIPTION’ ... OK
* this is package ‘redatam’ version ‘1.0.0’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [3s/6s] NOTE
Maintainer: ‘Jaime Salvador <jaime.salvador@ideasybits.com>’

New submission

Possibly misspelled words in DESCRIPTION:
  DICX (12:67)
  RXDB (12:59)
  Redatam (2:34, 12:40)

Found the following (possibly) invalid URLs:
  URL: https://github.com/ideasybits/redatam-r-package
    From: DESCRIPTION
          man/redatam-package.Rd
    Status: 404
    Message: Not Found
  URL: https://github.com/ideasybits/redatam-r-package/issues
    From: DESCRIPTION
          man/redatam-package.Rd
    Status: 404
    Message: Not Found
* 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 ‘redatam’ can be installed ... [10s/46s] OK
* used C++ compiler: ‘Debian clang version 18.1.8 (11)’
* checking C++ specification ... 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 ... WARNING
Found the following non-empty subdirectories of ‘inst’ also used by R:
  inst/libs
It is recommended not to interfere with package subdirectories used by
R.
* checking code files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... [0s/0s] OK
* checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
* checking whether the package can be unloaded cleanly ... [0s/0s] OK
* checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK
* checking whether the namespace can be unloaded cleanly ... [0s/0s] OK
* checking loading without being on the library search path ... [0s/0s] OK
* checking whether startup messages can be suppressed ... [0s/0s] 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 ... [2s/2s] NOTE
Found the following assignments to the global environment:
File ‘redatam/R/redatam-query.R’:
  assign(dsname, df, .GlobalEnv)
File ‘redatam/R/redatam-run.R’:
  assign(dsname, df, .GlobalEnv)
* checking Rd files ... [0s/0s] OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... WARNING
Undocumented code objects:
  ‘redatam_close_dictionary’ ‘redatam_destroy’ ‘redatam_init’
  ‘redatam_list_entities’ ‘redatam_list_variables’
  ‘redatam_open_dictionary’ ‘redatam_query’ ‘redatam_run’
  ‘redatam_save_dictionary’ ‘redatam_version’
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 ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking line endings in shell scripts ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking line endings in Makefiles ... OK
* checking compilation flags in Makevars ... OK
* checking for GNU extensions in Makefiles ... OK
* checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
* checking use of PKG_*FLAGS in Makefiles ... OK
* checking use of SHLIB_OPENMP_*FLAGS in Makefiles ... OK
* checking pragmas in C/C++ headers and code ... OK
* checking compilation flags used ... OK
* checking compiled code ... NOTE
File ‘redatam/libs/libredengine-1.0.0-rc2.so’:
  Found ‘stderr’, possibly from ‘stderr’ (C)
    Objects: ‘format.o’, ‘red_execute.o’
  Found ‘stdout’, possibly from ‘stdout’ (C)
    Objects: ‘format.o’, ‘red_execute.o’, ‘red_initialize.o’
File ‘redatam/libs/redatam.so’:
  Found ‘stderr’, possibly from ‘stderr’ (C)
    Objects: ‘format.o’, ‘red_execute.o’
  Found ‘stdout’, possibly from ‘stdout’ (C)
    Objects: ‘format.o’, ‘red_execute.o’, ‘red_initialize.o’

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
* checking examples ... [0s/0s] OK
* checking PDF version of manual ... [3s/2s] OK
* checking HTML version of manual ... [0s/0s] OK
* checking for non-standard things in the check directory ... OK
* checking for detritus in the temp directory ... NOTE
Found the following files/directories:
  ‘redatam’
* DONE
Status: 2 WARNINGs, 4 NOTEs