search for: altcdfenv

Hi, After updating R-2.12 on the Bioconductor build system about 1 week ago (we update R every 4-6 weeks for our devel builds), we've started to see something never seen before on Windows: for some BioC packages, 'R CMD build' would produce no output at all (0 byte) and, of course, no source tarball. Even though, the code returned by the command is 0! See an example of this is here:

I have recently upgraded to Ubuntu Gutsy and, for the first time, am using a 64-bit installation. After failing miserably to install R from source, not a problem for me in the past with a 32-bit install, I went the route of using the Debian Etch build. This went smoothly, but I am unable to update my numerous R and BioConductor packages, getting non-zero exit status errors on each package. Is