• using R version 2.14.2 RC (2012-02-23 r58468)
• using platform: i686-pc-linux-gnu (32-bit)
• using session charset: UTF-8
• checking for file ‘labstatR/DESCRIPTION’ ... OK
• this is package ‘labstatR’ version ‘1.0.6’
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... NOTE
  As from R 2.14.0 all packages need a namespace.
  One will be generated on installation, but it is better to handcraft a
  NAMESPACE file: R CMD build will produce a suitable starting point.
• checking for executable files ... OK
• checking whether package ‘labstatR’ can be installed ... OK
• checking installed package size ... OK
• checking package directory ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level files ... OK
• checking index information ... OK
• checking package subdirectories ... OK
• 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 for unstated 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 ... NOTE
  File ‘labstatR/R/zzz.R’:
  .First.lib calls:
  require("utils", quietly = TRUE)
  writeLines(strwrap(txt, indent = 4, exdent = 4))
  
  Package startup functions should not change the search path.
  Package startup functions should use ‘packageStartupMessage’ to
  generate messages.
  See section ‘Good practice’ in ?.onAttach.
  
  .First.lib: warning in packageDescription("labstatR", lib = mylib):
  partial argument match of 'lib' to 'lib.loc'
• checking Rd files ... OK
• checking Rd metadata ... 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 documentation object 'hist.pf':
  ‘hist.pf’
  
  S3 methods shown with full name in documentation object 'mean.a':
  ‘mean.a’
  
  S3 methods shown with full name in documentation object 'mean.g':
  ‘mean.g’
  
  The \usage entries for S3 methods should use the \method markup and not
  their full name.
  See the chapter ‘Writing R documentation files’ in the ‘Writing R
  Extensions’ manual.
• 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 data for ASCII and uncompressed saves ... OK
• checking examples ... OK
• checking PDF version of manual ... OK