* using log directory ‘/srv/hornik/tmp/CRAN_pretest/itsmr.Rcheck’
* using R Under development (unstable) (2025-05-13 r88200)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    Debian clang version 19.1.7 (3)
    Debian flang-new version 19.1.7 (3)
* running under: Debian GNU/Linux trixie/sid
* using session charset: UTF-8
* checking for file ‘itsmr/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘itsmr’ version ‘1.11’
* checking CRAN incoming feasibility ... [3s/4s] NOTE
Maintainer: ‘George Weigt <9634295@gmail.com>’

New submission

Package was archived on CRAN

Possibly misspelled words in DESCRIPTION:
  Brockwell (8:261)

CRAN repository db overrides:
  X-CRAN-Comment: Archived on 2025-04-30 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 serialization versions ... OK
* checking whether package ‘itsmr’ can be installed ... [2s/2s] 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 ... [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 ... [4s/4s] 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:
  ‘.difference_sign_test’ ‘.fcomp’ ‘.forecast.arma’ ‘.forecast.diff’
  ‘.forecast.hr’ ‘.forecast.log’ ‘.forecast.season’
  ‘.forecast.transform’ ‘.forecast.trend’ ‘.innovation.kernel’
  ‘.innovation.update’ ‘.innovations’ ‘.ljung_box_test’
  ‘.mcleod_li_test’ ‘.plot.forecast’ ‘.rank_test’ ‘.test.aacvf’
  ‘.test.acvf’ ‘.test.ar.inf’ ‘.test.arar.deaths’ ‘.test.arar.kernel’
  ‘.test.arar.trings’ ‘.test.forecast.deaths’ ‘.test.forecast.dowj’
  ‘.test.forecast.kernel’ ‘.test.forecast.lake’
  ‘.test.forecast.sunspots’ ‘.test.forecast.wine’ ‘.test.ia’
  ‘.test.ma.inf’ ‘.test.out’ ‘.test.periodogram’ ‘.test.smooth.exp’
  ‘.test.smooth.fft’ ‘.test.smooth.ma’ ‘.trings’ ‘.turning_point_test’
  ‘.yw.orig’
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 examples ... [3s/3s] 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: 1 WARNING, 1 NOTE