• using R version 3.0.1 Patched (2013-05-22 r62772)
• using platform: i386-pc-solaris2.10 (32-bit)
• using session charset: UTF-8
• checking for file ‘nlrwr/DESCRIPTION’ ... OK
• this is package ‘nlrwr’ version ‘1.1-0’
• 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 ‘nlrwr’ can be installed ... OK
• checking installed package size ... OK
• checking package directory ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level files ... OK
• checking for left-over 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 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 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 ‘nlrwr/R/onAttach.R’:
  .onAttach calls:
  cat("\n")
  cat("'nlrwr' has been loaded.\n\n")
  cat("Please cite R and 'nlrwr' if used for a publication,\n")
  cat("for references type 'citation()' and 'citation('nlrwr')'.\n\n")
  library(drc)
  
  Package startup functions should not change the search path.
  Package startup functions should use ‘packageStartupMessage’ to
  generate messages.
  See section ‘Good practice’ in '?.onAttach'.
• checking Rd files ... NOTE
  prepare_Rd: L.minor.Rd:32-34: Dropping empty section \examples
  prepare_Rd: O.mykiss.Rd:34: Dropping empty section \references
  prepare_Rd: SSexp.Rd:35: Dropping empty section \note
  prepare_Rd: btb.Rd:39-41: Dropping empty section \examples
  prepare_Rd: isomerization.Rd:37-38: Dropping empty section \references
  prepare_Rd: sockeye.Rd:36-37: Dropping empty section \examples
  prepare_Rd: sts.Rd:38-39: Dropping empty section \examples
• 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 'boxcox.nls':
  ‘boxcox.nls’
  
  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
  NOTE: There were 3 notes.
  See
  ‘/home/ripley/R/packages/tests32/nlrwr.Rcheck/00check.log’
  for details.