* using log directory 'd:/Rcompile/CRANpkg/local/2.15/ddesolve.Rcheck'
* using R version 2.15.0 (2012-03-30)
* using platform: x86_64-pc-mingw32 (64-bit)
* using session charset: ISO8859-1
* checking for file 'ddesolve/DESCRIPTION' ... OK
* this is package 'ddesolve' version '1.04'
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... NOTE
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 whether package 'ddesolve' can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking for portable file names ... 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
* loading checks for arch 'i386'
** 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
* loading checks for arch 'x64'
** 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 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 'ddesolve/R/zzz.r':
  .First.lib calls:
    cat("\nddesolve", pkg_info$Version, "-- Copyright (C) 2007-2010 Fisheries & Oceans Canada\n(based  on solv95 by Simon Wood)\n\n--------------------------------------------------\n*****  DEPRECATED - use package PBSddesolve  *****\n--------------------------------------------------\n\nType 'openVig()' on the command line to see the vignette:\n",     userguide_path, "\n\nPackaged on", pkg_date, "\nPacific Biological Station, Nanaimo\n\n\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' ... OK
* checking examples ... NONE
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes in 'inst/doc' ... OK
* checking running R code from vignettes ... OK
* checking re-building of vignette PDFs ... OK
* checking PDF version of manual ... OK
NOTE: There were 2 notes.
See
  'd:/Rcompile/CRANpkg/local/2.15/ddesolve.Rcheck/00check.log'
for details.