• using R version 2.9.1 (2009-06-26)
• using session charset: UTF-8
• checking for file 'ROCR/DESCRIPTION' ... OK
• this is package 'ROCR' version '1.0-2'
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking whether package 'ROCR' can be installed ... WARNING
  Found the following significant warnings:
  Warning: unmatched right brace in file 'performance.Rd' on line 7
  See http://www.r-project.org/nosvn/R.check/r-release-linux-ix86/ROCR-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 ... NOTE
  Non-standard license specification:
  GPL (version 2 or later)
  Standardizable: TRUE
  Standardized license specification:
  GPL (>= 2)
• 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 ... WARNING
  'library' or 'require' calls not declared from:
  methods
  package 'methods' is used but not declared
  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 ... NOTE
  Found possibly global 'T' or 'F' in the following function:
  .performance.chisq
• checking Rd files ... OK
• checking Rd files against version 2 parser ... WARNING
  *** error on file ./man/performance.Rd
  Error in parse_Rd("./man/performance.Rd", encoding = "unknown") :
  ./man/performance.Rd:7:1: unexpected '}'
  6: this function.}
  7: }
  ^
  
  problem found in ‘performance.Rd’
• checking Rd cross-references ... OK
• checking for missing documentation entries ... OK
• checking for code/documentation mismatches ... OK
• checking Rd \usage sections ... OK
• checking data for non-ASCII characters ... OK
• checking examples ... OK
• checking PDF version of manual ... OK