Re: [R-pkg-devel] Note about "No repository set, so cyclic dependency check skipped"

2015-07-20 Thread Uwe Ligges
winbuilder will be fixed soon. Best, Uwe Ligges On 21.07.2015 06:23, Antonio José Saez Castillo wrote: All my attempts to do that have failed. That is because I tried to check in R-devel on win-builder site (win-builder.r-project.org), far from my local computer, and it got the same note. So,

Re: [R-pkg-devel] Note about "No repository set, so cyclic dependency check skipped"

2015-07-20 Thread Antonio José Saez Castillo
All my attempts to do that have failed. That is because I tried to check in R-devel on win-builder site (win-builder.r-project.org), far from my local computer, and it got the same note. So, I think it may be not a problem only in my own PC. 2015-07-20 12:25 GMT+02:00 Dirk Eddelbuettel : > > On 2

Re: [R-pkg-devel] Setting up R-devel in Linux Mint 17.1 64-bit

2015-07-20 Thread MAURICIO ZAMBRANO BIGIARINI
On 20 July 2015 at 20:29, peter dalgaard wrote: > Oi! > > Could you guys move to r-devel? This has nothing to do with _package_ > development. Thanks for the advice. I was not sure about the list I should have submitted this message, but looking at http://www.r-project.org/mail.html: R-package-

Re: [R-pkg-devel] recreating CRAN Testing environment

2015-07-20 Thread Uwe Ligges
On 20.07.2015 19:50, Jonathan Callahan wrote: I am (hopefully) at the end of a series of back-and-forth submissions of a package to the CRAN upload site. I have done my best to test things by: - using devtools Not needed at all. - running "R CMD check --as-cran" on the command lin

Re: [R-pkg-devel] Setting up R-devel in Linux Mint 17.1 64-bit

2015-07-20 Thread peter dalgaard
Oi! Could you guys move to r-devel? This has nothing to do with _package_ development. -Peter D > On 21 Jul 2015, at 00:49 , MAURICIO ZAMBRANO BIGIARINI > wrote: > > -- Forwarded message -- > From: Dirk Eddelbuettel > Date: 20 July 2015 at 19:21 > Subject: Re: [R-pkg-devel]

Re: [R-pkg-devel] Setting up R-devel in Linux Mint 17.1 64-bit

2015-07-20 Thread MAURICIO ZAMBRANO BIGIARINI
-- Forwarded message -- From: Dirk Eddelbuettel Date: 20 July 2015 at 19:21 Subject: Re: [R-pkg-devel] Setting up R-devel in Linux Mint 17.1 64-bit To: MAURICIO ZAMBRANO BIGIARINI Cc: Dirk Eddelbuettel , r-package-devel@r-project.org On 20 July 2015 at 18:56, MAURICIO ZAMBRANO

Re: [R-pkg-devel] Setting up R-devel in Linux Mint 17.1 64-bit

2015-07-20 Thread Dirk Eddelbuettel
On 20 July 2015 at 18:56, MAURICIO ZAMBRANO BIGIARINI wrote: | how can I be sure that I I enabled the shared library support ? edd@max:~/svn/r-devel$ ./configure --help | grep enable-R-sh --enable-R-shlibbuild the shared/dynamic library 'libR' [no] edd@max:~/svn/r-devel$ Make sure you

Re: [R-pkg-devel] Setting up R-devel in Linux Mint 17.1 64-bit

2015-07-20 Thread MAURICIO ZAMBRANO BIGIARINI
= "When the pupil is ready, the master arrives." (Zen proverb) = Linux user #454569 -- Linux Mint user On 20 July 2015 at 18:35, Dirk Eddelbuettel wrote: > > On 20 July 2015 at 18:05, MAURICIO ZAMBRANO BIGIARINI wrote: > | D

Re: [R-pkg-devel] Help needed to setting custom packages for R 3.1.2

2015-07-20 Thread Jennifer Bryan
Hi Sebastien, This note about Rd warnings reminded me that I recently had the same problem. So I recreated it and, I think, have found a solution. I will explain in my specific example to be clear. I need to link to the docs for the Token2.0 class from the httr package. First thing you try: \

Re: [R-pkg-devel] Setting up R-devel in Linux Mint 17.1 64-bit

2015-07-20 Thread Dirk Eddelbuettel
On 20 July 2015 at 18:05, MAURICIO ZAMBRANO BIGIARINI wrote: | Dear list, | | I'm trying to set up the development version of R (R-devel ) for | testing some packages before submitting them to CRAN. I'm using Linux | Mint 17.1 64-bit, which is an Ubuntu-based distro. | | I followed the advice of

[R-pkg-devel] Setting up R-devel in Linux Mint 17.1 64-bit

2015-07-20 Thread MAURICIO ZAMBRANO BIGIARINI
Dear list, I'm trying to set up the development version of R (R-devel ) for testing some packages before submitting them to CRAN. I'm using Linux Mint 17.1 64-bit, which is an Ubuntu-based distro. I followed the advice of Dirk on https://stat.ethz.ch/pipermail/r-sig-debian/2012-August/001935.html

Re: [R-pkg-devel] Help needed to setting custom packages for R 3.1.2

2015-07-20 Thread Hadley Wickham
On Mon, Jul 13, 2015 at 5:38 PM, Duncan Murdoch wrote: > On 13/07/2015 5:36 PM, Seth Wenchel wrote: >> Are you exporting the functions from pkgB and pkgC? It's hard to tell from >> your table below. The easiest way is to add a comment before each of the >> functions in pkgB and pkgC that you want

Re: [R-pkg-devel] Help needed to setting custom packages for R 3.1.2

2015-07-20 Thread sbihorel
Hi, Thanks to your suggestions and those of other responders, I was able to get rid of the warning messages returned during R CMD check. However I am still confused by the .Rd file-related warnings I get when we install the packages. For instance: Rd warning: /tmp/some/path/man/pkgC_functio

Re: [R-pkg-devel] recreating CRAN Testing environment

2015-07-20 Thread Jonathan Callahan
Thanks to all so far for excellent suggestions! On Mon, Jul 20, 2015 at 11:18 AM, Gábor Csárdi wrote: > On Mon, Jul 20, 2015 at 1:59 PM, Ben Bolker wrote: > [...] > >The most important thing that you haven't explicitly mentioned is > > to test on the most recent development version of R (ch

Re: [R-pkg-devel] recreating CRAN Testing environment

2015-07-20 Thread Gábor Csárdi
On Mon, Jul 20, 2015 at 1:59 PM, Ben Bolker wrote: [...] >The most important thing that you haven't explicitly mentioned is > to test on the most recent development version of R (check out via > Subversion/configure/make/make install from scratch). Can you adjust > your DigitalOcean settings

Re: [R-pkg-devel] recreating CRAN Testing environment

2015-07-20 Thread Dirk Eddelbuettel
Jonathan, On 20 July 2015 at 13:59, Ben Bolker wrote: | On 15-07-20 01:50 PM, Jonathan Callahan wrote: | > In an effort to save time and effort on both ends, can anyone | > advise on what I need to do to generate ALL the warning messages | > that the CRAN testing will find? | |The most impor

Re: [R-pkg-devel] recreating CRAN Testing environment

2015-07-20 Thread Avraham Adler
Even if you don't use Windows, it pays to submit your package to the Winbuilder test of buth R-release and R-devel. The error reports, if any, are often not-OS dependant and will serve as a good gaage as to how the real CRAN will respond. Avi On Mon, Jul 20, 2015 at 1:59 PM, Ben Bolker wrote: >

Re: [R-pkg-devel] recreating CRAN Testing environment

2015-07-20 Thread Ben Bolker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15-07-20 01:50 PM, Jonathan Callahan wrote: > I am (hopefully) at the end of a series of back-and-forth > submissions of a package to the CRAN upload site. > > I have done my best to test things by: > > - using devtools - running "R CMD check --as

[R-pkg-devel] recreating CRAN Testing environment

2015-07-20 Thread Jonathan Callahan
I am (hopefully) at the end of a series of back-and-forth submissions of a package to the CRAN upload site. I have done my best to test things by: - using devtools - running "R CMD check --as-cran" on the command line - checking my package on OSX, win-builder.R and various 32 and 64 bit

Re: [R-pkg-devel] Note about "No repository set, so cyclic dependency check skipped"

2015-07-20 Thread Dirk Eddelbuettel
On 20 July 2015 at 08:53, Martyn Plummer wrote: | On Mon, 2015-07-20 at 07:36 +0200, Antonio José Saez Castillo wrote: | > When checking a package I am getting | > | > * checking package dependencies ... NOTE | >No repository set, so cyclic dependency check skipped | > | > This is an old sou

Re: [R-pkg-devel] Note about "No repository set, so cyclic dependency check skipped"

2015-07-20 Thread Martyn Plummer
On Mon, 2015-07-20 at 07:36 +0200, Antonio José Saez Castillo wrote: > When checking a package I am getting > > * checking package dependencies ... NOTE >No repository set, so cyclic dependency check skipped > > This is an old source of discussion and I've found a lot of suggestions, > but no