Re: [R-pkg-devel] function name conflict problem

2020-02-04 Thread Hugh Parsonage
Package karon is the problem. Is that package in your depends or imports? Does that package use Depends? On Wed, 5 Feb 2020 at 8:24 am, wrote: > In trying to develop a package to be submitted to CRAN, when I do Install > and Reload or devtools::check(), I get the warning: > > > > Warning: replac

Re: [R-pkg-devel] Warning: parse error in file 'Rraven-Ex.R'

2020-02-04 Thread Jeff Newmiller
In your examples. On February 4, 2020 5:53:08 PM PST, Marcelo Araya Salas wrote: >Hi all > >I got this error from CRAN tests: > >Warning: parse error in file 'Rraven-Ex.R': >'\.' is an unrecognized escape in character string starting ""\." > >However, I can't find the original file where the err

[R-pkg-devel] Warning: parse error in file 'Rraven-Ex.R'

2020-02-04 Thread Marcelo Araya Salas
Hi all I got this error from CRAN tests: Warning: parse error in file 'Rraven-Ex.R': '\.' is an unrecognized escape in character string starting ""\." However, I can't find the original file where the error is found. I have try unsuccessfully for several hours :( any suggestions on how to find

Re: [R-pkg-devel] function name conflict problem

2020-02-04 Thread sierrastew
Thanks. I had seen this but it didn't register. I made this change to all the potential conflicts (the packages ellipse and mgcv are never in an @import statement), but I still get the conflict messages. John Karon From: Max Turgeon Sent: Tuesday, February 4, 2020 3:10 PM To: sierras...@mi

Re: [R-pkg-devel] function name conflict problem

2020-02-04 Thread Max Turgeon
I find it's well explained in the book by Hadley Wickham: http://r-pkgs.had.co.nz/namespace.html#imports If package ellipse is in Imports (in your DESCRIPTION file), then install.packages will make sure it's available on the user's system when installing your own package. Therefore you can wri

[R-pkg-devel] function name conflict problem

2020-02-04 Thread sierrastew
Thanks Duncan. Please clarify: if I use ellipse::ellipse in code, do I need to have @importFrom ellipse eliipse in the Roxygen code. -Original Message- From: Duncan Murdoch Sent: Tuesday, February 4, 2020 2:45 PM To: sierras...@mindspring.com Subject: Re: [R-pkg-devel] function name co

Re: [R-pkg-devel] function name conflict problem

2020-02-04 Thread Duncan Murdoch
On 04/02/2020 4:21 p.m., sierras...@mindspring.com wrote: In trying to develop a package to be submitted to CRAN, when I do Install and Reload or devtools::check(), I get the warning: Warning: replacing previous import 'ellipse::pairs' by 'graphics::pairs' when loading 'karon' Warning: rep

[R-pkg-devel] function name conflict problem

2020-02-04 Thread sierrastew
In trying to develop a package to be submitted to CRAN, when I do Install and Reload or devtools::check(), I get the warning: Warning: replacing previous import 'ellipse::pairs' by 'graphics::pairs' when loading 'karon' Warning: replacing previous import 'MVN::mvn' by 'mgcv::mvn' when loading

Re: [R-pkg-devel] 转发: [CRAN-pretest-archived] CRAN submission BAREB 1.0

2020-02-04 Thread Duncan Murdoch
The 00install.out file has this error message: unable to load shared object ‘/srv/hornik/tmp/CRAN/BAREB.Rcheck/00LOCK-BAREB/00new/BAREB/libs/BAREB.so’: /srv/hornik/tmp/CRAN/BAREB.Rcheck/00LOCK-BAREB/00new/BAREB/libs/BAREB.so: undefined symbol: dpotrf_ That name dpotrf_ looks like something

[R-pkg-devel] 转发: [CRAN-pretest-archived] CRAN submission BAREB 1.0

2020-02-04 Thread Yuliang Li
Hi all, I am trying to submit my R package to CRAN. However, I keep getting an error in the second link, saying my package could not be installed. But the package works perfectly fine in my personal computer. I would really appreciate it if you could provide some possible solution. Thanks in a

Re: [R-pkg-devel] Suggests in a Package

2020-02-04 Thread Roy Mendelssohn - NOAA Federal via R-package-devel
Thanks. And thanks for the tip. -Roy > On Feb 4, 2020, at 10:20 AM, Duncan Murdoch wrote: > > On 04/02/2020 1:13 p.m., Roy Mendelssohn - NOAA Federal via R-package-devel > wrote: >> Hi All: >> I still get a little confused on what it means if a package is listed in >> "Suggest" in my package

Re: [R-pkg-devel] Suggests in a Package

2020-02-04 Thread Duncan Murdoch
On 04/02/2020 1:13 p.m., Roy Mendelssohn - NOAA Federal via R-package-devel wrote: Hi All: I still get a little confused on what it means if a package is listed in "Suggest" in my package. I have been working to try and keep dependencies down. One of my packages produces maps with data, and I

[R-pkg-devel] Suggests in a Package

2020-02-04 Thread Roy Mendelssohn - NOAA Federal via R-package-devel
Hi All: I still get a little confused on what it means if a package is listed in "Suggest" in my package. I have been working to try and keep dependencies down. One of my packages produces maps with data, and I have been asked if the maps can be made interactive. It turns out this can be don

Re: [R-pkg-devel] r-hub status

2020-02-04 Thread brian knaus
Thank you Gabor! I've posted an issue. https://github.com/r-hub/rhub/issues/338 Thank you Bill! I think the solution for this may be simple. But I wanted to make sure I could reproduce the warning so that I can validate that my fix resolves the issue. And thank you Uwe for all the work you do h

Re: [R-pkg-devel] r-hub status

2020-02-04 Thread Uwe Ligges
On 04.02.2020 18:21, William Dunlap wrote: CRAN's check gives a warning checking Rd \usage sections ... WARNING Documented arguments not in \usage in documentation object 'Process chromR objects': ‘...’ and man/proc_chromR.Rd on github does list '...' in the \arguments section but no fun

Re: [R-pkg-devel] r-hub status

2020-02-04 Thread William Dunlap
CRAN's check gives a warning checking Rd \usage sections ... WARNING Documented arguments not in \usage in documentation object 'Process chromR objects': ‘...’ and man/proc_chromR.Rd on github does list '...' in the \arguments section but no function listed in the \usage section uses '...'. T

Re: [R-pkg-devel] CXX14 not defined on Windows

2020-02-04 Thread Dirk Eddelbuettel
On 4 February 2020 at 17:51, Guido Kraemer wrote: | I am testing building a package on Windows. The package requires C++14. You will have to wait. The current Rtools is at g++ 4.9.3 which (barely) supports C++11. We all keep our fingers crossed as the replacement Rtools would bring g++ 8.*.

Re: [R-pkg-devel] r-hub status

2020-02-04 Thread Gábor Csárdi
This is the R-hub issue tracker: https://github.com/r-hub/rhub/issues Gabor On Tue, Feb 4, 2020 at 4:47 PM brian knaus wrote: > > Does anyone know the current status of r-hub? My package ( > https://github.com/knausb/vcfR) is throwing warnings on R-devel ( > https://cran.r-project.org/web/checks

[R-pkg-devel] CXX14 not defined on Windows

2020-02-04 Thread Guido Kraemer
I am testing building a package on Windows. The package requires C++14. I have installed the latest versions of R (3.6.2), RTools (3.5), and RStudio. The package builds fine under Linux. I get the following error: > devtools::install_github("gdkrmr/zarr-R") ...   C++14 standard reque

[R-pkg-devel] r-hub status

2020-02-04 Thread brian knaus
Does anyone know the current status of r-hub? My package ( https://github.com/knausb/vcfR) is throwing warnings on R-devel ( https://cran.r-project.org/web/checks/check_results_vcfR.html) and CRAN has asked me to fix it. Tried r-hub but it failed. https://builder.r-hub.io/status/vcfR_1.9.0.9000.ta

Re: [R-pkg-devel] new package processing time

2020-02-04 Thread Duncan Murdoch
On 04/02/2020 9:15 a.m., Marcelo Araya Salas wrote: Thanks I found it here: ftp://cran.r-project.org/incoming/archive/ not sure what that's suppose to mean That generally means that it has been rejected. The usual sequence of events is: You submit it, and an email comes to the maintainer

Re: [R-pkg-devel] new package processing time

2020-02-04 Thread Dirk Eddelbuettel
On 4 February 2020 at 08:15, Marcelo Araya Salas wrote: | I found it here: | | ftp://cran.r-project.org/incoming/archive/ | | not sure what that's suppose to mean "It's dead." It generally means you will have gotten an email with the reasoning. But whatever is in archive/ is no longer proces

Re: [R-pkg-devel] new package processing time

2020-02-04 Thread Ben Bolker
Also a vote for the foghorn::cran_incoming() function. "archive" means your package was rejected. If you don't know why/didn't receive an e-mail, you might have to e-mail CRAN maintainers for clarification. • Hornik, Ligges and Zeileis. "Changes on CRAN: 2017-12-01 to 2018-06-30"

Re: [R-pkg-devel] new package processing time

2020-02-04 Thread Marcelo Araya Salas
Thanks I found it here: ftp://cran.r-project.org/incoming/archive/ not sure what that's suppose to mean Marcelo El mar., 4 feb. 2020 a las 8:12, Dirk Eddelbuettel () escribió: > > On 4 February 2020 at 10:28, Helmut Schütz wrote: > | Possibly it went unnoticed. > > A follow-up email may be a

Re: [R-pkg-devel] Fwd: LICENSE file in package including third party library

2020-02-04 Thread Dirk Eddelbuettel
On 4 February 2020 at 15:04, GD wrote: | I have a very specific question regarding the licensing of my R package. | | Here is the details: I have an R package under the MIT license so the | DESCRIPTION file contains the field `License: MIT + file LICENSE` and | the LICENSE file contains the foll

Re: [R-pkg-devel] new package processing time

2020-02-04 Thread Dirk Eddelbuettel
On 4 February 2020 at 10:28, Helmut Schütz wrote: | Possibly it went unnoticed. A follow-up email may be a good idea. | My first new package took two days from submission to acceptance | including answering questions in July last year. It is _much_ more clogged now as you can tell via a quick

[R-pkg-devel] Fwd: LICENSE file in package including third party library

2020-02-04 Thread GD
Hi, I have a very specific question regarding the licensing of my R package. Here is the details: I have an R package under the MIT license so the DESCRIPTION file contains the field `License: MIT + file LICENSE` and the LICENSE file contains the following required fields: ``` YEAR: COPYRIG

Re: [R-pkg-devel] new package processing time

2020-02-04 Thread Helmut Schütz
Hi Marcelo, Marcelo Araya Salas wrote on 2020-02-04 00:56: I submitted a new package to CRAN a couple of weeks ago. Does anyone know how long does it take for the package to be processed? New package versions are usually processed in a few hours so that's why I am wondering if everything is fine