similar to: removing files on windows as part of vignette building

Hi, This is a follow-up to the problem reported here: https://stat.ethz.ch/pipermail/r-devel/2010-September/058460.html After I updated R-2.12 to 2010-09-13 r52905 on the Bioc build system, some of the packages that have a Makefile in <pkg>/inst/doc still don't build on Windows. For example, 'R\bin\R.exe CMD build adSplit' gives: * checking for file

Based on some testing it seems to me that if I have a package with a dataset in /data a Sweave vignette in inst/doc (but no associated pdf file) the vignette loads the data in /data through data(dataset) and I do a R CMD build R will try to build the pdf version of the vignette, but will be unable to find the dataset in data because the package is not yet installed. However, if I do

I want to include a vignette with a package I wrote. I did follow the "Writting R extentions" document step by step, but went I run "Rcmd build", an error occurs. It goes like this: " * creating vignettes ... ERROR . . . . :7: Emergency stop L7L ==> Fatal error occurred, no output PDF file produced!texify: pdflatex failed for some reason <see log file>.

The Bioconductor build for a package DirichletMultinomial on R Under development (unstable) (2013-02-26 r62077) -- "Unsuffered Consequences" at http://bioconductor.org/checkResults/devel/bioc-LATEST/DirichletMultinomial/george2-buildsrc.html shows * creating vignettes ... ERROR ... Error: processing vignette ?DirichletMultinomial.Rnw? failed with diagnostics: chunk 21 (label

Hello, I am writing a package called 'DLM' containing a vignette. The vignette contains a chunck with the function call 'library(DLM)'. This worked fine with 'R CMD check DLM', but when it comes to building the package with 'R CMD build DLM' I get the following error message: * creating vignettes ... ERROR Error: chunk 1 Error in library(DLM) : There is no

I'm having a problem rebuilding a package, new to me in R 2.15.0 (Linux) It hits all that contain the line \usepackage[pdftex]{graphics} and leads to the following when running R CMD check on the directory. (I do this often; a final run on the tar.gz file will happen before submission.) Since I float and resize my figures, removing the line is fatal in other ways.

I've been having problems building vignettes in bioconductor packages with R-devel. Turns out that Rdevel/share/texmf/hyperref.cfg wants Blue and Red predefined, when only blue and red are defined (as of rsync Rdevel, Sept 10th). This is on a Debian unstable system (Sept 9th version). Might not apply to all other tetex systems. Seems to have bitten the bioconductor build system, though.

I am currently writing a (private) package in which I produce pdf files from within R using LaTeX. To do so I mainly copied some lines from the buildVignettes() function in the tools package. This uses the texi2dvi which is included in R's bin directory: system(paste(file.path(R.home(), "bin", "texi2dvi"), "--quiet --pdf", bft)) This runs

On page 11 of the Extensions manual it says that "R CMD build will automatically create PDF versions of the vignettes for distribution" however, I have not been successful on Windows 2.0.1 beta. I tried creating a simple package by entering the code in the ?package.skeleton example then adding the Rnw file from the utils package to AnExample\inst\doc but when I ran R CMD build it

Dear All, I have been checking the metafor package against R-devel. R CMD check --as-cran metafor yields one note: FOSS licence with BuildVignettes: false Yes, I have 'BuildVignettes: FALSE' in my DESCRIPTION file. I see at http://developer.r-project.org/blosxom.cgi/R-devel/NEWS: Tue, 25 Jun 2013 CHANGES IN R-devel UTILITIES 'R CMD check --as-cran' warns about a false

In a package 'vig' R CMD build vig (or tools::buildVignettes(dir="vig") with $ cat vig/vignettes/vig1.Rnw \documentclass{article} \begin{document} <<>>= x <- 1 @ \end{document} $ cat vig/vignettes/vig2.Rnw \documentclass{article} \begin{document} <<>>= x @ \end{document} produces vig2.pdf where x is defined with value 1 -- the vignettes share a build

(xposted to bioc-devel and r-devel as I feel it is relevant to both communities) As someone whose body of work is likely to consist mostly of infrastructural packages and research directly in computing I wholeheartedly agree with Kasper's suggestion that we as a community should work to provide and use package citations. I borrow heavily from existing work in terms of both concept and

Ben Bolstad experienced something odd while running R CMD check over a package of ours using r-devel (yesterday's fresh). He tracked down the problem to a vignette calling 'library(MASS)'. Please kindly ignore if this is a known (and temporary) issue. Laurent ----- Forwarded message from Ben Bolstad <bolstad@stat.berkeley.edu> ----- Return-Path:

Hi, I have the following error when building a package * creating vignettes ... ERROR Error: chunk 3 Error in pmatch(x, table, duplicates.ok) : argument is not of mode character Error in buildVignettes(dir = ".") : Error: chunk 3 Error in pmatch(x, table, duplicates.ok) : argument is not of mode character Execution halted I use R-2.0.1 under debian linux 2.6.9

I often use R CMD BATCH to run my files (e.g. script.R), and get the output recorded in script.Rout -- this is great. On my setup (R.2.3.0 on linux), if any plots are created, they get stored in Rplots.ps. This can get confusing if I have several batch scripts in one directory. I've written a simple shell script to rename Rplots.ps to e.g. script.Rout.ps so that later I can easily identify

I have packages where I know CRAN and other test platforms do not have all the resources to build the vignettes, for example, access to databases. Previously I think putting BuildVignettes: false in the DESCRIPTION file resolved this, by preventing CRAN checks from attempting to run the vignette code. (If it was not this, then there was some other magic I don't understand.) Now, when

Dear list, I have been checking my package ('analogue') using R2.13-0-alpha (details of exact svn version appended below) and the R CMD check procedure is generating an error rebuilding a vignette in the package, which raises a NOTE in the check. The log printed to screen during check shows: .... * checking re-building of vignettes ... NOTE Error in re-building vignettes: ... Error in

Dear lists: I am somewhat puzzled by the use of texi2dvi/pdflatex in R2.7.0. When building EBImage (bioconductor) with 2.7.0 I get the same error both in Windows and Linux, which reads the following: ** building package indices ... * DONE (EBImage) * creating vignettes ... ERROR /usr/bin/texi2dvi: pdflatex exited with bad status, quitting. Error in texi2dvi(file = bft, pdf = TRUE, clean =

Dear all, When running function 'testQAReport()', which uses function 'buildVignettes()' to create a pdf-file I get the following error: > source("testQAReport.R") > testQAReport() Error in .get_package_metadata(pkgdir) : Files 'DESCRIPTION' and 'DESCRIPTION.in' are missing. Since I did not get this error in earlier versions of R, could you

For people reading this: I was installing bzip2 by hand. Two things to bear in mind (1) it only installs a shared library if you use a special Makefile (this is clearly stated in the installation docs) and (2) I had to symlink libbz2.so.1 to libbz2.so.1.0.6 (the included libbz2.so.1.0 was not being picked up). Best, Kasper On Fri, Mar 27, 2015 at 11:19 AM, Kasper Daniel Hansen <