SCM

R Development Page

nlmeUpdK log file (check_x86_64_linux)

Wed Dec 11 01:36:57 2013: Checking package nlmeUpdK (SVN revision 124) ...
* using log directory ‘/mnt/building/build_2013-12-11-00-09/RF_PKG_CHECK/PKGS/nlmeUpdK.Rcheck’
* using R version 3.0.2 Patched (2013-12-06 r64409)
* using platform: x86_64-unknown-linux-gnu (64-bit)
* using session charset: UTF-8
* checking for file ‘nlmeUpdK/DESCRIPTION’ ... OK
* this is package ‘nlmeUpdK’ version ‘0.3-11’
* checking CRAN incoming feasibility ... NOTE
Maintainer: ‘Andrzej Galecki ’
New submission
* 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 ‘nlmeUpdK’ can be installed ... [1s/3s] OK
* checking installed package size ... OK
* checking package directory ... OK
* checking DESCRIPTION meta-information ... NOTE
Package listed in more than one of Depends, Imports, Suggests, Enhances:
  ‘lattice’
A package should be listed in only one of these fields.
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... WARNING
Invalid citation information in ‘inst/CITATION’:
  Error: ‘\l’ is an unrecognized escape in character string starting ""Andrzej Ga{\l"
* checking R 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 dependencies in R code ... NOTE
Namespace in Imports field not imported from: ‘lattice’
  All declared Imports should be used.
See the information on DESCRIPTION files in the chapter ‘Creating R
packages’ of the ‘Writing R Extensions’ manual.
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... OK
* checking for missing documentation entries ... WARNING
Undocumented code objects:
  ‘Dim’ ‘Names’ ‘Names<-’ ‘VarCorr’ ‘asOneFormula’ ‘coef<-’ ‘corMatrix’
  ‘getCovariateFormula’ ‘getResponseFormula’ ‘isInitialized’ ‘logDet’
  ‘matrix<-’ ‘model.matrix.reStruct.U’ ‘pdConstruct’ ‘pdFactor’
  ‘pdKronecker’ ‘pdMat’ ‘pdMatrix’ ‘splitFormula’ ‘unlistFun’
All user-level objects in a package should have documentation entries.
See the chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking examples ... NONE
* checking PDF version of manual ... OK

WARNING: There were 2 warnings.
NOTE: There were 3 notes.
See
  ‘/mnt/building/build_2013-12-11-00-09/RF_PKG_CHECK/PKGS/nlmeUpdK.Rcheck/00check.log’
for details.

Run time: 61.48 seconds.

Additional Logs:   00install.out
Thanks to:
Vienna University of Economics and Business Powered By FusionForge