* using log directory ‘/srv/hornik/tmp/CRAN/Clustering.Rcheck’
* using R Under development (unstable) (2024-04-19 r86451)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    Debian clang version 17.0.6 (5)
    Debian flang-new version 17.0.6 (5)
* running under: Debian GNU/Linux trixie/sid
* using session charset: UTF-8
* checking for file ‘Clustering/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘Clustering’ version ‘1.7.9’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [4s/4s] NOTE
Maintainer: ‘Luis Alfonso Perez Martos <lapm0001@gmail.com>’

Unknown, possibly misspelled, fields in DESCRIPTION:
  ‘References’

CRAN repository db overrides:
  X-CRAN-Comment: Archived on 2024-04-20 as issues were not corrected
    despite reminders.
* 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 whether package ‘Clustering’ can be installed ... [8s/8s] 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 code files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... [2s/2s] OK
* checking whether the package can be loaded with stated dependencies ... [2s/2s] 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/2s] OK
* checking loading without being on the library search path ... [2s/2s] 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 ... [12s/12s] 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 ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... NOTE
Documented arguments not in \usage in Rd file 'calculate_connectivity.Rd':
  ‘datdf’

Documented arguments not in \usage in Rd file 'dunn_metric.Rd':
  ‘distance’ ‘method’

Documented arguments not in \usage in Rd file 'evaluate_all_column_dataset.Rd':
  ‘data’

Documented arguments not in \usage in Rd file 'information_external.Rd':
  ‘info’

Documented arguments not in \usage in Rd file 'information_internal.Rd':
  ‘info’

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 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 ... [6s/8s] OK
* checking PDF version of manual ... [4s/4s] 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: 2 NOTEs