SNAData 1.16.0 Denise Scholtens
Snapshot Date: 2016-04-20 09:20:20 -0700 (Wed, 20 Apr 2016) | URL: https://hedgehog.fhcrc.org/bioc-data/branches/RELEASE_3_2/experiment/pkgs/SNAData | Last Changed Rev: 3460 / Revision: 3730 | Last Changed Date: 2015-10-13 13:14:23 -0700 (Tue, 13 Oct 2015) |
| zin1 | Linux (Ubuntu 14.04.2 LTS) / x86_64 | NotNeeded | OK | [ OK ] | | |
##############################################################################
##############################################################################
###
### Running command:
###
### /home/biocbuild/bbs-3.2-bioc/R/bin/R CMD check --no-vignettes --timings SNAData_1.16.0.tar.gz
###
##############################################################################
##############################################################################
* using log directory ‘/home/biocbuild/bbs-3.2-data-experiment/meat/SNAData.Rcheck’
* using R version 3.2.4 Revised (2016-03-16 r70336)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘SNAData/DESCRIPTION’ ... OK
* this is package ‘SNAData’ version ‘1.16.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 ‘SNAData’ can be installed ... [1s/1s] OK
* checking installed package size ... OK
* checking package directory ... OK
* checking ‘build’ directory ... OK
* checking DESCRIPTION meta-information ... NOTE
Malformed Description field: should contain one or more complete sentences.
* 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 loading without being on the library search path ... OK
* checking dependencies in R code ... NOTE
'library' or 'require' call to ‘graph’ which was already attached by Depends.
Please remove these calls from your code.
Package in Depends field not imported from: ‘graph’
These packages need to be imported from (in the NAMESPACE file)
for when this namespace is loaded but not attached.
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... NOTE
File ‘SNAData/R/zzz.R’:
.onLoad calls:
require("graph")
Package startup functions should not change the search path.
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 sizes of PDF files under ‘inst/doc’ ... OK
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [1s/1s] OK
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes in ‘inst/doc’ ... OK
* checking running R code from vignettes ... SKIPPED
* checking re-building of vignette outputs ... SKIPPED
* checking PDF version of manual ... OK
* DONE
Status: 3 NOTEs
See
‘/home/biocbuild/bbs-3.2-data-experiment/meat/SNAData.Rcheck/00check.log’
for details.