* using log directory ‘/srv/hornik/tmp/CRAN_pretest/CSTE.Rcheck’
* using R Under development (unstable) (2024-11-15 r87338)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    Debian clang version 19.1.1 (1)
    Debian flang-new version 19.1.1 (1)
* running under: Debian GNU/Linux trixie/sid
* using session charset: UTF-8
* checking for file ‘CSTE/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘CSTE’ version ‘2.0.0’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [3s/3s] WARNING
Maintainer: ‘Wenjie Hu <huwenjie@pku.edu.cn>’

New submission

Package was archived on CRAN

Insufficient package version (submitted: 2.0.0, existing: 2.0.0)

Possibly misspelled words in DESCRIPTION:
  CSTE (5:45)
  Guo (7:9)
  al (6:138, 7:16)
  et (6:135, 7:13)

CRAN repository db overrides:
  X-CRAN-Comment: Archived on 2024-04-20 as issues were not corrected
    despite reminders.

The Date field is over a month old.

This build time stamp is over a month old.
* 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 ‘CSTE’ can be installed ... [8s/8s] OK
* used C++ compiler: ‘Debian clang version 19.1.3 (1)’
* 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 ... [1s/1s] OK
* checking whether the package can be loaded with stated dependencies ... [1s/1s] OK
* checking whether the package can be unloaded cleanly ... [1s/1s] OK
* checking whether the namespace can be loaded with stated dependencies ... [1s/1s] OK
* checking whether the namespace can be unloaded cleanly ... [1s/1s] OK
* checking loading without being on the library search path ... [1s/1s] 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 ... [6s/6s] 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 'tool.Rd':
  ‘seq’

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 line endings in C/C++/Fortran sources/headers ... OK
* checking pragmas in C/C++ headers and code ... OK
* checking compilation flags used ... OK
* checking compiled code ... OK
* checking examples ... [2s/2s] OK
* checking PDF version of manual ... [2s/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 ... OK
* DONE
Status: 1 WARNING, 1 NOTE