a4Core 1.7.0 Tobias Verbeke , Willem Ligtenberg
Snapshot Date: 2013-03-24 17:01:43 -0700 (Sun, 24 Mar 2013) | URL: https://hedgehog.fhcrc.org/bioconductor/trunk/madman/Rpacks/a4Core | Last Changed Rev: 73199 / Revision: 74774 | Last Changed Date: 2013-02-06 01:38:38 -0800 (Wed, 06 Feb 2013) |
| george2 | Linux (Ubuntu 12.04.1 LTS) / x86_64 | OK | [ OK ] | |
moscato2 | Windows Server 2008 R2 Enterprise SP1 (64-bit) / x64 | OK | OK | OK |
petty | Mac OS X Leopard (10.5.8) / i386 | OK | OK | OK |
* using log directory ‘/home/biocbuild/bbs-2.12-bioc/meat/a4Core.Rcheck’
* using R version 3.0.0 beta (2013-03-19 r62328)
* using platform: x86_64-unknown-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘a4Core/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘a4Core’ version ‘1.7.0’
* 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 hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking whether package ‘a4Core’ can be installed ... [14s/14s] 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 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 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 examples ... [7s/8s] OK
* checking PDF version of manual ... OK