• using R version 2.15.0 Patched (2012-03-31 r58888)
  • using platform: sparc-sun-solaris2.10 (32-bit)
  • using session charset: UTF-8
  • checking for file ‘forensim/DESCRIPTION’ ... OK
  • checking extension type ... Package
  • this is package ‘forensim’ version ‘2.0’
  • 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 for .dll and .exe files ... OK
  • checking whether package ‘forensim’ 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 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 ‘forensim/R/zzz.R’:
    .First.lib calls:
    cat(" ### forensim 2.0 is loaded ### \n")

    Package startup functions should use ‘packageStartupMessage’ to
    generate messages.
    See section ‘Good practice’ in ?.onAttach.

    LRmixTK : analyse : veriFile: warning in read.table(tclvalue(filename),
    h = TRUE, as.is = TRUE, sep = "\t", na.string = ""): partial argument
    match of 'h' to 'header'
    LRmixTK : analyse : veriFile: warning in read.table(tclvalue(filename),
    h = TRUE, as.is = TRUE, sep = "\t", na.string = ""): partial argument
    match of 'na.string' to 'na.strings'
    LRmixTK : analyse : veriFile: warning in read.csv(tclvalue(filename), h
    = TRUE, as.is = TRUE, na.string = ""): partial argument match of 'h'
    to 'header'
    LRmixTK : sampleProf : displayprofile: warning in
    read.table(tclvalue(filePath), h = TRUE, as.is = TRUE, sep = "\t",
    na.string = ""): partial argument match of 'h' to 'header'
    LRmixTK : sampleProf : displayprofile: warning in
    read.table(tclvalue(filePath), h = TRUE, as.is = TRUE, sep = "\t",
    na.string = ""): partial argument match of 'na.string' to
    'na.strings'
    LRmixTK : sampleProf : displayprofile: warning in
    read.csv(tclvalue(filePath), h = TRUE, as.is = TRUE, na.string = ""):
    partial argument match of 'h' to 'header'
    RMP: warning in read.table(filename, h = TRUE): partial argument match
    of 'h' to 'header'
    simMixSNP: warning in sample(c(0, 1, 2), size = nSNP, prob = c(p0, p1,
    p2), rep = TRUE): partial argument match of 'rep' to 'replace'
    simPCR2TK : simPCR2TK.local : logis.frames : logi.regression: warning
    in sample(s, dataselec.verif(), rep = FALSE): partial argument match
    of 'rep' to 'replace'
  • 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 use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
  • checking compiled code ... OK
  • checking installed files from ‘inst/doc’ ... OK
  • checking examples ... [78s/79s] OK
  • checking for unstated dependencies in vignettes ... OK
  • checking package vignettes in ‘inst/doc’ ... OK
  • checking running R code from vignettes ... [12s/12s] OK
  • checking re-building of vignette PDFs ... [32s/31s] OK
  • checking PDF version of manual ... OK
    NOTE: There were 2 notes.
    See
    ‘/home/ripley/R/packages/tests32/forensim.Rcheck/00check.log’
    for details.