Re: [R-pkg-devel] Replicate solaris errors

I don't remember the installation procedure, sorry. But I'd rather try rhub before following that path again. Iñaki > > On Sat, Aug 11, 2018 at 2:17 PM Iñaki Úcar wrote: >> >> El sáb., 11 ago. 2018 a las 19:30, Thibault Vatter >> () escribió: >> > >> > Dear pac

Re: [R-pkg-devel] Replicate solaris errors

El sáb., 11 ago. 2018 a las 19:30, Thibault Vatter () escribió: > > Dear package developers, > > We've recently received an email letting us know that our package > rvinecopulib ( > https://cran.r-project.org/web/packages/rvinecopulib/index.html) would be > removed from CRAN unless the errors from

Re: [R-pkg-devel] Building my R package: issue when importing two functions with the same name

El mar., 7 ago. 2018 a las 9:32, Gianmarco Alberti () escribió: > > I am building a R package, and I am facing an issue caused (as far as I > understand) by the fact that some functions out of my package rely on two > fuctions having the same name and coming from 2 different packages: > >

Re: [R-pkg-devel] Disable a particular knitr vignette

fallback simply ignores the fancy latex commands and produces a HTML output, which prevents R CMD check from complaining. Regards, Iñaki El jue., 2 ago. 2018 a las 10:04, Iñaki Úcar () escribió: > > Hi everyone, > > I have a JSS vignette based on the rticles package. It was compiling &g

Re: [R-pkg-devel] Disable a particular knitr vignette

is is described in the vignettes > (https://cran.r-project.org/package=R.rsp). > > -Henrik Thanks for the suggestion, Henrik. I would prefer, though, not to change the behaviour on other platforms and not to rely on another dependency just for a workaround. Iñaki > On Thu, Aug 2, 2018 at

[R-pkg-devel] Disable a particular knitr vignette

Hi everyone, I have a JSS vignette based on the rticles package. It was compiling just fine until rticles v0.5 for some reason started requiring pandoc v2.x for such a document class, and failing otherwise. Due to this requirement, Windows machines on CRAN show a nasty WARN, because they still

Re: [R-pkg-devel] can't reproduce cran-pretest error

Hi, a couple of things,: 1) Have you checked the rchk report for possible issues? https://raw.githubusercontent.com/kalibera/cran-checks/master/rchk/results/epanet2toolkit.out 2) Here there's a call to RENgettimeparam, which passes an empty character buffer:

Re: [R-pkg-devel] C++11 and deprecated warnings "noise" for auto_ptr

e silent! So those > of us using Boost and BH could add the define to the headers. > > Dirk > > -- > http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org > > __ > R-package-devel@r-project.org mailing list > https:

Re: [R-pkg-devel] More on explosive dependencies

El lun., 16 jul. 2018 a las 3:24, Lenth, Russell V () escribió: > > Package developers, > > I posted a question a couple of months ago dealing with how to reduce the > number of dependencies in a package. Part of the specific issue I face is > that I have a `cld` S3 method for which the generic

Re: [R-pkg-devel] compilation flags WARNING

; > >> Iñaki > >> > >>> > >>> Göran Broström > >> > >> __ > >> R-package-devel@r-project.org mailing list > >> https://stat.ethz.ch/mailman/listinfo/r-package-devel > > > > __ > > R-package-devel@r-project.org mailing list > > https://stat.ethz.ch/mailman/listinfo/r-package-devel > > > > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Iñaki Úcar http://www.enchufa2.es @Enchufa2 __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Weird error on CRAN linux check

port' should be superfluous if S3method is used. > On Thu, 5 Jul 2018 at 20:43, Iñaki Úcar wrote: > >> >> >> El jue., 5 jul. 2018 21:35, David Hugh-Jones >> escribió: >> >>> Installed from CRAN or github? CRAN should be OK - I hope! >>> >>

Re: [R-pkg-devel] Weird error on CRAN linux check

El jue., 5 jul. 2018 21:35, David Hugh-Jones escribió: > Installed from CRAN or github? CRAN should be OK - I hope! > >From GitHub before the patch. > On Thu, 5 Jul 2018 at 20:33, Iñaki Úcar wrote: > >> I installed huxtable in two environments, my own Fedora install

Re: [R-pkg-devel] Weird error on CRAN linux check

I installed huxtable in two environments, my own Fedora installation with R 3.5.0 and all my packages and in a fresh Ubuntu system with R 3.4.4 and an empty library. In both cases, huxtable is unusable: every example I try fails because it doesn't find the methods. So it has nothing to do with R

Re: [R-pkg-devel] compilation flags WARNING

El jue., 5 jul. 2018 a las 16:11, Göran Broström () escribió: > > I am preparing a CRAN release of eha (a trivial change due to a change > in the survival package), but when checking the build I get: > > goran@M6800:~/R$ R CMD check --as-cran eha_2.5.2.tar.gz > ... > * checking compilation flags

Re: [R-pkg-devel] Weird error on CRAN linux check

El mié., 4 jul. 2018 a las 22:47, Duncan Murdoch () escribió: > > On 04/07/2018 4:04 PM, Joris Meys wrote: > > > > > > On Wed, Jul 4, 2018 at 9:31 PM, Duncan Murdoch > > wrote: > > > > > > That shouldn't matter. That function was created in a local > >

Re: [R-pkg-devel] Weird error on CRAN linux check

;>> -- > >>> Joris Meys > >>> Statistical consultant > >>> > >>> Department of Data Analysis and Mathematical Modelling > >>> Ghent University > >>> Coupure Links 653, B-9000 Gent (Belgium) > >>> > >>> <https://maps.google.com/?q=Coupure+links+653,%C2%A0B-9000+Gent,%C2%A0Belgium=gmail=g> > >>> > >>> tel: +32 (0)9 264 61 79 > >>> --- > >>> Biowiskundedagen 2017-2018 > >>> http://www.biowiskundedagen.ugent.be/ > >>> > >>> --- > >>> Disclaimer : http://helpdesk.ugent.be/e-maildisclaimer.php > >>> > >> -- > >> Sent from Gmail Mobile > >> > > > > > > > > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Iñaki Úcar http://www.enchufa2.es @Enchufa2 __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Compiled code checks raise a WARNING in Fedora 28

2018-05-23 17:40 GMT+02:00 Dirk Eddelbuettel <e...@debian.org>: > > On 23 May 2018 at 17:22, Iñaki Úcar wrote: > | Hi, > | > | For other Fedora users that may be struggling with this too... > | > | Fedora 28 introduced new hardening flags for compiled code

[R-pkg-devel] Compiled code checks raise a WARNING in Fedora 28

Hi, For other Fedora users that may be struggling with this too... Fedora 28 introduced new hardening flags for compiled code (see [1]). Particularly, -D_GLIBCXX_ASSERTIONS is added to the default CXXFLAGS (verify the output of 'R CMD config CXXFLAGS'), which enables range checks for C++ arrays,

Re: [R-pkg-devel] CRAN pretest archived because of 2 NOTEs

2018-04-18 22:49 GMT+02:00 Gertjan van den Burg : > Thanks for your comment. Your suggestion wouldn't solve my original problem > unfortunately, because then I'd have to reverse engineer R's RNG for my > Python package. Besides, the quality of the random numbers

Re: [R-pkg-devel] Avoid reprocessing Rmd vignette

2018-03-20 5:12 GMT+01:00 Jennifer Bryan : > Hi Tim, > > Here's a rather long thread from previous discussions of this: > > https://stat.ethz.ch/pipermail/r-devel/2014-May/069113.html > > These two lines from R CMD check suggest the two ways the vignette code > will be

Re: [R-pkg-devel] Avoid reprocessing Rmd vignette

2018-03-20 4:04 GMT+01:00 Tim Keitt : > http://www.keittlab.org/ > > On Mon, Mar 19, 2018 at 6:41 AM, Dirk Eddelbuettel wrote: > >> >> On 18 March 2018 at 21:57, Tim Keitt wrote: >> | That's a great idea, however my problem is with building a vignette, not >> |

Re: [R-pkg-devel] Avoid reprocessing Rmd vignette

2018-03-19 3:57 GMT+01:00 Tim Keitt : > http://www.keittlab.org/ > > On Sun, Mar 18, 2018 at 8:14 PM, Dirk Eddelbuettel wrote: > >> >> Tim, >> >> On 18 March 2018 at 18:58, Tim Keitt wrote: >> | I have an Rmd vignette that runs some benchmarks. It takes long

Re: [R-pkg-devel] vignette with third party software

2018-02-26 16:16 GMT+01:00 Iñaki Úcar <i.uca...@gmail.com>: > 2018-02-26 15:03 GMT+01:00 Dominik Leutnant <leutn...@fh-muenster.de>: >> Dear all, >> >> We'd like to submit an update of the "swmmr" package to CRAN, which >> interfaces the rai

Re: [R-pkg-devel] vignette with third party software

2018-02-26 15:03 GMT+01:00 Dominik Leutnant : > Dear all, > > We'd like to submit an update of the "swmmr" package to CRAN, which > interfaces the rainfall runoff model SWMM from the US environmental > protection agency. > The package also includes three vignettes which

Re: [R-pkg-devel] author field in description problem

2018-02-25 23:49 GMT+01:00 William Revelle : > Hi, > > I am trying to take advantage of the Authors@R: field in my description file > for the psych package to add an ORCID address (as discussed in the R journal). > > When I R CMD check with R development on my Mac, or with win

Re: [R-pkg-devel] [Rd] How to address the following: CRAN packages not using Suggests conditionally

Re-sending, since I forgot to include the list, sorry. I'm including r-package-devel too this time, as it seems more appropriate for this list. El 22 ene. 2018 10:11, "Iñaki Úcar" <i.uca...@gmail.com> escribió: > > > El 22 ene. 2018 8:12, "Ulrich Bodenho

Re: [R-pkg-devel] Debian: example file is no longer read correctly

2017-12-20 11:11 GMT+01:00 Blume Christine : > Dear all, > > I guess I need your help again. With debian my package (nparACT) gives an > error message that seems to be related to loading the data: > > Warning in is.na(data$activity) : > is.na() applied to

Re: [R-pkg-devel] nparACT package: "working directory was changed to...resetting"

2017-12-19 16:27 GMT+01:00 Blume Christine : > Hi Duncan, > > Thanks a lot! Good to see that you had a similar idea, I did just that...in > my example it looks like this, however, that does not help, i.e. that is the > code that is associated with the warning… > >

[R-pkg-devel] CRAN check FAIL due to pragmas in headers and code

Hi all, Three days ago, Patrick Perry posted the following on R-devel: 2017-12-11 16:32 GMT+01:00 Patrick Perry : > A recent change to r-devel causes an R CMD check warning when a C file > includes a "#pragma GCC diagnostic ignored" pragma: >

Re: [R-pkg-devel] creating indelible file during unit test

2017-12-12 15:47 GMT+01:00 Barry Rowlingson : > I think unix makes it impossible for you to create something that even you > can't delete. You may need higher powers ("root") to change the ownership > of the thing you've created. In a Unix system with administrator

Re: [R-pkg-devel] (no subject)

2017-12-05 18:38 GMT+01:00 Uwe Ligges <lig...@statistik.tu-dortmund.de>: > > > On 05.12.2017 18:35, Iñaki Úcar wrote: >> >> 2017-12-05 10:04 GMT+01:00 Jose Manuel Vera <vera.joseman...@gmail.com>: >>> >>> Hi all >>> >>>

Re: [R-pkg-devel] (no subject)

2017-12-05 10:04 GMT+01:00 Jose Manuel Vera : > Hi all > > Submitted my package to CRAN but I got some notes I cannot understand. > > First NOTE is regarding possibly mis-spelled words in DESCRIPTION. Taken > into account that these are not mispelled words (catastro is a

Re: [R-pkg-devel] adding rPython as a suggested package

2017-12-01 7:50 GMT+01:00 Slava Lyubchich : > Hello, > > I have a package on CRAN (funtimes) and I am trying to add a function > that uses some Python code (only one function in the package needs > Python, others do not). In order to do that, I > 1) add in the DESCRIPTION >

Re: [R-pkg-devel] Package valgrind problem I can't solve: Direction?

2017-11-06 0:09 GMT+01:00 Peter Dunn : > Impossible or not… it just happened (unless I am being really stupid, which > is entirely possible, indeed probable). I confirmed again this morning: > After rebuilding (R CMD build) and checking (R CMD check) without any > errors, I used

Re: [R-pkg-devel] Package valgrind problem I can't solve: Direction?

2017-11-03 6:01 GMT+01:00 Peter Dunn : > Iñaki and all > > Well, thanks for pointers to rhub. Wonderful. Moving things to github, but > have to go home now… > > So, when I download CRAN code, initialise w and lambda (which workled for > Iñaki), and run > >

Re: [R-pkg-devel] Package valgrind problem I can't solve: Direction?

2017-11-01 5:56 GMT+01:00 Peter Dunn : > Wow: Thanks again. You are going above and beyond Iñaki which I appreciate > greatly. > > But same error message appears, even after fixing (both the relerr, which I > had already attended to, and the lambda issue). All I can say is that

Re: [R-pkg-devel] Package valgrind problem I can't solve: Direction?

2017-10-30 0:54 GMT+01:00 Peter Dunn : > Thanks for this direction. > > But I am still confused, as the problem persists after attending to any > possible issue: That piece of identified code only has four variables, and I > can account for them all. > > The two variables its

Re: [R-pkg-devel] Package valgrind problem I can't solve: Direction?

2017-10-30 0:54 GMT+01:00 Peter Dunn : > Thanks for this direction. > > But I am still confused, as the problem persists after attending to any > possible issue: That piece of identified code only has four variables, and I > can account for them all. > > The two variables its

Re: [R-pkg-devel] Package valgrind problem I can't solve: Direction?

Hi, 2017-10-26 5:16 GMT+02:00 Peter Dunn : > Hi all > > I am trying to compile (on my Mac) an R package (tweedie) which includes > Fortran 77 code. I’m not much of a programmer, but can still manage to write > and update F77 code. I’m new to valgrind. > > In checking my

Re: [R-pkg-devel] Where do demos fit in?

2017-10-20 5:42 GMT+02:00 Neal Fultz : > A graduate student just asked me (copied below), in response to a bug I > wrote ( > https://github.com/DeclareDesign/estimatr/pull/38/commits/99e82e253979d1307714632e9dc05d2e2c9c66df > ): > > How do demos normally relate to tests and

Re: [R-pkg-devel] r-quantities seeking feedback

2017-10-06 22:28 GMT+02:00 David Hugh-Jones : > Many measurements have no unit, but some uncertainty - e.g. the b and se > from an arbitrary regression. Can you give specific examples of the > advantages from binding these packages tightly together? As Duncan already

Re: [R-pkg-devel] r-quantities seeking feedback

or bars in plots...). Iñaki Cheers, D On Fri, 6 Oct 2017 at 17:25, Iñaki Úcar <i.uca...@gmail.com> wrote: > Dear all, > > Edzer Pebesma and I are combining forces into a new GitHub > organisation called "r-quantities", to which we have moved the CRAN > packa

[R-pkg-devel] r-quantities seeking feedback

Dear all, Edzer Pebesma and I are combining forces into a new GitHub organisation called "r-quantities", to which we have moved the CRAN packages 'units', 'errors' and 'constants'. The idea is to write a new package called 'quantities' to integrate 'units' and 'errors' into a comprehensive

Re: [R-pkg-devel] tibbles are not data frames

2017-09-26 13:41 GMT+02:00 Holger Hoefling : > Hi Thierry, > > You write: > > "If a package requires a data.frame, then it is up to the _user_ to > provide a data.frame (and a tibble is not a data.frame). " > > Actually, as pointed out before, calling > > is.data.frame > > on a

Re: [R-pkg-devel] Directing package feedback to Github issues

Hi, 2017-08-23 1:37 GMT+02:00 Bruce Hoff : > The official instructions for writing an R package (https://cran.r-project. > org/doc/manuals/r-release/R-exts.html) states, in part, > > "The mandatory ‘Maintainer’ field should give a *single* name followed by a > *valid*

Re: [R-pkg-devel] Question on Notes for Package Submission

Hi, The messages are quite clear: 2017-08-17 10:14 GMT+02:00 Chu-Lan Kao : > Dear Sir, > > We've just uploaded a package with two notes that we couldn't figure out > how to deal with it. They are: > > 1) * checking R code for possible problems ... NOTE > > est.changepoints:

Re: [R-pkg-devel] CRAN submission pretest warning about Rcpp version used to build dplyr

2017-07-13 20:19 GMT+02:00 Dirk Eddelbuettel <e...@debian.org>: > > On 13 July 2017 at 19:52, Iñaki Úcar wrote: > | Or, in other words, Brooke, now you have to wait until Rcpp 0.12.12 > | appears on CRAN and then one or two days more until dplyr is rebuilt. > | Then, try to

Re: [R-pkg-devel] best approach to getting an external library to *not* use stdout, stderr, etc.

2017-06-28 16:29 GMT+02:00 Simon Barthelmé : > Dear list, > > I'm trying to wrap an external C++ library that has the bad habit of > printing errors to std::cerr, a behaviour which will lead to CRAN issuing > warnings. I was wondering if people had come up with a

Re: [R-pkg-devel] Linking external libraries in non-standard locations

2017-06-17 18:00 GMT+02:00 Dirk Eddelbuettel <e...@debian.org>: > > On 17 June 2017 at 17:30, Iñaki Úcar wrote: > | Hi all, > | > | After googling around for a while, I found that this is a common > | problem, but still it is not clear to me how I should handle this.

[R-pkg-devel] Linking external libraries in non-standard locations

Hi all, After googling around for a while, I found that this is a common problem, but still it is not clear to me how I should handle this. I have a package A, with C++ code via Rcpp, that needs an external C++ library libB. I have a configure script that sets PKG_CPPFLAGS=-I/path/to/B/include

[R-pkg-devel] Logging data to disk from C++ using a DBMS

with dplyr no matter which storage method is selected, memory or database. The question is whether there is a better, more efficient, way of achieving this goal. Is there any package already doing something similar? Ideas and alternatives welcome. Thanks in advance. Regards, -- Iñaki Úcar http

Re: [R-pkg-devel] run a function from a list

ot;, "floater.floor", "floater.index", "floater.formula", > "inverse.balance", "inverse.cap", "inverse.multipler", "inverse.floor", > "inverse.floater.formula")) > > > > > __ > R-package-devel@r-