baySeq 1.0.0
Thomas J. Hardcastle
| Snapshot Date: 2009-12-13 23:30:35 -0800 (Sun, 13 Dec 2009) | | URL: https://hedgehog.fhcrc.org/bioconductor/branches/RELEASE_2_5/madman/Rpacks/baySeq | | Last Changed Rev: 42684 / Revision: 43539 | | Last Changed Date: 2009-10-27 16:33:29 -0700 (Tue, 27 Oct 2009) |
| wilson2 | Linux (openSUSE 11.1) / x86_64 | OK | OK | |
| liverpool | Windows Server 2003 R2 (32-bit) / x64 | OK | WARNINGS | OK |
| pitt | Mac OS X Tiger (10.4.11) / i386 | OK | OK | OK |
| pelham | Mac OS X Leopard (10.5.8) / i386 | OK | [ OK ] | OK |
* checking for working pdflatex ... OK
* using log directory '/Users/biocbuild/bbs-2.5-bioc/meat/baySeq.Rcheck'
* using R version 2.10.0 Patched (2009-10-27 r50222)
* using session charset: UTF-8
* using option '--no-vignettes'
* checking for file 'baySeq/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'baySeq' version '1.0.0'
* checking package name space information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking whether package 'baySeq' can be installed ... 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 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 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 data for non-ASCII characters ... OK
* checking examples ... OK
* checking package vignettes in 'inst/doc' ... SKIPPED
* checking PDF version of manual ... OK