beanumber / openWARData

An R package consisting of data associated with openWAR
7 stars 1 forks source link

Another vignette build failure #5

Closed znmeb closed 9 years ago

znmeb commented 9 years ago
* creating vignettes ... ERROR

Attaching package: 'openWAR'

The following object is masked from 'package:base':

    tabulate

Loading required package: car
Loading required package: dplyr

Attaching package: 'dplyr'

The following object is masked from 'package:stats':

    filter

The following objects are masked from 'package:base':

    intersect, setdiff, setequal, union

Loading required package: lattice
Loading required package: ggplot2
Loading required package: mosaicData

Attaching package: 'mosaic'

The following objects are masked from 'package:dplyr':

    count, do, tally

The following object is masked from 'package:car':

    logit

The following objects are masked from 'package:stats':

    D, IQR, binom.test, cor, cov, fivenum, median, prop.test,
    quantile, sd, t.test, var

The following objects are masked from 'package:base':

    max, mean, min, prod, range, sample, sum

Quitting from lines 27-31 (comparison.Rmd) 
Error: processing vignette 'comparison.Rmd' failed with diagnostics:
object 'openWAR.2012' not found
Execution halted
Error: Command failed (1)
> 

Seems like you need a vignette build step in your testing process.

beanumber commented 9 years ago

Yes...

Running R CMD check:

* installing *source* package ‘openWARData’ ...
** R
** data
*** moving datasets to lazyload DB
** inst
** preparing package for lazy loading
Error in loadNamespace(i, c(lib.loc, .libPaths()), versionCheck = vI[[i]]) : 
  there is no package called ‘survival’
ERROR: lazy loading failed for package ‘openWARData’
* removing ‘/home/bbaumer/Dropbox/lib/openWARData.Rcheck/openWARData’

Why do we need survival? And I have it installed anyway, so what is the problem? Is it a libPaths() issue?

http://stackoverflow.com/questions/23938865/how-to-debug-a-case-where-r-cmd-check-fails-under-narrow-circumstances

beanumber commented 9 years ago

This seems to have been fixed.