• using R Under development (unstable) (2012-05-19 r59366)
• using platform: x86_64-unknown-linux-gnu (64-bit)
• using session charset: UTF-8
• checking for file ‘opefimor/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘opefimor’ version ‘1.0’
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... WARNING
  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.
  CRAN requires a NAMESPACE file for all submissions.
• checking for executable files ... OK
• checking whether package ‘opefimor’ 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 loading without being on the library search path ... 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 ‘opefimor/R/zzz.R’:
  .First.lib calls:
  cat("Companion package to the book:\n")
  cat("Option Pricing and Estimation of Financial Models in R,\nWiley, Chichester, S.M. Iacus (2011)\n")
  cat("\nFor more informations type: vignette(\"opefimor\") or ?opefimor\n")
  
  Package startup functions should use ‘packageStartupMessage’ to
  generate messages.
  See section ‘Good practice’ in ?.onAttach.
  
• 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 ... OK
• checking Rd contents ... OK
• checking for unstated dependencies in examples ... OK
• checking sizes of PDF files under ‘inst/doc’ ... OK
• checking installed files from ‘inst/doc’ ... NOTE
  The following files should probably not be installed:
  ‘opefimor.tex’
  
  Consider the use of a .Rinstignore file: see ‘Writing R Extensions’,
  or move the vignette sources from ‘inst/doc’ to ‘vignettes’.
• checking examples ... [0s/0s] OK
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes in ‘inst/doc’ ... OK
• checking running R code from vignettes ... [0s/0s] OK
• checking re-building of vignette PDFs ... [1s/2s] OK
• checking PDF version of manual ... OK
  WARNING: There was 1 warning.
  NOTE: There were 2 notes.
  See
  ‘/home/hornik/tmp/R.check/r-devel/Work/PKGS/opefimor.Rcheck/00check.log’
  for details.