• using R Under development (unstable) (2012-02-23 r58468)
• using platform: i686-pc-linux-gnu (32-bit)
• using session charset: UTF-8
• checking for file ‘aster2/DESCRIPTION’ ... OK
• this is package ‘aster2’ version ‘0.1’
• 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 whether package ‘aster2’ can be installed ... OK
• checking installed package size ... OK
• checking package directory ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... 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
• 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 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 ‘aster2/R/onAttach.R’:
  .onAttach calls:
  cat("This is beta software.\n")
  cat("Unless you need to do aster models with dependence groups,\n")
  cat(" use package \"aster\" instead.\n")
  cat("See help(aster2-package) for differences from package \"aster\"\n")
  cat(" and examples.\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 contents of ‘data’ directory ... OK
• checking data for non-ASCII characters ... OK
• checking data for ASCII and uncompressed saves ... OK
• checking line endings in C/C++/Fortran sources/headers ... OK
• checking line endings in Makefiles ... OK
• checking for portable compilation flags in Makevars ... OK
• checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
• checking compiled code ... OK
• checking examples ... [63s/63s] OK
• checking for unstated dependencies in tests ... OK
• checking tests ... [26s/26s] OK
  Running ‘asterdata.R’ [0s/0s]
  Comparing ‘asterdata.Rout’ to ‘asterdata.Rout.save’ ... OK
  Running ‘constancy.R’ [1s/1s]
  Comparing ‘constancy.Rout’ to ‘constancy.Rout.save’ ... OK
  Running ‘echinacea-cond.R’ [1s/1s]
  Comparing ‘echinacea-cond.Rout’ to ‘echinacea-cond.Rout.save’ ... OK
  Running ‘echinacea.R’ [21s/21s]
  Comparing ‘echinacea.Rout’ to ‘echinacea.Rout.save’ ... OK
  Running ‘families.R’ [1s/1s]
  Comparing ‘families.Rout’ to ‘families.Rout.save’ ... OK
  Running ‘logl.R’ [0s/0s]
  Comparing ‘logl.Rout’ to ‘logl.Rout.save’ ... OK
  Running ‘subset.R’ [0s/0s]
  Comparing ‘subset.Rout’ to ‘subset.Rout.save’ ... OK
  Running ‘transform.R’ [1s/1s]
  Comparing ‘transform.Rout’ to ‘transform.Rout.save’ ... OK
• checking PDF version of manual ... OK
  NOTE: There was 1 note.
  See
  ‘/home/hornik/tmp/R.check/r-devel/Work/PKGS/aster2.Rcheck/00check.log’
  for details.