* using log directory ‘/srv/hornik/tmp/CRAN_pretest/aftsem.Rcheck’ * using R Under development (unstable) (2024-09-02 r87090) * using platform: x86_64-pc-linux-gnu * R was compiled by Debian clang version 18.1.8 (9) Debian flang-new version 18.1.8 (9) * running under: Debian GNU/Linux trixie/sid * using session charset: UTF-8 * checking for file ‘aftsem/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘aftsem’ version ‘1.0’ * package encoding: UTF-8 * checking CRAN incoming feasibility ... [1s/1s] WARNING Maintainer: ‘’ The maintainer field lacks a name New submission Non-FOSS package license (GNU General Public License v3.0) Possibly misspelled words in DESCRIPTION: Gehan (10:25) Hellers (10:83) Jin (10:51) lss (10:55) No Authors@R field in DESCRIPTION. Please add one, modifying Authors@R: c(person(given = "Martin", family = "Benedikt", role = "aut"), person(role = "cre", email = "benedma2@cvut.cz")) as necessary. The Title field should be in title case. Current version is: ‘Implemented several basic algorithms for estimation of regression parameters for semiparametric accelerated failure time model’ In title case that is: ‘Implemented Several Basic Algorithms for Estimation of Regression Parameters for Semiparametric Accelerated Failure Time Model’ 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 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 ‘aftsem’ can be installed ... [32s/32s] WARNING Found the following significant warnings: Warning: aftsem-package.Rd:26: All text must be in a section See ‘/srv/hornik/tmp/CRAN_pretest/aftsem.Rcheck/00install.out’ for details. * used C++ compiler: ‘Debian clang version 18.1.8 (9)’ * checking package directory ... OK * checking for future file timestamps ... OK * checking DESCRIPTION meta-information ... NOTE Malformed Description field: should contain one or more complete sentences. Non-standard license specification: GNU General Public License v3.0 Standardizable: FALSE * 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] NOTE aftsem: no visible binding for global variable ‘response’ Undefined global functions or variables: response * checking Rd files ... [0s/0s] WARNING prepare_Rd: aftsem-package.Rd:26: All text must be in a section prepare_Rd: aftsem-package.Rd:32-34: Dropping empty section \examples * checking Rd metadata ... WARNING Rd files with duplicated alias 'aftsem': ‘aftsem-package.Rd’ ‘aftsem.Rd’ * checking Rd line widths ... OK * checking Rd cross-references ... NOTE Unknown package ‘’ in Rd xrefs * checking for missing documentation entries ... OK * checking for code/documentation mismatches ... OK * checking Rd \usage sections ... WARNING Undocumented arguments in Rd file 'gehan_estimation.Rd' ‘m’ 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 ... NOTE Auto-generated content requiring editing in Rd file 'aftsem-package.Rd': \details: ‘...o use the package, including the most important functions ~~’ \references: ‘~~ Literature or other references for background information ~~’ \seealso: ‘~~ Optional links to other man pages, e.g. ~~ ~~ \code{\link...’ * checking for unstated dependencies in examples ... OK * checking line endings in C/C++/Fortran sources/headers ... OK * checking line endings in Makefiles ... OK * checking compilation flags in Makevars ... OK * checking for GNU extensions in Makefiles ... OK * checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK * checking use of PKG_*FLAGS in Makefiles ... OK * checking use of SHLIB_OPENMP_*FLAGS in Makefiles ... OK * checking pragmas in C/C++ headers and code ... OK * checking compilation flags used ... OK * checking compiled code ... OK * checking examples ... [1s/1s] OK * 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 WARNINGs, 4 NOTEs