• using R version 2.8.0 Under development (unstable) (2008-08-04 r46223)
  • using session charset: UTF-8
  • checking for file 'biclust/DESCRIPTION' ... OK
  • this is package 'biclust' version '0.5'
  • checking package name space information ... OK
  • checking package dependencies ... OK
  • checking if this is a source package ... OK
  • checking whether package 'biclust' can be installed ... WARNING
    Found the following significant warnings:
    WARNING: 'SaveImage' is defunct: please remove it
    See http://www.r-project.org/nosvn/R.check/r-devel-linux-ix86/biclust-00install.html for details.
  • 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 name space can be loaded with stated dependencies ... 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 ... OK
  • checking Rd files ... OK
  • checking Rd cross-references ... OK
  • checking for missing documentation entries ... WARNING
    Warning in get_S4_generics_with_methods(code_env) :
    Generics g in env = <environment: package:biclust> where hasMethods(g, env) errors: ‘show’
    May need something like

    importFrom("methods", "show")

    in NAMESPACE.
    Warning in methods::findMethods(g, env) :
    non-generic function 'show' given to findMethods()
    All user-level objects in a package should have documentation entries.
    See the chapter 'Writing R documentation files' in manual 'Writing R
    Extensions'.
  • checking for code/documentation mismatches ... OK
  • checking Rd \usage sections ... OK
  • checking data for non-ASCII characters ... OK
  • checking line endings in C/C++/Fortran sources/headers ... OK
  • checking line endings in Makefiles ... OK
  • checking for portable use of $BLAS_LIBS ... OK
  • creating biclust-Ex.R ... OK
  • checking examples ... OK
  • creating biclust-manual.tex ... OK
  • checking biclust-manual.tex using pdflatex ... OK