• using R version 2.10.1 Patched (2010-02-06 r51106)
• using session charset: UTF-8
• checking for file 'realized/DESCRIPTION' ... OK
• this is package 'realized' version '0.81'
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking whether package 'realized' can be installed ... WARNING
  Found the following significant warnings:
  Warning: ./man/rv.avg.Rd:20: unexpected '}'
  Warning: ./man/rv.timescale.Rd:7: unexpected '}'
  See http://www.r-project.org/nosvn/R.check/r-patched-linux-x86_64/realized-00install.html for details.
• checking package directory ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking DESCRIPTION meta-information ... WARNING
  Invalid license file pointers: LICENSE
• 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 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
  .ts2millis: no visible global function definition for ‘timeDate’
• checking Rd files ... WARNING
  prepare_Rd: rv.avg.Rd:20: unexpected '}'
  prepare_Rd: rv.timescale.Rd:7: unexpected '}'
• 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 'merge.realizedObject':
  merge.realizedObject
  
  The \usage entries for S3 methods should use the \method markup and not
  their full name.
  See the chapter 'Writing R documentation files' in manual 'Writing R
  Extensions'.
• checking data for non-ASCII characters ... OK
• checking line endings in C/C++/Fortran sources/headers ... OK
• checking line endings in Makefiles ... OK
• checking for portable use of $BLAS_LIBS ... OK
• checking examples ... OK
• checking PDF version of manual ... OK