similar to: "Failed to locate the 'texi2pdf' output file"

Just thought I would mention that the issue below (and in https://stat.ethz.ch/pipermail/r-devel/2013-April/066318.html) is still not resolved. It hasn't been a big problem, but it potentially could be, if a critical package were to have this error on release day, then all its dependencies would fail to build, which would probably require us to postpone our release. See the complete thread

Hello, I'm seeing three different vignette-related errors with recent versions of R-3.0.0 alpha. First, with the package BitSeq (http://bioconductor.org/packages/2.12/bioc/html/BitSeq.html), I get the following when trying to build the package: Error: processing vignette ?BitSeq.Rnw' failed with diagnostics: Failed to locate the ?weave? output file (by engine ?utils::Sweave?) for

Hello, I have come across two separate packages that have a Makefile in inst/doc which use the R_HOME variable. In both cases, the path to R_HOME gets munged in such a way that commands that include R_HOME fail on Windows: For example, one Makefile, for the xmapcore package ( https://hedgehog.fhcrc.org/bioconductor/trunk/madman/Rpacks/xmapcore/username/password: readonly) has this:

Hi, Installing from binaries on Windows: > install.packages("multtest") Warning: dependency 'Biobase' is not available trying URL 'http://cran.fhcrc.org/bin/windows/contrib/2.12/multtest_2.6.0.zip' Content type 'application/zip' length 1645590 bytes (1.6 Mb) opened URL downloaded 1.6 Mb package 'multtest' successfully unpacked

Hi, Why isn't 'R CMD check --force-multiarch' installing the package for all the architectures that are going to be checked? For some packages, it only installs for the default arch ('i386'). Then testing the package for 'x64' fails. For example, Output of R CMD check --force-multiarch fabia_1.5.0.tar.gz: ----------------------------------------------------------- *

Hi, This is a follow up to: https://stat.ethz.ch/pipermail/r-devel/2010-July/057921.html The Bioconductor daily builds have been reporting a lot of strange things lately on Windows using R-2.12. This started 2 or 3 months ago and things are not getting better with recent R-2.12. Here is a sample from today's build results. We use Windows Server 2003 R2 for the 32-bit builds, Windows

Hi, The R-based version of R CMD build doesn't work for me on Windows: E:\biocbld\bbs-2.7-bioc>R\bin\R CMD build meat\Biobase * checking for file 'meat\Biobase/DESCRIPTION' ... OK * preparing 'Biobase': * checking DESCRIPTION meta-information ... OK * cleaning src * installing the package to re-build vignettes Warning in shell(sprintf("%s > %s

I am having a problem using two DLLs with the same name, but obviously located in different directories, in an R session. The troublesome package is the (Bioconductor) Rgraphviz package. It relies on (3rd party software) graphviz and imports functions from (Bioconductor) package graph. Unfortunately, the current stable release of graphviz for Windows

Hi, 'R CMD build' (with R 2.12.0 RC) fails to clean the src/ folder on Windows: D:\biocbld\bbs-2.7-bioc>ls meat/BUS/src BUS.cpp BUS.h D:\biocbld\bbs-2.7-bioc>R\bin\R CMD build meat\BUS * checking for file 'meat\BUS/DESCRIPTION' ... OK * preparing 'BUS': * checking DESCRIPTION meta-information ... OK * cleaning src * installing the package

Hi, On Windows, with last R-devel tarball (r40647) from ftp://ftp.stat.math.ethz.ch/Software/R/R-devel_2007-02-04.tar.gz I get the following build error: E:\biocbld\bbs-2.0-bioc\R\src\gnuwin32> make ... ... ---------- Making package utils ------------ adding build stamp to DESCRIPTION installing NAMESPACE file and metadata installing R files Error in namespaceExport(ns, exports) :

Dear all, To create a *.pdf file from a *.Rnw file I do: olddir <- getwd(); setwd(outdir); tryCatch({Sweave("QAReport.Rnw"); tools::texi2pdf("QAReport.tex", clean=TRUE) }, finally = setwd(olddir) ); This works fine, however 'clean=TRUE' does only work when: outdir <-

Hi, So in an interactive R session, R.home() returns the following: > R.home() [1] "D:/biocbld/bbs-3.2-bioc/R" However, if I call it from system2(), I get different results: > system2("R", "-q -e R.home()") > R.home() [1] "D:/biocbld/BBS-3~1.2-B/R" Similarly: > system2("R", "-q -e Sys.getenv('R_HOME')") >

I checked after this question popped up on Stackoverflow: https://stackoverflow.com/questions/44785961/compile-pdf-in-rstudio-works-but-knit2pdf-does-not-work-in-r-or-rstudio On Windows, texi2pdf looks for the texify.exe of Miktex, but looks in a very wrong place: > Sys.which("texify") texify

We are trying to setup a Windows server that will allow any of our users to build a binary R package given a source package. The idea is to have a central R installation and allow users to install packages to their own package library for the purposes of binary package building. It seems, however, that write access to $R_HOME is required as part of the install step even when -l is used to

Hi, On both Unix and Windows there is a mechanism to add variables to the environment when R is started. I noticed that, on Unix, this mechanism is not used when R is started normally at the command line but only when it's started using the 'R CMD' syntax. One problem with this is some lack of consistent cross-platform behaviour. For example: On Linux: $ echo $TEXINPUTS $

Hi, Today we've seen the following problem with the R-2.12 that we use for our Windows builds: > installed.packages() Error: subscript out of bounds After some investigation we discovered that the cause of this failure was that 1 of the 890 packages currently installed on the machine (Windows Server 2003 R2) had its DESCRIPTION file empty:

In the process of updating R to R 2.7 alpha or R 2.7 beta for the BioConductor 2.2 builds on Windows, I have hit a snag because the BioC build system has long path names (e.g. D:\biocbld\bbs-2.2-bioc\R) and these path names are not resolving properly by MiKTeX 2.7 during vignette construction. Take, for example, the attached vignette from Biobase, Bioconductor.Rnw. I have built R from source

Currently Makefiles for vignettes are only supported for .tex files. Could the tools package be modified to allow file extensions to be specified for a vignette engine? Having the pandoc pdf conversion in a Makefile rather than through R would be tidier in some cases. If I specify my vignette engine as ``` tools::vignetteEngine( 'myengine', pattern = '\\.[Rr](md|nw)$',

If I understand correctly, all vignettes in a package are built in the same R process. Global options, loaded packages, etc., in an earlier vignette persist in later vignettes. This can introduce user confusion (e.g., when a later vignette builds successfully because a package is require()'ed in an earlier vignette, but not the current one), difficult-to-identify bugs (e.g., when a setting

On Wed, Aug 13, 2008 at 6:56 AM, Laurent Gautier <lgautier@gmail.com> wrote: > There is a chance that further changes in the handling of plotting > devices event appear; > I think that there is an ongoing effort to bring new features for R-2.8. > > What about bumping that to r-devel ? (Sorry if you already did and I missed > it). > The solution you came up with could be