similar to: 'R CMD build' not cleaning the src/ folder on Windows

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:

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, 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

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, Every day a few Bioconductor packages (different ones each day) fail to build, on Windows only, with an error like this: D:\biocbld\bbs-2.13-bioc\meat>D:\biocbld\bbs-2.13-bioc\R\bin\R.exe CMD build --keep-empty-dirs --no-resave-data OrganismDbi [...] Error in find_vignette_product(name, by = "texi2pdf", engine = engine) : Failed to locate the 'texi2pdf' output file (by

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

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 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:

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

With several versions of R 2.12.0 I have been seeing this when running R CMD build Rcpp from the SVN sources: [...] Transcript written on Rd2.log. Saving output to '/home/edd/svn/rcpp/pkg/Rcpp/build/Rcpp.pdf' ... Warning in file.create(to[okay]) : cannot create file '/home/edd/svn/rcpp/pkg/Rcpp/build/Rcpp.pdf', reson 'No such file or directory' Done

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) :

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

When running make check-all on R-1.9.0beta (2004-03-31) built with pgf77/gcc/g++ on the Opteron (running SLES8), I get four warnings about not finding the DESCRIPTION files for the packages in the VR bundle; e.g., cannot open file `/u1/scratch/R-1.9.0/tests/Packages/VR/spatial/DESCRIPTION' Error in tools:::.checkPackageDepends(dir = "/u1/scratch/R-1.9.0/tests/Packages/VR/spatial")

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, 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')") >

Hi, I have an input data > dput (input) structure(list(ScanDate = structure(c(16433, 16440, 16447, 16454, 16461, 16468, 16475, 16482, 16489, 16496, 16503, 16510, 16517, 16524, 16531, 16538, 16545, 16552, 16559, 16566, 16573, 16580, 16587, 16594, 16601, 16608, 16615, 16622), class = "Date"), OnPromotion = c(0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 1, 1, 1, 1, 1, 1, 0, 1, 1, 1, 1, 0, 0, 0, 1,

On Wed, Mar 07, 2007 at 11:22:36PM +0000, olly wrote: > docs/Makefile.am: Stop shipping docs/apidoc/latex/* in the > xapian-core tarballs since it's just useless bloat. Removing it > more than halves the size of the tarball (55% reduction!) Hmm, this is very odd. I tried unpacking the last xapian-core snapshot tarball, deleting the junk files, and rebuilding the tarball, and I got

Full_Name: Jarno Tuimala Version: 2.3.1 OS: Solaris / Linux Submission from: (NULL) (193.166.2.98) Today I downloaded the latest source code release R-2.3.1.tar.gz, and it seems not to contain the VR bundle. After running ./configure I get the following error message: checking for recommended packages... ./src/library/Recommended/VR_*.tar.gz: No such file or directory no configure: error: Some

Hi, The current implementation for utils::tar() seems to generate broken tarballs when some of the files to include in the tarball are >= 2GB. For example, when running 'R CMD build' on a big Bioconductor data package, we see this warning: * checking for file ?ChIPXpressData/DESCRIPTION? ... OK * preparing ?ChIPXpressData?: * checking DESCRIPTION meta-information ... OK *