• using R Under development (unstable) (2014-07-23 r66240)
• using platform: x86_64-unknown-linux-gnu (64-bit)
• using session charset: UTF-8
• checking for file ‘LIHNPSD/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘LIHNPSD’ version ‘0.2.1’
• checking package namespace information ... OK
• checking package dependencies ... NOTE
  Depends: includes the non-default packages:
  ‘sn’ ‘moments’ ‘BB’ ‘Bolstad2’ ‘optimx’ ‘Rmpfr’
  Adding so many packages to the search path is excessive and importing
  selectively is preferable.
• 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 ‘LIHNPSD’ 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 dependencies in R code ... NOTE
  Packages in Depends field not imported from:
  ‘BB’ ‘Bolstad2’ ‘Rmpfr’ ‘moments’ ‘optimx’ ‘sn’
  These packages need to be imported from (in the NAMESPACE file)
  for when this namespace is loaded but not attached.
  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 ... OK
• 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 contents of ‘data’ directory ... OK
• checking data for non-ASCII characters ... OK
• checking data for ASCII and uncompressed saves ... OK
• checking examples ... [7s/7s] OK
• checking PDF version of manual ... OK

NOTE: There were 2 notes.