* using log directory ‘/srv/hornik/tmp/CRAN/octopucs.Rcheck’
* using R Under development (unstable) (2024-07-15 r86902)
* 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 ‘octopucs/DESCRIPTION’ ... OK
* this is package ‘octopucs’ version ‘0.1.0’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [3s/3s] NOTE
Maintainer: ‘Roger Guevara <roger.guevara@inecol.mx>’

New submission

The Description field should not start with the package name,
  'This package' or similar.

The Date field is not in ISO 8601 yyyy-mm-dd format.
* 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 ‘octopucs’ can be installed ... [4s/4s] OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking DESCRIPTION meta-information ... NOTE
Author field differs from that derived from Authors@R
  Author:    ‘Roger Guavara [aut, cre], Ian MacGregor-Fors [aut]’
  Authors@R: ‘Roger Guevara [aut, cre], Ian MacGregor-Fors [aut]’

* 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 ... NOTE
Mismatches for apparent methods not registered:
plot:
  function(x, ...)
plot.octopucs:
  function(M2, cex, lab.pos, n, distance, method, prop, Name, ylim,
           xlim, verbose, orientation)

text:
  function(x, ...)
text.octopucs:
  function(M2, support, sep.lab, disp, verbose, orientation)
See section ‘Registering S3 methods’ in the ‘Writing R Extensions’
manual.
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... [7s/7s] 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
S3 methods shown with full name in Rd file 'plot.octopucs.Rd':
  ‘plot.octopucs’

S3 methods shown with full name in Rd file 'text.octopucs.Rd':
  ‘text.octopucs’

The \usage entries for S3 methods should use the \method markup and not
their full name.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking examples ... [14s/15s] NOTE
Examples with CPU (user + system) or elapsed time > 5s
          user system elapsed
octopucs 8.918  0.076   9.379
* 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: 5 NOTEs