* using log directory 'd:/RCompile/CRANincoming/R-devel/hassediagram.Rcheck' * using R Under development (unstable) (2025-05-18 r88216 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 14.2.0 GNU Fortran (GCC) 14.2.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * checking for file 'hassediagram/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'hassediagram' version '1.0' * package encoding: UTF-8 * checking CRAN incoming feasibility ... ERROR Maintainer: 'Damianos Michaelides and Simon Bate ' The maintainer field is invalid or specifies more than one person New submission Conflicting package names (submitted: hassediagram, existing: hasseDiagram [CRAN archive]) Possibly misspelled words in DESCRIPTION: Hasse (3:8, 12:24) The Title field should be in title case. Current version is: 'Hasse diagram of the layout structure and restricted layout structure' In title case that is: 'Hasse Diagram of the Layout Structure and Restricted Layout Structure' The Description field contains or the 'restricted layout structure' of an experimental Please write DOIs as . The Date field 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 hidden files and directories ... OK * checking for portable file names ... OK * checking whether package 'hassediagram' can be installed ... OK * checking installed package size ... OK * checking package directory ... OK * checking for future file timestamps ... OK * checking 'build' directory ... OK * checking DESCRIPTION meta-information ... NOTE Maintainer field differs from that derived from Authors@R Maintainer: 'Damianos Michaelides and Simon Bate ' Authors@R: 'Damianos Michaelides ' * 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 ... OK * checking whether the package can be loaded with stated dependencies ... OK * checking whether the package can be unloaded cleanly ... OK * checking whether the namespace can be loaded with stated dependencies ... OK * checking whether the namespace can be unloaded cleanly ... OK * checking loading without being on the library search path ... 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: sort: function(x, decreasing, ...) sort.effectorder.fun: function(x) 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 ... [14s] OK * checking Rd files ... 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 ... OK * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking contents of 'data' directory ... OK * checking data for non-ASCII characters ... OK * checking LazyData ... OK * checking data for ASCII and uncompressed saves ... OK * checking installed files from 'inst/doc' ... OK * checking files in 'vignettes' ... OK * checking examples ... [57s] NOTE Examples with CPU (user + system) or elapsed time > 10s user system elapsed hasselayout 36.27 1.59 37.9 itemlist 17.38 0.31 17.7 * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking re-building of vignette outputs ... OK * checking PDF version of manual ... [21s] OK * checking HTML version of manual ... OK * DONE Status: 1 ERROR, 3 NOTEs