[Rd] R CMD build/check Documentation in Writing R Extensions 1.3

Hi, In WRE section 1.3, there is a note that says "R CMD check and R CMD build run R processes with --vanilla in which none of the user’s startup files are read." While this is true, is it somewhat confusing? When reading quickly, it is possible to read that statement as "running R CMD check is

Re: [Rd] R CMD build should fail early for old package versions?

On 30/09/2019 5:25 p.m., Toby Hocking wrote: Hi all, Today I had an R CMD build that failed while building a vignette because the vignette needs tidyr (>= 1.0, declared in DESCRIPTION Suggests) but my system had a previous version installed. It did not take me too long to figure out the issue

[Rd] R CMD build should fail early for old package versions?

Hi all, Today I had an R CMD build that failed while building a vignette because the vignette needs tidyr (>= 1.0, declared in DESCRIPTION Suggests) but my system had a previous version installed. It did not take me too long to figure out the issue (solved by upgrading tidyr) but it would have

[Rd] R CMD build installing the package to process help pages

Dear All, If a package has dynamic manual pages (i.e. `\Sexpr{} macros), then R CMD build installs the package, and (by default) creates the PDF manual. I understand that this is needed for build-time Sexprs. Could anyone explain me why `R CMD build` needs to install the package if all the

Re: [Rd] R CMD build then check fails on R-devel due to serialization version

An update on the adoption of serialization format 3: R 3.5.0 (released yesterday) supports serialization format 3, but the default is still format 2 to make the transition easier. It is expected that the default will soon be changed to 3 in R-devel. Packages thus must not depend on what is

Re: [Rd] R CMD build then check fails on R-devel due to serialization version

To reduce difficulties for people relying on automated tests set up to build&"check --as-cran" using R-devel (e.g. travis-ci), the default serialization version has been temporarily switched back to 2. Thank you for your patience - according to svn history, the last change of the serialization

Re: [Rd] R CMD build then check fails on R-devel due to serialization version

As things stand now, package tarballs with vignettes that are built with R-devel will not install in R 3.4.x, so CRAN can't accept them and someone running R CMD check --as-cran should be told that. A WARNING is appropriate. Most likely what will change soon is that build/version.rds will be

Re: [Rd] R CMD build then check fails on R-devel due to serialization version

This change poses difficulties for automated build systems such as travis-ci, which is widely used in the R community. In particular because this is a WARNING and not a NOTE this causes all R-devel builds with vignettes to fail, as the default settings fail the build if R CMD check issues a

Re: [Rd] R CMD build then check fails on R-devel due to serialization version

On 10/01/2018 1:26 PM, Neal Richardson wrote: Hi, Since yesterday I'm seeing `R CMD check --as-cran` failures on the R-devel daily build (specifically, R Under development (unstable) (2018-01-09 r74100)) for multiple packages: * checking serialized R objects in the sources ... WARNING Found

[Rd] R CMD build then check fails on R-devel due to serialization version

Hi, Since yesterday I'm seeing `R CMD check --as-cran` failures on the R-devel daily build (specifically, R Under development (unstable) (2018-01-09 r74100)) for multiple packages: * checking serialized R objects in the sources ... WARNING Found file(s) with version 3 serialization:

[Rd] R CMD build errors if files cannot be moved, even if they are in Rbuildignore

When a package is built it is first moved to a temporary directory (lines 962-980 in build.R). However, this moves *all* files to the temporary directory, even those in Rbuildignore; only later (lines 997-1024) are Rbuildignore files excluded. The problem with this approach is that some files in

Re: [Rd] R CMD build error during vignettes build

On Wed, 22 Feb 2017 12:22:45 +0200, Mikko Korpela wrote: [...] > When trying to build the vignette from the git version of your package > (as part of R CMD build), I see the same error message. Investigating > further, the "tangled" file diveMove.R from >

Re: [Rd] R CMD build error during vignettes build

On 21/02/17 19:06, Sebastian P. Luque wrote: Hello, I'm trying to rebuild a package (using R version 3.3.2 (2016-10-31)) that has not seen any changes since it was last built without problems in previous R versions. It fails during vignette building with: ---

[Rd] R CMD build error during vignettes build

Hello, I'm trying to rebuild a package (using R version 3.3.2 (2016-10-31)) that has not seen any changes since it was last built without problems in previous R versions. It fails during vignette building with: ------ $ R CMD

[Rd] R CMD build failure

I have a local library 'dart' that imports httr. It has routines that access central patient data such as birth date, so it is heavily used locally but of no interest to anyone else. The httr library (and 300 others) are in a shared directory, referenced by everyone in the biostatistics

Re: [Rd] R CMD build failure

What field is httr in the DESCRIPTION? Hadley On Thu, Jul 9, 2015 at 10:26 AM, Therneau, Terry M., Ph.D. thern...@mayo.edu wrote: I have a local library 'dart' that imports httr. It has routines that access central patient data such as birth date, so it is heavily used locally but of no

Re: [Rd] R CMD build failure

On Thu, Jul 9, 2015 at 12:26 PM, Therneau, Terry M., Ph.D. thern...@mayo.edu wrote: I have a local library 'dart' that imports httr. It has routines that access central patient data such as birth date, so it is heavily used locally but of no interest to anyone else. The httr library (and 300

Re: [Rd] R CMD build failure

On Thu, 9 Jul 2015, Therneau, Terry M., Ph.D. wrote: I have a local library 'dart' that imports httr. [snip `R CMD build' can't find dart] Any ideas? There is no mention in the Writing R Extentions manual that it ignores the Rprofile file. Terry, From WRE: 1.3 Checking and

Re: [Rd] R CMD build failure

Depends: httr (= 0.6), XML in the DESCRIPTION file import(httr, XML) in NAMESPACE Per your question I just tried changing Depends to Imports, it didn't make a change. Terry T. On 07/09/2015 12:33 PM, Hadley Wickham wrote: What field is httr in the DESCRIPTION? Hadley On Thu, Jul 9, 2015

Re: [Rd] R CMD build looking for texi2dvi in the wrong place (R-devel)

Dan, On Jan 12, 2015, at 7:50 PM, Dan Tenenbaum dtene...@fredhutch.org wrote: R CMD build fails with recent R-devel because it is looking for texi2dvi in /usr/local/bin, but on this system, MacTex has installed it in /usr/bin. No, you're looking at the wrong package - texi2dvi comes from

[Rd] R CMD build looking for texi2dvi in the wrong place (R-devel)

R CMD build fails with recent R-devel because it is looking for texi2dvi in /usr/local/bin, but on this system, MacTex has installed it in /usr/bin. $ R CMD build IRanges * checking for file 'IRanges/DESCRIPTION' ... OK * preparing 'IRanges': * checking DESCRIPTION meta-information ... OK *

Re: [Rd] R CMD build looking for texi2dvi in the wrong place (R-devel)

- Original Message - From: Duncan Murdoch murdoch.dun...@gmail.com To: Dan Tenenbaum dtene...@fredhutch.org, Simon Urbanek simon.urba...@r-project.org Cc: R-devel r-devel@r-project.org Sent: Monday, January 12, 2015 8:40:07 PM Subject: Re: [Rd] R CMD build looking for texi2dvi

Re: [Rd] R CMD build looking for texi2dvi in the wrong place (R-devel)

On 12/01/2015 6:26 PM, Dan Tenenbaum wrote: - Original Message - From: Simon Urbanek simon.urba...@r-project.org To: Dan Tenenbaum dtene...@fredhutch.org Cc: R-devel r-devel@r-project.org Sent: Monday, January 12, 2015 5:50:35 PM Subject: Re: [Rd] R CMD build looking for texi2dvi

Re: [Rd] R CMD build/check on Windows 7

If of any value/FYI, this seems to be related to my R-devel post 'R devel [and R 2.14.1 patched]: R CMD build now sources ~/.Rprofile': https://stat.ethz.ch/pipermail/r-devel/2012-February/063365.html /Henrik On Tue, Jul 17, 2012 at 7:48 PM, Bert Gunter gunter.ber...@gene.com wrote: Folks:

Re: [Rd] R CMD build - will reset the timestamps of all files in a package

Valentin Todorov valentin.todo...@chello.at on Tue, 25 Oct 2011 14:34:21 -0700 writes: After half a year of silence on this issue I would dare ask again: is this intended, why and how can I avoid it? Best regards, Valentin ... I wonder why (R version 2.13.0 and

Re: [Rd] R CMD build - will reset the timestamps of all files in a package

After half a year of silence on this issue I would dare ask again: is this intended, why and how can I avoid it? Best regards, Valentin ... I wonder why (R version 2.13.0 and after) the command R CMD build sets the timestamp of all files in the package to the current date/time. This seems not

[Rd] R CMD build - will reset the timestamps of all files in a package

Dear developers, I wonder why (R version 2.13.0 and after) the command R CMD build sets the timestamp of all files in the package to the current date/time. This seems not to be mentioned in the list of changes. Is there an option to avoid this? Best regards, Valentin

Re: [Rd] R CMD build processes inst/doc/Makefile only if there are vignette files?

On 11-04-29 10:36 PM, Prof Brian Ripley wrote: On Fri, 29 Apr 2011, Hervé Pagès wrote: On 11-03-30 01:55 AM, Prof Brian Ripley wrote: What R CMD build (and check) does is to call tools::buildVignettes. That has been true for a while, and buildVignettes() returns if no vignettes are found. The

Re: [Rd] R CMD build processes inst/doc/Makefile only if there are vignette files?

On 11-03-30 01:55 AM, Prof Brian Ripley wrote: What R CMD build (and check) does is to call tools::buildVignettes. That has been true for a while, and buildVignettes() returns if no vignettes are found. The docs are out-of-date. My view is that you are misusing inst/doc: it is intended *only*

Re: [Rd] R CMD build processes inst/doc/Makefile only if there are vignette files?

On Fri, 29 Apr 2011, Hervé Pagès wrote: On 11-03-30 01:55 AM, Prof Brian Ripley wrote: What R CMD build (and check) does is to call tools::buildVignettes. That has been true for a while, and buildVignettes() returns if no vignettes are found. The docs are out-of-date. My view is that you are

Re: [Rd] R CMD build --resave-data

Hervé Pagès hpa...@fhcrc.org on Tue, 12 Apr 2011 22:21:58 -0700 writes: On 11-04-12 07:06 PM, Simon Urbanek wrote: On Apr 12, 2011, at 8:53 PM, Hervé Pagès wrote: Hi Uwe, On 11-04-11 08:13 AM, Uwe Ligges wrote: On 11.04.2011 02:47,

Re: [Rd] R CMD build --resave-data

On 13.04.2011 02:53, Hervé Pagès wrote: Hi Uwe, On 11-04-11 08:13 AM, Uwe Ligges wrote: On 11.04.2011 02:47, Hervé Pagès wrote: Hi, More about the new --resave-data option As mentioned previously here https://stat.ethz.ch/pipermail/r-devel/2011-April/060511.html 'R CMD build' and 'R

Re: [Rd] R CMD build --resave-data

Hi Uwe, On 11-04-13 10:50 AM, Uwe Ligges wrote: On 13.04.2011 02:53, Hervé Pagès wrote: Hi Uwe, On 11-04-11 08:13 AM, Uwe Ligges wrote: On 11.04.2011 02:47, Hervé Pagès wrote: Hi, More about the new --resave-data option As mentioned previously here

Re: [Rd] R CMD build --resave-data

Hi Uwe, On 11-04-11 08:13 AM, Uwe Ligges wrote: On 11.04.2011 02:47, Hervé Pagès wrote: Hi, More about the new --resave-data option As mentioned previously here https://stat.ethz.ch/pipermail/r-devel/2011-April/060511.html 'R CMD build' and 'R CMD INSTALL' handle this new option

Re: [Rd] R CMD build --resave-data

If you deliberately ignore the fact that 'R CMD INSTALL' is also used by developers to install from the *package source tree* (by opposition to end users who use it to install from a *source tarball*, .. for a good reason, IMHO no serious developer would do that for obvious reasons - you'd

Re: [Rd] R CMD build --resave-data

On 11-04-12 07:06 PM, Simon Urbanek wrote: On Apr 12, 2011, at 8:53 PM, Hervé Pagès wrote: Hi Uwe, On 11-04-11 08:13 AM, Uwe Ligges wrote: On 11.04.2011 02:47, Hervé Pagès wrote: Hi, More about the new --resave-data option As mentioned previously here

Re: [Rd] R CMD build now removes empty dirs

Pages, Herve hpa...@fhcrc.org on Tue, 29 Mar 2011 23:56:47 -0700 (PDT) writes: Hi, It's unfortunate that with recent revisions of R 2.13 (this appeared in revision 54640, March 2), 'R CMD build' now removes empty dirs in the package. People might have good reasons for

Re: [Rd] R CMD build --resave-data

On 11.04.2011 02:47, Hervé Pagès wrote: Hi, More about the new --resave-data option As mentioned previously here https://stat.ethz.ch/pipermail/r-devel/2011-April/060511.html 'R CMD build' and 'R CMD INSTALL' handle this new option inconsistently. The former does --resave-data=gzip by

Re: [Rd] R CMD build now removes empty dirs

Hi Henrik, Just to clarify, you still have the ability of installing directory structures that are partly empty. Actually 'R CMD INSTALL pkgpath/' does this. And if srctarball.tar.gz contains empty dirs, 'R CMD INSTALL srctarball.tar.gz' will also keep them. The problem is that *by default* 'R

[Rd] R CMD build --resave-data

Hi, More about the new --resave-data option As mentioned previously here https://stat.ethz.ch/pipermail/r-devel/2011-April/060511.html 'R CMD build' and 'R CMD INSTALL' handle this new option inconsistently. The former does --resave-data=gzip by default. The latter doesn't seem to support

[Rd] R CMD build processes inst/doc/Makefile only if there are vignette files?

Hi, in Section 'Writing package vignettes' of 'Writing R Extensions' it says: Whenever a Makefile is found, then R CMD build will try to run make after the Sweave runs, so PDF manuals can be created from arbitrary source formats (plain LaTeX files, ...). [...] Note that the make step is executed

[Rd] R CMD build now removes empty dirs

Hi, It's unfortunate that with recent revisions of R 2.13 (this appeared in revision 54640, March 2), 'R CMD build' now removes empty dirs in the package. People might have good reasons for having empty dirs in their packages. For example, in Bioconductor, we have some tools to automatically

Re: [Rd] R CMD build processes inst/doc/Makefile only if there are vignette files?

What R CMD build (and check) does is to call tools::buildVignettes. That has been true for a while, and buildVignettes() returns if no vignettes are found. The docs are out-of-date. My view is that you are misusing inst/doc: it is intended *only* for files which are going to be installed and

Re: [Rd] R CMD build now removes empty dirs

I am also in favor for keeping the ability of installing directory structures that are partly empty. I've used it before to setup templates that can conveniently be copied recursively to a local path. I did noticed that R CMD INSTALL gave a warning about empty directories before (or was it a

[Rd] R CMD build error (RProtoBuf on windows)

Hello all, I am trying to port the package RProtoBuf to windows. The developers of RProtoBuf have given me some helpful pointers so far, but now I am stuck. After having made what I think are the necessary changes to the package to compile on windows, R CMD build RProtoBuf outputs a somewhat

Re: [Rd] R CMD build error (RProtoBuf on windows)

On Fri, 25 Feb 2011, Koert Kuipers wrote: Hello all, I am trying to port the package RProtoBuf to windows. The developers of RProtoBuf have given me some helpful pointers so far, but now I am stuck. After having made what I think are the necessary changes to the package to compile on

Re: [Rd] 'R CMD build' not cleaning the src/ folder on Windows

This problems seems to be solved in current R 2.12 RC. Thanks! H. On 10/10/2010 10:47 PM, Hervé Pagès wrote: Hi, 'R CMD build' (with R 2.12.0 RC) fails to clean the src/ folder on Windows: D:\biocbld\bbs-2.7-biocls meat/BUS/src BUS.cpp BUS.h D:\biocbld\bbs-2.7-biocR\bin\R CMD build meat\BUS

[Rd] 'R CMD build' not cleaning the src/ folder on Windows

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

Re: [Rd] R CMD build cannot create vignettes on Windows if Makefile is used

Oops, sorry for the noise but after looking at today's BioC build/check results, I realize the problem is still here. At least for some of the 8 packages that had an 'R CMD build' timeout because of the Sweave.sty file not being found. I just happened to run 'R CMD build' by hands yesterday on a

Re: [Rd] R CMD build cannot create vignettes on Windows if Makefile is used

Duncan, On 09/13/2010 11:47 AM, Duncan Murdoch wrote: On 13/09/2010 2:38 PM, Hervé Pagès wrote: [...] Thanks for suggesting workarounds but don't you think there is a real problem? As I said, we don't use TEXINPUTS on Windows, we use the command line version. I didn't write the code, so I

Re: [Rd] R CMD build cannot create vignettes on Windows if Makefile is used

On 14/09/2010 2:46 PM, Hervé Pagès wrote: Duncan, On 09/13/2010 11:47 AM, Duncan Murdoch wrote: On 13/09/2010 2:38 PM, Hervé Pagès wrote: [...] Thanks for suggesting workarounds but don't you think there is a real problem? As I said, we don't use TEXINPUTS on Windows, we use the

Re: [Rd] R CMD build cannot create vignettes on Windows if Makefile is used

Hervé Pagès wrote: Hi Duncan, On 09/12/2010 05:07 AM, Duncan Murdoch wrote: On 12/09/2010 12:49 AM, Hervé Pagès wrote: Hi Duncan, On 09/11/2010 03:56 AM, Duncan Murdoch wrote: On 11/09/2010 12:52 AM, Hervé Pagès wrote: Hi, I found the following problem with recent

Re: [Rd] R CMD build cannot create vignettes on Windows if Makefile is used

On 13/09/2010 2:38 PM, Hervé Pagès wrote: On 09/13/2010 03:34 AM, Duncan Murdoch wrote: Hervé Pagès wrote: Hi Duncan, On 09/12/2010 05:07 AM, Duncan Murdoch wrote: On 12/09/2010 12:49 AM, Hervé Pagès wrote: Hi Duncan, On 09/11/2010 03:56 AM, Duncan Murdoch wrote: On 11/09/2010

Re: [Rd] R CMD build cannot create vignettes on Windows if Makefile is used

On 09/13/2010 03:34 AM, Duncan Murdoch wrote: Hervé Pagès wrote: Hi Duncan, On 09/12/2010 05:07 AM, Duncan Murdoch wrote: On 12/09/2010 12:49 AM, Hervé Pagès wrote: Hi Duncan, On 09/11/2010 03:56 AM, Duncan Murdoch wrote: On 11/09/2010 12:52 AM, Hervé Pagès wrote: Hi, I found the

Re: [Rd] R CMD build cannot create vignettes on Windows if Makefile is used

On 12/09/2010 12:49 AM, Hervé Pagès wrote: Hi Duncan, On 09/11/2010 03:56 AM, Duncan Murdoch wrote: On 11/09/2010 12:52 AM, Hervé Pagès wrote: Hi, I found the following problem with recent R-devel (2010-08-26 r52817) on Windows (32-bit and 64-bit): 'R CMD build pkg' gets stalled during

Re: [Rd] R CMD build cannot create vignettes on Windows if Makefile is used

Hi Duncan wouldn't it be possible that by default the Sweave.sty in share/texmf is found by 'R CMD build' for use by package vignettes without manual intervention? AfaIcs this is also how it worked in the past. Best wishes Wolfgang On Sep/11/10 12:56 PM, Duncan Murdoch wrote: On

Re: [Rd] R CMD build cannot create vignettes on Windows if Makefile is used

On 12/09/2010 12:04 PM, Wolfgang Huber wrote: Hi Duncan wouldn't it be possible that by default the Sweave.sty in share/texmf is found by 'R CMD build' for use by package vignettes without manual intervention? Yes, it does work that way. What Hervé is talking about are cases where people

Re: [Rd] R CMD build cannot create vignettes on Windows if Makefile is used

Hi Duncan, On 09/12/2010 05:07 AM, Duncan Murdoch wrote: On 12/09/2010 12:49 AM, Hervé Pagès wrote: Hi Duncan, On 09/11/2010 03:56 AM, Duncan Murdoch wrote: On 11/09/2010 12:52 AM, Hervé Pagès wrote: Hi, I found the following problem with recent R-devel (2010-08-26 r52817) on Windows

Re: [Rd] R CMD build cannot create vignettes on Windows if Makefile is used

On 11/09/2010 12:52 AM, Hervé Pagès wrote: Hi, I found the following problem with recent R-devel (2010-08-26 r52817) on Windows (32-bit and 64-bit): 'R CMD build pkg' gets stalled during vignette creation for packages that have a Makefile in pkg/inst/doc. It seems that the problem is that the

Re: [Rd] R CMD build cannot create vignettes on Windows if Makefile is used

Hi Duncan, On 09/11/2010 03:56 AM, Duncan Murdoch wrote: On 11/09/2010 12:52 AM, Hervé Pagès wrote: Hi, I found the following problem with recent R-devel (2010-08-26 r52817) on Windows (32-bit and 64-bit): 'R CMD build pkg' gets stalled during vignett creation for packages that have a

[Rd] R CMD build cannot create vignettes on Windows if Makefile is used

Hi, I found the following problem with recent R-devel (2010-08-26 r52817) on Windows (32-bit and 64-bit): 'R CMD build pkg' gets stalled during vignette creation for packages that have a Makefile in pkg/inst/doc. It seems that the problem is that the commands used in the Makefile for converting

Re: [Rd] R CMD build wiped my computer (from R-help)

Duncan Murdoch wrote: On 28/07/2010 8:10 PM, Ray Brownrigg wrote: NOTE: Now submitted to R-devel, as this seems more appropriate. I may have spoken too soon about this having been fixed. (see below). If I create another unusual but not 'invalid' filename in the R subdirectory, the

Re: [Rd] R CMD build wiped my computer (from R-help)

NOTE: Now submitted to R-devel, as this seems more appropriate. I may have spoken too soon about this having been fixed. (see below). If I create another unusual but not 'invalid' filename in the R subdirectory, the behaviour is different from that reported below, and is similar to the

Re: [Rd] R CMD build wiped my computer (from R-help)

On 28/07/2010 8:10 PM, Ray Brownrigg wrote: NOTE: Now submitted to R-devel, as this seems more appropriate. I may have spoken too soon about this having been fixed. (see below). If I create another unusual but not 'invalid' filename in the R subdirectory, the behaviour is different from that

[Rd] R CMD build wiped my computer

Hi, I ran R (version 2.9.0) CMD build under root in Fedora (9). When it tried to remove junk files it removed EVERYTHING in my local account! (See below). Can anyone tell me what happened, and even more importantly if I can I restore what was lost. Panickingly, Jarrod

Re: [Rd] R CMD build wiped my computer

Jarrod Hadfield j.hadfi...@ed.ac.uk on Tue, 27 Jul 2010 21:37:09 +0100 writes: Hi, I ran R (version 2.9.0) CMD build under root in Fedora (9). When it tried to remove junk files it removed EVERYTHING in my local account! (See below). Can anyone tell me what happened,

Re: [Rd] R CMD build wiped my computer

Hi Martin, I think this is the most likely reason given that the name in the DESCRIPTION file does NOT have a version number. Even so, it is very easy to misname a file and then delete it/change its name (as I've done here) and I hope current versions of R would not cause this problem.

Re: [Rd] 'R CMD build --binary BUNDLE' and Windows

It has only been fixed partly: 'Contains' fields with more than about 72 characters are 'corrupted' when the DESCRIPTION file is 'reformated' in the process from 'incomming' to 'http://cran.at.r-project.org/web/packages/' - or R (2.9.0) cannot handle 'contains' fields with more than one line.

Re: [Rd] 'R CMD build --binary BUNDLE' and Windows

c...@badsberg.eu wrote: 'R CMD build --binary BUNDLE' and Windows. When using R version 2.9.0 beta for 'R CMD build --binary CoCo' on Windows only the first package of the 'Contains' field of the bundle DESCRIPTION file ends up in the zip file. (Same result for the bundle 'VR' by R version

[Rd] 'R CMD build --binary BUNDLE' and Windows

'R CMD build --binary BUNDLE' and Windows. When using R version 2.9.0 beta for 'R CMD build --binary CoCo' on Windows only the first package of the 'Contains' field of the bundle DESCRIPTION file ends up in the zip file. (Same result for the bundle 'VR' by R version 2.9.0 beta.) The check

Re: [Rd] R CMD build on Vista

On Sun, 19 Oct 2008, Ollivier TARAMASCO wrote: Hello, I have R 2.7.2 and RTools 2.8 on a vista pro computer. On my computer R CMD build changes the file names : all capital letters are transformed into lowercase letters (for instance the DESCRIPTION file is changed in 'description'). What

Re: [Rd] R CMD build on Vista

Check what drives you have available on your system and what file system each uses. Click on Start button and type in System Information and then choose Components / Storage / Drives in the left side panel. That will report all your drives and their file system and other information. Try running

[Rd] R CMD build and et_EE.UTF-8 locale - invalid files (PR#10351)

Full_Name: Ott Toomet Version: 2.6.0, 2.5.x OS: debian etch, lenny Submission from: (NULL) (80.235.63.243) When building a package with 'R CMD build name_of_directory using et_EE.UTF-8 locale, I get the following: [EMAIL PROTECTED]:~/tyyq/econ/micEcon$ R CMD build trunk * checking for file

Re: [Rd] R CMD build and et_EE.UTF-8 locale - invalid files (PR#10351)

[EMAIL PROTECTED] wrote: Full_Name: Ott Toomet Version: 2.6.0, 2.5.x OS: debian etch, lenny Submission from: (NULL) (80.235.63.243) When building a package with 'R CMD build name_of_directory using et_EE.UTF-8 locale, I get the following: [EMAIL PROTECTED]:~/tyyq/econ/micEcon$ R CMD

[Rd] 'R CMD build' and file permissions

Hi, When building a source package on Linux with 'R CMD build', the files in the resulting tarball don't have the original permissions. The problem is that the packages I want to build include an SQLite data base (an .sqlite file) and, before I run 'R CMD build', I've made this file read-only

Re: [Rd] r cmd build

The Writing Extensions manual says to do an R CMD build for releases to CRAN. That's what I have been doing and that does produce a .tar.gz file even though I get a message about hhc.exe. Is that what I should continue to do and ignore the message or should I be using one of the alternatives you

Re: [Rd] r cmd build

Something should be added to the Writing Extensions manual since one gets this message during the R CMD build on Vista: hhc: not found CHM compile failed: HTML Help Workshop not installed? and one is not really sure if the result is ok or not -- it does say it FAILED. Even better would be to get

Re: [Rd] r cmd build

Gabor Grothendieck wrote: The Writing Extensions manual says to do an R CMD build for releases to CRAN. That's what I have been doing and that does produce a .tar.gz file even though I get a message about hhc.exe. Is that what I should continue to do and ignore the message or should I be

[Rd] r cmd build

On Windows Vista hhc.exe is not available. One can do this on an install: rcmd install --docs=normal myPackage to avoid the message about hhc.exe; however, rcmd build does not appear to support --docs=normal so one cannot do a build without getting a message about hhc.exe (although the build

Re: [Rd] R CMD build with mingw and msys (PR#9766)

On 29/06/2007 7:53 AM, [EMAIL PROTECTED] wrote: Full_Name: Steffen Version: 2-5-0 OS: Windows Submission from: (NULL) (192.124.243.162) Hi, the R CMD build script is using if($WINDOWS) { ## workaround for paths in Cygwin tar $filepath =~

[Rd] R CMD build fails with try(stop()) in vignette

A vignette in pkg/inst/doc with \documentclass[]{article} \begin{document} test= try(stop('err')) @ \end{document} produces an error with R CMD build pkg: ... ** building package indices ... * DONE (testPkg) * creating vignettes ... ERROR Error in try(stop(err)) : err This is not seen with

Re: [Rd] R CMD build fails with try(stop()) in vignette

It would appear that printing the error message to stderr() is what is causing the build to fail; replace try(stop('err')) with cat('Error in try(stop(err)) : err\n', file = stderr()) and I get the same failure. Best, luke On Wed, 11 Apr 2007, Martin Morgan wrote: A

Re: [Rd] R CMD build when the package name is different from the directory name

Dear Seth, Thank you for your message. On Thursday 28 September 2006 16:22, Seth Falcon wrote: Arne Henningsen [EMAIL PROTECTED] writes: Hi, I was really happy when I saw that in R version 2.3.0 R CMD check works for packages whose package name is different from the directory name in

Re: [Rd] R CMD build when the package name is different from the directory name

Arne Henningsen wrote: Dear Seth, Thank you for your message. On Thursday 28 September 2006 16:22, Seth Falcon wrote: Arne Henningsen [EMAIL PROTECTED] writes: Hi, I was really happy when I saw that in R version 2.3.0 R CMD check works for packages whose package name is different

[Rd] R CMD build when the package name is different from the directory name

Hi, I was really happy when I saw that in R version 2.3.0 R CMD check works for packages whose package name is different from the directory name in which it is located (see http://cran.r-project.org/src/base/NEWS). Now, I can have branches of my packages in directories like

Re: [Rd] R CMD build when the package name is different from the directory name

Another possibility is to store your code in svn or other version control system. On 9/28/06, Arne Henningsen [EMAIL PROTECTED] wrote: Hi, I was really happy when I saw that in R version 2.3.0 R CMD check works for packages whose package name is different from the directory name in which it

Re: [Rd] R CMD build when the package name is different from the directory name

Dear Gabor, Thank you for your message. On Thursday 28 September 2006 15:30, Gabor Grothendieck wrote: Another possibility is to store your code in svn or other version control system. Unfortunately, I can't see why this should make a difference for R CMD build. Do I miss something? The

Re: [Rd] R CMD build when the package name is different from the directory name

Arne Henningsen [EMAIL PROTECTED] writes: Hi, I was really happy when I saw that in R version 2.3.0 R CMD check works for packages whose package name is different from the directory name in which it is located (see http://cran.r-project.org/src/base/NEWS). Now, I can have branches of my

Re: [Rd] R CMD build when the package name is different from the directory name

I normally only keep one version locally since everything else can be retrieved, if needed, from the repository. If you do want to keep multiple versions locally then, of course, there is still a potential problem. On 9/28/06, Arne Henningsen [EMAIL PROTECTED] wrote: Dear Gabor, Thank you for

[Rd] R CMD build question

On Solaris when my package is built, I get the following result: creating vignettes ...Segmentation Fault - core dumped OK My question isn't why I get a segfault, but why does build return an OK after such an inauspicious event? Is build only supposed to error out if something more central to

Re: [Rd] R CMD build question

JimMcD == James W MacDonald [EMAIL PROTECTED] on Fri, 22 Sep 2006 11:28:48 -0400 writes: JimMcD On Solaris when my package is built, I get the following result: I don't think this is bound to Solaris at all. JimMcD creating vignettes ...Segmentation Fault - core dumped JimMcD

Re: [Rd] R CMD build says, 'Can't call method print'

This is a Perl scope problem on $log. For a quick fix, remove 'my' where it is defined (the real fix is to pass $log down, and I'll do that in the sources). On Sun, 23 Apr 2006, Seth Falcon wrote: Hi, While running R CMD build on one of the Bioc packages, I'm getting the following error

[Rd] R CMD build says, 'Can't call method print'

Hi, While running R CMD build on one of the Bioc packages, I'm getting the following error message * creating vignettes ... OK * cleaning src * removing junk files * checking for LF line-endings in source files Can't call method print on an undefined value at

[Rd] R CMD build: Subdirectory 'R' contains invalid file names

Hi, I get * excluding invalid files from 'R.oo' Subdirectory 'R' contains invalid file names: attachLocally.Object.Rex Exception.Rex extend.default.Rex InternalErrorException.reportBug.Rex Package.Rex Person.Rex Rdoc.Rex setMethodS3.Rex StaticFields.Rex when running R CMD build in R v2.3.0

Re: [Rd] R CMD build: Subdirectory 'R' contains invalid file names

Henrik Bengtsson writes: Hi, I get * excluding invalid files from 'R.oo' Subdirectory 'R' contains invalid file names: attachLocally.Object.Rex Exception.Rex extend.default.Rex InternalErrorException.reportBug.Rex Package.Rex Person.Rex Rdoc.Rex setMethodS3.Rex StaticFields.Rex

Re: [Rd] R CMD build: Subdirectory 'R' contains invalid file names

Hi, On 2/10/06, Kurt Hornik [EMAIL PROTECTED] wrote: Henrik Bengtsson writes: Hi, I get * excluding invalid files from 'R.oo' Subdirectory 'R' contains invalid file names: attachLocally.Object.Rex Exception.Rex extend.default.Rex InternalErrorException.reportBug.Rex Package.Rex

Re: [Rd] R CMD build: Subdirectory 'R' contains invalid file names

On Fri, 10 Feb 2006, Henrik Bengtsson wrote: Hi, On 2/10/06, Kurt Hornik [EMAIL PROTECTED] wrote: Henrik Bengtsson writes: Hi, I get * excluding invalid files from 'R.oo' Subdirectory 'R' contains invalid file names: attachLocally.Object.Rex Exception.Rex extend.default.Rex