Re: [R-pkg-devel] R package submission - C code does not compile

2018-12-06 Thread Uwe Ligges
Please resubmit, a hicc up on the check machine. Best, Uwe Ligges On 06.12.2018 19:29, Michael Kellermann wrote: Hi all, I'm attempting to submit an update of our eiPack package to CRAN. When I submitted it, it passed the Windows check with no problem (other than a note for a change in mainta

[R-pkg-devel] R package submission - C code does not compile

2018-12-06 Thread Michael Kellermann
Hi all, I'm attempting to submit an update of our eiPack package to CRAN. When I submitted it, it passed the Windows check with no problem (other than a note for a change in maintainer), but it failed almost immediately on the Debian check. The 00install.out file shows that it failed due to an i

Re: [R-pkg-devel] testing coercion

2018-12-06 Thread Kevin Coombes
Thanks for the suggestion. But it may not be quite expressive enough; I think I will instead use > ifelse(getRversion() < "3.6.0", > ! canCoerce(wv, "double"), # fails in older versions > canCoerce(wv, "double")) # works in newer versions That way, when I update the p

Re: [R-pkg-devel] New CRAN internet policy

2018-12-06 Thread Roy Mendelssohn - NOAA Federal via R-package-devel
--- Begin Message --- Thanks muchly. -Roy > On Dec 6, 2018, at 8:50 AM, Hadley Wickham wrote: > > Policies at https://cran.r-project.org/web/packages/policies.html > > Dirk Eddelbuettel has a CRAN policy watch where you can see the > changes: https://github.com/eddelbuettel/crp > > Hadley >

Re: [R-pkg-devel] testing coercion

2018-12-06 Thread Sebastian Meyer
Hi Kevin, I think using > canCoerce(wv, "double") || getRversion() < "3.6.0" could solve the issue of an inconsistent test result and is descriptive. Best regards, Sebastian Am 06.12.18 um 16:59 schrieb Kevin Coombes: > Hi, > > A package I recently submitted to CRAN includes an S4

Re: [R-pkg-devel] New CRAN internet policy

2018-12-06 Thread Hadley Wickham
Policies at https://cran.r-project.org/web/packages/policies.html Dirk Eddelbuettel has a CRAN policy watch where you can see the changes: https://github.com/eddelbuettel/crp Hadley On Thu, Dec 6, 2018 at 10:42 AM Roy Mendelssohn - NOAA Federal wrote: > > Hi All: > > Can someone point me to whe

Re: [R-pkg-devel] New CRAN internet policy

2018-12-06 Thread Roy Mendelssohn - NOAA Federal via R-package-devel
--- Begin Message --- Hi All: Can someone point me to where all the policies such as this one are posted. This may affect a package I have, and one problem I have is different people have differing ideas of what defines a "graceful" exit. Thanks, Roy > On Dec 6, 2018, at 8:22 AM, Hadley Wi

[R-pkg-devel] New CRAN internet policy

2018-12-06 Thread Hadley Wickham
Hi all, I'd love to get some clarification on what the new internet policy means for packages like httr: > Packages which use Internet resources should fail gracefully with an > informative > message if the resource is not available (and not give a check warning nor > error). It's not clear wh

[R-pkg-devel] testing coercion

2018-12-06 Thread Kevin Coombes
Hi, A package I recently submitted to CRAN includes an S4 class that defines a method to coerce from that class to a numeric vector, basically through > setAs("myClass", "numeric", function(from) from@psi) Being perhaps overly compulsive about trying to test everything while documenting behavi

Re: [R-pkg-devel] package 'corpus' not available?

2018-12-06 Thread Uwe Ligges
Please submit again, perhaps a race cndition on one of the incoming check machines that instaled corpus when your package was checked? If this persists, pls write to in response to the auto-rejection. Best, Uwe Ligges On 06.12.2018 07:28, Dalthorp, Daniel via R-package-devel wrote: Su