* using log directory ‘/srv/hornik/tmp/CRAN/NFert.Rcheck’
* using R Under development (unstable) (2024-07-02 r86867)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    Debian clang version 18.1.8 (1+b1)
    Debian flang-new version 18.1.8 (1+b1)
* running under: Debian GNU/Linux trixie/sid
* using session charset: UTF-8
* checking for file ‘NFert/DESCRIPTION’ ... OK
* this is package ‘NFert’ version ‘0.0.0.9000’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [2s/3s] NOTE
Maintainer: ‘Michele Croci <michele.croci@unicatt.it>’

New submission

Version contains large components (0.0.0.9000)

Non-FOSS package license (`use_mit_license()`, `use_gpl3_license()` or friends to pick a
license)

Package has a VignetteBuilder field but no prebuilt vignette index.

The Title field should be in title case. Current version is:
  ‘Nitrogen fertilization balance’
In title case that is:
  ‘Nitrogen Fertilization Balance’

DESCRIPTION fields with placeholder content:
  Description: what the package does (one paragraph).
* checking package namespace information ... OK
* checking package dependencies ... NOTE
Vignette dependency required without any vignettes:: ‘knitr’
* 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 ‘NFert’ can be installed ... [1s/1s] OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking DESCRIPTION meta-information ... WARNING
Non-standard license specification:
  `use_mit_license()`, `use_gpl3_license()` or friends to pick a
  license
Standardizable: FALSE
* 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/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 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] OK
* 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:
  ‘ca.table’ ‘cb.table’ ‘coefN_mineralised’ ‘coefN_readily’ ‘coef_time’
  ‘e.table’ ‘mydataset’ ‘uptake_table’
Undocumented data sets:
  ‘ca.table’ ‘cb.table’ ‘coefN_mineralised’ ‘coefN_readily’ ‘coef_time’
  ‘e.table’ ‘mydataset’ ‘uptake_table’
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 ... WARNING
Undocumented arguments in Rd file 'immobilization_and_dispersion_losses.Rd'
  ‘B’ ‘oxygen_availability’ ‘id_rag’ ‘ca.table’

Undocumented arguments in Rd file 'leaching_loss.Rd'
  ‘oxygen_availability’ ‘id_rag’ ‘b1’ ‘ca.table’ ‘cb.table’
Documented arguments not in \usage in Rd file 'leaching_loss.Rd':
  ‘method’

Undocumented arguments in Rd file 'soil_fertility.Rd'
  ‘coefN_readily’ ‘coefN_mineralised’ ‘coef_time’

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 ... NOTE
Argument items with no description in Rd file 'immobilization_and_dispersion_losses.Rd':
  ‘cb.table’
Argument items with no description in Rd file 'leaching_loss.Rd':
  ‘method’
* 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 ... [0s/0s] OK
* checking PDF version of manual ... [3s/3s] 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 ... OK
* DONE
Status: 3 WARNINGs, 3 NOTEs