Re: [R-pkg-devel] Possible malware(?) in a vignette

rther indication that > it's a false-positive is that a simple re-packaging the streams (i.e. NOT > changing the actual PDF contents) make the same file pass the tests as > clean. > > > > Also note that there is a bit of a confusion as the currently released > version (poweRlaw 0.80

Re: [R-pkg-devel] Possible malware(?) in a vignette

On Thu, 25 Jan 2024 at 10:13, Colin Gillespie wrote: > > Hi All, > > I've had two emails from users in the last 24 hours about malware > around one of my vignettes. A snippet from the last user is: > > --- > I was trying to install a R package that depends on PowerRLaw two > weeks ago. However

Re: [R-pkg-devel] Virtual C++ functions

On Wed, 15 Nov 2023 at 12:45, Michael Meyer via R-package-devel wrote: > > Greetings, > Suppose I wanted to develop a package with C++ code that contains virtual > functions which the package user should define.It's assumed that evaluation > is expensive so we do not want to define these in R

Re: [R-pkg-devel] PkgA imports PkgB, and PkgB suggests PkgA?

El sáb., 4 nov. 2023 5:43, Shu Fai Cheung escribió: > Hi All, > > I vaguely recall that, on CRAN, if PkgA imports PkgB, then PkgB cannot > import PkgA. (Please correct me if I am wrong.) > > How about this? > > PkgA imports PkgB (because PkgA has some helper functions for using PkgB) > PkgB

Re: [R-pkg-devel] CartogRaflow submission

El mar., 17 oct. 2023 9:13, cartograf...@gmail.com escribió: > Hi, I've put an update version of the package cartogRaflow 1.0.4 in CRAN > today. > There are 2 errors > Last released version's CRAN status: OK: 11, ERROR: 2 > See: < >

Re: [R-pkg-devel] [EXTERNAL] Re: Warning: a function declaration without a prototype is deprecated in all versions of C

On Tue, 26 Sept 2023 at 10:29, Sameh Abdulah wrote: > > Thanks for replying! > > The main problem that this warning from a C library that I am relying on, I > have no control to fix the warning there. So, I am still getting this warning > from R, when building my package. We don't have a way

Re: [R-pkg-devel] What to do when a package is archived from CRAN

About licensing, On Sun, 27 Aug 2023 at 17:30, SHIMA Tatsuya wrote: > > Hi Ivan, thanks for taking the time to look at all the details of this. > > > You licensed the package as MIT. Are your dependencies compatible > with MIT? All direct dependencies of your Rust code seem to be licensed >

Re: [R-pkg-devel] [Rd] R packages to send plottable data to external apps

I think r-package-devel is a better place for this. CC'ing there. On Sun, 27 Aug 2023 at 23:50, Mike Marchywka wrote: > > I was curious what R packages, or indeed any other applications, exist > to plot streamed data from arbitrary data generators. It need not > be publication quality plotting

Re: [R-pkg-devel] Package broke with R 4.3.0

On Tue, 27 Jun 2023 at 18:45, Jeff Newmiller wrote: > > if (any(c( "alaska", "hawaii") %in% zoom)){} Note that this changes behavior. If e.g. zoom is c("something", "alaska"), the code above returns TRUE. Previous behavior was FALSE (with a warning). Iñaki > On June 27, 2023 9:11:09 AM PDT,

Re: [R-pkg-devel] Package broke with R 4.3.0

On Tue, 27 Jun 2023 at 16:31, wrote: > > It appears that my R package choroplethr broke due to this change in R > 4.3.0: > > CHANGES IN R 4.3.0: > > SIGNIFICANT USER-VISIBLE CHANGES: > > Calling && or || with LHS or (if evaluated) RHS of length greater than one > is now always an error, with a

Re: [R-pkg-devel] Please install cmake on macOS builders

El vie., 12 may. 2023 5:58, Simon Urbanek escribió: > I think it would be quite useful to have some community repository of code > snippets dealing with such situations. R-exts gives advice and pieces of > code which are useful, but they are not complete solutions and situations > like Dirk's

Re: [R-pkg-devel] How to update "SystemRequirements: C++11"?

On Tue, 7 Feb 2023 at 01:50, Avraham Adler wrote: > > On Tue, Feb 7, 2023 at 12:10 AM Iñaki Ucar wrote: > > > > On Tue, 7 Feb 2023 at 00:09, Avraham Adler wrote: > > > > > > "If a package does have a src/Makevars[.win] file then also

Re: [R-pkg-devel] How to update "SystemRequirements: C++11"?

On Tue, 7 Feb 2023 at 00:09, Avraham Adler wrote: > > "If a package does have a src/Makevars[.win] file then also setting > the make variable ‘CXX_STD’ there is recommended," That doesn't refer to the SystemRequirements field. Iñaki > > Avi > > On Mon, Feb 6, 202

Re: [R-pkg-devel] How to update "SystemRequirements: C++11"?

On Mon, 6 Feb 2023 at 23:27, Avraham Adler wrote: > > On Mon, Feb 6, 2023 at 9:46 PM Duncan Murdoch > wrote: > > > > On 06/02/2023 4:01 p.m., Duncan Murdoch wrote: > > > On 06/02/2023 3:46 p.m., Winston Chang wrote: > > >> I recently submitted a package to CRAN with "SystemRequirements: C++11".

Re: [R-pkg-devel] no visible binding for global variable ‘degree_C’ - CRAN check note

On Mon, 12 Dec 2022 at 16:43, EcoC2S - Irucka Embry wrote: > > Hi Andrew, set_units(T, "degree_C") does not work; Sorry, do you mean that the code fails? Or the code works but you still see the NOTE? In this case, it is possible that you didn't replace all the instances of set_units(T, degree_C)

Re: [R-pkg-devel] How ton print in the console from Rcpp

Hi, On Thu, 20 Oct 2022 at 12:42, Elysée Aristide wrote: > > Greetings, > > In my CDatanet package, I want to print texts and values during a numerical > optimization process. I saw in many posts that CRAN is not happy with > sd::cout and sd::endl. What I understood is that it is better to use

Re: [R-pkg-devel] Linking to a large external library

On Fri, 10 Jun 2022 at 14:54, Ben Engbers wrote: > > \Hi, > > It's been several Fedora versions since I installed R with the command > 'sudo dnf install R'. And with every update of Fedora, R was > automatically updated to the recent version. Fedora 36 was only recently > released. So I would

Re: [R-pkg-devel] CRAN check linux gcc12 Boost error

El dom., 10 abr. 2022 20:33, jérémy Gelb escribió: > Dear all, > > A package I am developing is encountering an error on the platform > (r-devel-linux-x86_64-debian-gcc) since CRAN decided to force the use of > gcc12. > What's the package and what's the error? A link to the report would be

Re: [R-pkg-devel] Setting OpenMP threads (globally) for an R package

On Fri, 18 Mar 2022 at 06:33, Simon Urbanek wrote: > > > On Mar 18, 2022, at 6:10 PM, Evan Biederstedt > > wrote: > > There is some connection to setting `export OMP_NUM_THREADS=1` before > > starting R, and moderate memory usage; that's all I know. > > That's odd. OpenMP itself doesn't

[R-pkg-devel] "polygon edge not found" on macos-arm64

Dear CRAN maintainers, I see there's a new WARN on the recently added macos-arm64 platform for quite a number of packages. Specifically, vignette rebuilding fails with "polygon edge not found" (example in [1]). In addition, there are a number of warnings like this: Warning in

Re: [R-pkg-devel] Tracking down inconsistent errors and notes across operating systems

Hi, On Thu, 22 Jul 2021 at 15:51, Hannah Owens wrote: > > Hi all, > I am working on an update to a package I have on CRAN called occCite. My > latest release attempt didn’t pass incoming automated checks, because there > is an outstanding error. Additionally, there are some weird notes I would >

Re: [R-pkg-devel] New version of 'evlust' package no longer passes incoming checks after ony very minor change

On Thu, 27 May 2021 at 04:54, Thierry Denoeux wrote: > > Dear all, > > Two weeks ago, I successfully uploaded version 2.01 of package ‘evclust’ on > the CRAN website. Earlier this week I received a message telling me that a > problem had been detected in the Linux-based checks for r-devel. The

Re: [R-pkg-devel] What To Include In \donttest{}

On Thu, 27 May 2021 at 06:10, Danielle Maeser wrote: > > Thank you for your assistance. The link is very helpful. > > However, I am still not sure what the difference is between the example > provided with \donttest{} and a vignette. It seems both display an example > of the function. For

Re: [R-pkg-devel] Checking compiled code ... WARNING

Now with the list in CC, apologies. On Fri, 12 Mar 2021 at 21:12, Elysée Aristide wrote: > > Dear all, > > I checked (as cran) my package PartialNetwork > and I got this warning. > > * checking compiled code ... WARNING > File

Re: [R-pkg-devel] Support for several versions of another package

On Mon, 22 Feb 2021 at 11:55, Gábor Csárdi wrote: > > On Sun, Feb 21, 2021 at 3:47 PM Iñaki Ucar wrote: > > > > Hi, > > > > Let's say that pkgA uses pkgB::function1. Then, version 2 of pkgB > > removes function1 and exports function2 for the same functionali

Re: [R-pkg-devel] Support for several versions of another package

02/2021 12:17 p.m., Gábor Csárdi wrote: > > On Sun, Feb 21, 2021 at 6:05 PM Duncan Murdoch > > wrote: > >> > >> On 21/02/2021 9:47 a.m., Iñaki Ucar wrote: > >>> Hi, > >>> > >>> Let's say that pkgA uses pkgB::function1. Then, v

[R-pkg-devel] Support for several versions of another package

Hi, Let's say that pkgA uses pkgB::function1. Then, version 2 of pkgB removes function1 and exports function2 for the same functionality. So pkgA does something along these lines: if (utils::packageVersion("pkgB") < 2) { pkgB::function1() } else { pkgB::function2() } I'd say that there's

Re: [R-pkg-devel] submitting two packages simultaneously

On Fri, 27 Nov 2020 at 17:20, jérémy Gelb wrote: > > Dear All, > > I plan to submit a package I created called spNetwork. The package > uses both Rcpp and parallelization to ensure reasonable calculation > time. However, it is currently not possible to pass a compiled > function to a child

Re: [R-pkg-devel] puzzling CRAN rejection

On Tue, 13 Oct 2020 at 01:47, Ben Bolker wrote: > > > > On 10/12/20 7:37 PM, Duncan Murdoch wrote: > > On 12/10/2020 6:51 p.m., Ben Bolker wrote: > >> > >> > >> On 10/12/20 6:36 PM, Duncan Murdoch wrote: > >>> On 12/10/2020 6:14 p.m., Ben Bolker wrote: > > > > > > I'd say a

Re: [R-pkg-devel] puzzling CRAN rejection

On Mon, 12 Oct 2020 at 22:40, Ben Bolker wrote: > > On 10/12/20 4:34 PM, Iñaki Ucar wrote: > > You are right. I was too fast and didn't read "last released version". > > Then the only suspicious thing I see is: > > > > Overall checktime 23 min &g

Re: [R-pkg-devel] puzzling CRAN rejection

le after the initial CRAN testing anyway ... > > cheers > Ben > > > On 10/12/20 4:23 PM, Iñaki Ucar wrote: > > On Mon, 12 Oct 2020 at 22:04, Ben Bolker wrote: > >> > >> Before I risk wasting the CRAN maintainers' time with a query, can > >> anyone

Re: [R-pkg-devel] puzzling CRAN rejection

On Mon, 12 Oct 2020 at 22:04, Ben Bolker wrote: > >Before I risk wasting the CRAN maintainers' time with a query, can > anyone see what I'm missing here? Everything I can see looks OK, with > the possible exception of the 'NA' result for "CRAN incoming > feasibility" on

Re: [R-pkg-devel] DOI for archived package?

If you proposed https://cran.r-project.org/src/contrib/Archive//_.tar.gz and the editor is suspicious about the "src/contrib/Archive" stuff, you could propose instead https://cran.r-project.org/package==, which *looks* more permanent I guess. Iñaki On Thu, 10 Sep 2020 at 18:14, Kevin R. Coombes

Re: [R-pkg-devel] R CMD INSTALL -l /path/lib

On Wed, 19 Aug 2020 at 14:02, Gábor Csárdi wrote: > > From https://cran.r-project.org/doc/manuals/R-exts.html: > > > The script is run in a separate R environment containing the following > variables: R_PACKAGE_NAME (the name of the package), R_PACKAGE_SOURCE (the > path to the source directory

Re: [R-pkg-devel] Debugging Clang ASAN errors

On Fri, 3 Jul 2020 at 12:19, Martin R. Smith wrote: > > A package I recently had accepted to CRAN is throwing up a "memory not > mapped" segfault on CRAN's post-acceptance fedora-clang ASAN test. This > error does not occur with debian-clang or gcc. > (Check results: >

Re: [R-pkg-devel] [CRAN-pretest-archived] CRAN submission gwsem 2.0.3

On Sun, 14 Jun 2020 at 14:32, Joshua N Pritikin wrote: > > > I'm trying to include vignettes that take much too long for CRAN check. > > At the beginning of the Rmarkdown vignette, I use > > is_CRAN <- !identical(Sys.getenv("NOT_CRAN"), "true") > if (is_CRAN) q() > > And then I use > >

Re: [R-pkg-devel] CRAN checks failing for ATLAS

El sáb., 22 feb. 2020 14:26, Stefan Möding escribió: > Hi, > > I was notified by the CRAN maintainers that checks for my package are > failing: > > https://cran.r-project.org/web/checks/check_results_usl.html > > I don’t understand what’s going on here. All regular checks show the OK > status.

Re: [R-pkg-devel] revdepcheck::revdep_check interpretation problem

El lun., 10 feb. 2020 9:24, Spencer Graves < spencer.gra...@effectivedefense.org> escribió: > Hello, All: > > >I just ran "revdepcheck::revdep_check" on my development version > of "https://github.com/sbgraves237/Ecdat;; copied below. It ended with > "OK: 16, BROKEN: 0". That sounds

[R-pkg-devel] CRAN RPM repositories available

Hi all, I apologize if you are receiving multiple copies of this email, but I'm cross-posting because I believe this may be of interest to a wider audience than just R-SIG-Fedora. This is to announce that I'm maintaining a Copr project [1] that provides RPM repos for Fedora 30, 31 and rawhide

Re: [R-pkg-devel] finding "logo.jpg" [was: "try" malfunctions on Ubuntu Linux 16.04 LTS, R-release, GCC]

El lun., 3 feb. 2020 20:30, Spencer Graves < spencer.gra...@effectivedefense.org> escribió: >Thanks to Iñaki Ucar for identifying a second error that > explained why I still got an error after wrapping one in "try". > > >That still leaves a ques

Re: [R-pkg-devel] "try" malfunctions on Ubuntu Linux 16.04 LTS, R-release, GCC

On Mon, 3 Feb 2020 at 03:16, Spencer Graves wrote: > > Hello, All: > > >devtools::check_rhub failed to trap an error wrapped in "try", > per the email below. This came from running > devtools::check_rhub(Ecfun_dir), where Ecfun_dir = the path to a copy of >

Re: [R-pkg-devel] CRAN rules re. web scraping?

On Thu, 23 Jan 2020 at 02:49, Spencer Graves wrote: > > Hello, All: > > > GOOD NEWS AND BAD NEWS: > > >* First the good news: I heard from Brian Ripley; see below. > His web site says, "He retired in August 2014 on grounds of ill health." > (http://www.stats.ox.ac.uk/~ripley/) I was

Re: [R-pkg-devel] warnings by 3rd party headers

On Fri, 17 Jan 2020 at 20:42, Guido Kraemer wrote: > > Thanks, just to drive this a bit further: > > What if the headers then start producing some ugly compile warnings? Do > I have to fix these, too? How ugly? You can ignore "variable set but not used"-kind of stuff, but if things turn ugly

Re: [R-pkg-devel] warnings by 3rd party headers

On Thu, 16 Jan 2020 at 16:58, Guido Kraemer wrote: > > I need to distribute some 3rd party headers with my package. The headers > make R CMD check produce warnings: > > File which contains pragma(s) suppressing important diagnostics: > ... > Files which contain pragma(s) suppressing

Re: [R-pkg-devel] error in sample(), invalid 'size' argument

On Wed, 15 Jan 2020 at 19:26, Roberts, David wrote: > > Dear Bill, Dear Iñaki, > > Thank you both; I'm confident that you are right. I realized a list > or data.frame would generate that error message, but I did not know that > NULL would also do so. > > This means the the error

Re: [R-pkg-devel] error in sample(), invalid 'size' argument

On Wed, 15 Jan 2020 at 13:58, Roberts, David wrote: > > Colleagues, > > I have a function (maxsimset) in package optpart that has worked for > at least a decade, passes check --as-cran on my ubuntu-based system, and > builds without errors at win-builder and CRAN windows, but fails at CRAN >

Re: [R-pkg-devel] [EXTERNAL] Re: Checkpoint package failing CRAN checks

El lun., 13 ene. 2020 11:45, Hong Ooi via R-package-devel < r-package-devel@r-project.org> escribió: > Good catch, Ivan! Fixing that seems to have done the trick. Thanks! > > The question now is why checkpoint hasn't crashed and burned prior to > this, but I'll leave that for another day

Re: [R-pkg-devel] No prebuilt vignette index

Remove the "inst" directory and don't use "--no-build-vignettes" in your build command. Iñaki On Sun, 15 Dec 2019 at 21:45, Charith Karunarathna < charith_karunarat...@sfu.ca> wrote: > > > Hi Everyone, > > > I wonder how to address the following NOTE that I am getting from the > win-builder

Re: [R-pkg-devel] No prebuilt vignette index

Charith, maybe if you provide more details (how do you build the package?, a link to a repository, a link to the checks...) you'll have more chances of getting help. Iñaki El vie., 13 dic. 2019 0:24, Charith Karunarathna < charith_karunarat...@sfu.ca> escribió: > Reposting... > > > Hi Everyone,

Re: [R-pkg-devel] reduce size of shared objects

On Wed, 11 Dec 2019 at 15:01, Guido Kraemer wrote: > > I have tried the suggestion from the blog post and added > > |strippedLib: $(SHLIB) if test -e "/usr/bin/strip" & test -e > "/bin/uname" & [[ `uname` == "Linux" ]] ; \ then /usr/bin/strip > --strip-debug $(SHLIB); fi .phony: strippedLib| > ||

Re: [R-pkg-devel] reduce size of shared objects

On Wed, 11 Dec 2019 at 14:07, Guido Kraemer wrote: > > I am building an R package (https://github.com/gdkrmr/zarr-R) that wraps > a couple of C++ headers and the resulting shared object is huge (>20Mb, > see https://travis-ci.org/gdkrmr/zarr-R). I have tried to set the > following in

Re: [R-pkg-devel] Static PDF Vignette

On Wed, 4 Dec 2019 at 22:54, Charith Karunarathna wrote: > > Hi, > > I followed these instructions, > (https://www.markvanderloo.eu/yaRb/2019/01/11/add-a-static-pdf-vignette-to-an-r-package/), > to add a pdf (perfectphyloR.pdf) as the vignette of my package > (perfectphyloR). However, I am

Re: [R-pkg-devel] roxygen2 7.0.1 backslash escape error

El sáb., 30 nov. 2019 16:22, Yoni escribió: > Thank you for the clarification. > > I am then more confused. > > The CRAN version of the package (texPreview) has been unchanged since Oct > 23, at which point it was passing the checks with no errors. > If your package is sitting on CRAN since

Re: [R-pkg-devel] Advice about non-replicable error in CRAN R CMD check

On Mon, 21 Oct 2019 at 13:34, Dueber, David wrote: > > When I submitted my package (BifactorIndicesCalculator: > https://github.com/ddueber/BifactorIndicesCalculator) to CRAN, the automated > checks returned an error for the development release of R in Windows. The log > file is >

Re: [R-pkg-devel] R package which creates a directory in the user home dir

And if the user hits "yes", the package rappdirs may be useful to get an appropriate place to save that data. Iñaki On Thu, 17 Oct 2019 at 14:45, Martin Maechler wrote: > > > Sigbert Klinke > > on Thu, 17 Oct 2019 14:29:54 +0200 writes: > > > Hi, > > I'am developing a

Re: [R-pkg-devel] How reproduce CRAN check

On Fri, 13 Sep 2019 at 16:16, Cristiane Hayumi Taniguti wrote: > > ...twopts_f2.cpp:101:7: runtime error: nan is > outside the range of representable values of type 'int' > onemap.Rcheck/onemap-Ex.Rout:twopts_f2.cpp:101:26: runtime error: nan is > outside the range of

Re: [R-pkg-devel] Problems installing dependences of my package

On Mon, 9 Sep 2019 at 16:58, Andrea Vilar Alvarez wrote: > > First of all, I am not sure about the difference between Depends and Imports, > but I only use Depends. Common advice goes the other way around: you should avoid Depends as much as possible, so that your users' search path doesn't get

Re: [R-pkg-devel] General considerations about vignettes

On Fri, 30 Aug 2019 at 15:26, J C Nash wrote: > > I'm seeking some general advice about including vignettes in my packages, > which are largely for nonlinear estimation and function minimization > (optimization). > This means that my packages offer alternatives to many other tools, and the >

Re: [R-pkg-devel] [External] Re: Farming out methods to other packages

On Sat, 10 Aug 2019 at 21:11, Lenth, Russell V wrote: > > Thanks Iñaki, > > However... > > > 1) renaming those methods (e.g., recover_data_foo, because as soon as > there is a something.foo > > in your namespace, it will be dispatched regardless of whether you > register it or not) > >

Re: [R-pkg-devel] Farming out methods to other packages

On Sat, 10 Aug 2019 at 19:21, Lenth, Russell V wrote: > > Dear developers, > > I maintain a package, emmeans, that provides post-hoc analyses for a variety > of models. These models are supported by writing S3 methods for recover_data > and emm_grid. Quite a few models are supported internally

Re: [R-pkg-devel] help understanding two NOTES during the automatic package checking

On Tue, 6 Aug 2019 at 14:40, Andy Stein wrote: > > Hi, > > I am submitting my first ever R package to CRAN! It's almost ready, but I > have two notes below and I do not understand the best way to fix them and I > was looking to get some feedback if anyone had time to help. I paste the > notes

Re: [R-pkg-devel] help troubleshooting travis-ci issues?

On Mon, 5 Aug 2019 at 00:08, Ben Bolker wrote: > > > Yeah, I might try that, or I might try installing the downstream > packages that are causing problems from Rutter's repo. AFAICT from the build log, the packages that are causing problems are being installed precisely from Rutter's repo:

Re: [R-pkg-devel] help troubleshooting travis-ci issues?

On Sun, 4 Aug 2019 at 23:45, Ben Bolker wrote: > > I tried that already, thanks. Sorry, I should have read til the end of the email before posting. > That's why I'm now suspecting it's some > kind of mismatch between the Rutter PPAs and the default (?) repos that > Travis uses. It would be a

Re: [R-pkg-devel] help troubleshooting travis-ci issues?

On Sun, 4 Aug 2019 at 23:26, Ben Bolker wrote: > > > I'm having some trouble with travis builds of a package (local checks > work fine) and hoping if I can get suggestions for diagnosis & > troubleshooting ... > > The package is 'broom.mixed'; I hadn't changed it in a while, but > recently got

Re: [R-pkg-devel] Fwd: package submission: parallel problem

On Mon, 15 Jul 2019 at 12:24, Ronan GRIOT wrote: > > Dear R developpers, > I submitted a package involving some parallel functions. > > I received this error message: > > Error in .check_ncores(length(names)) : 30 simultaneous processes spawned > > I read that CRAN only pass the test if 2 cores

Re: [R-pkg-devel] CRAN pre-test failed on NOTE "no visible binding for global variable"

raúl On Tue, 2 Jul 2019 at 14:18, Berlanga, Antonio J wrote: > > Hi r-package-devel, > > I've submitted my first package but it failed the CRAN pre-tests on > NOTES. I got: > > - my email > > - an extra non-standard file (which I have now added to .Rbuildignore) > > - NOTEs on "no visible global

Re: [R-pkg-devel] "Progress reports" for examples in packages.

Which line of code is it? Iñaki On Tue, 2 Jul 2019 at 11:32, Rolf Turner wrote: > > > Many thanks to Henrik Bengtsson and Martin Maechler for pointing out > that I can monitor progress by looking at the file > > "mypkg.Rcheck/mypkg-Ex.Rout" > > e.g. by using "tail -f". This strategy

Re: [R-pkg-devel] CRAN NOTE: SHLIB_OPENMP_*FLAGS in Makefiles

On Wed, 19 Jun 2019 at 19:03, Charith Karunarathna wrote: > > Hi, > > I got the following NOTES after submitting my R package to CRAN for the first > time. > > " > Flavor: r-devel-windows-ix86+x86_64 > Check: use of SHLIB_OPENMP_*FLAGS in Makefiles, Result: NOTE > src/Makevars.win:

Re: [R-pkg-devel] Link compiled C object to internal package file

On Wed, 19 Jun 2019 at 16:47, mark padgham wrote: > > Yeah, but that would require completely rewriting the C code to accept a > variable for something that is used hundreds of times as a simple macro. > (Most of that C code is an old library bundled with the package, so not > my work in that

Re: [R-pkg-devel] Unsure how to fix 'Package required but not available: 'dvmisc'' (which is CRAN pkg) error

On Mon, 17 Jun 2019 at 12:18, Marta Karaś wrote: > > Hi Iñaki, > > Thank you a lot for answering! Just to clarify, you basically suggest > resubmitting without any change (except from adding relevant note in > cran-comments.md)? Yes, that's correct. Iñaki

Re: [R-pkg-devel] Unsure how to fix 'Package required but not available: 'dvmisc'' (which is CRAN pkg) error

On Mon, 17 Jun 2019 at 11:13, Marta Karaś wrote: > > Dear all, > > I am trying to submit update to my R package `adept` (GitHub code link > ) and I got pre-test error on Windows > (error check log link >

Re: [R-pkg-devel] package submission errors gsl

On Sun, 16 Jun 2019 at 17:25, halaleh kamari wrote: > > Hi, > I'm trying to submit my first package to cran. I got an email saying that my > package does not pass the incoming checks automatically. > In fact I got 1 ERROR which is related to the RcppGSL package that I use in > my package. > The

Re: [R-pkg-devel] Another CRAN-only bug

On Thu, 13 Jun 2019 at 10:41, David Hugh-Jones wrote: > > Well, the test that fails is this one: > https://win-builder.r-project.org/incoming_pretest/huxtable_4.6.0_20190612_195453/Windows/examples_and_tests/tests_x64/testthat/test-openxlsx.R > > > The last line fails here: > > hx <-

Re: [R-pkg-devel] Another CRAN-only bug

On Wed, 12 Jun 2019 at 22:58, David Hugh-Jones wrote: > > Hi all, > > Not for the first time, my package has a bug that isn't found on rhub, > travis, appveyor, or my local machine, but is found on CRAN. This time it's > Windows-only, so I can't even download a Docker image and investigate that >

Re: [R-pkg-devel] [Rd] Making a package CITATION file from BibTeX

I believe r-package-devel is the proper list for this. Now in CC. On Thu, 30 May 2019 at 00:16, Dr Gregory Jefferis wrote: > > Dear Colleagues, > > I would like to provide a CITATION file for my package nat.nblast [1]. > > I have the correct citation in BibTeX format [2]. How can I convert this

Re: [R-pkg-devel] Cran check on Solaris

On Tue, 28 May 2019 at 20:12, Τόλης Χαλκής wrote: > > Dear all, > > we have submitted the package volesti to CRAN and it is temporarily > accepted, because the check in solaris and > windows r-release-windows-ix86+x86_64 failed as you can see here >

Re: [R-pkg-devel] Failed on win-builder

On Tue, 28 May 2019 at 17:09, Juhee Lee wrote: > > In the first case, I've already done that. But I've got the same results. Can you please paste the output from "R CMD build" here? Iñaki __ R-package-devel@r-project.org mailing list

Re: [R-pkg-devel] Failed on win-builder

On Tue, 28 May 2019 at 16:29, Juhee Lee wrote: > > Hello. I'm checking my package for CRAN. > > I check my package on win-builder, then I got these NOTE and WARNING. > > * checking sizes of PDF files under 'inst/doc' ... WARNING > 'gs+qpdf' made some significant size reductions: >

Re: [R-pkg-devel] Three-argument S3method declaration does not seem to affect dispatching from inside the package.

On Sun, 19 May 2019 at 23:23, Pavel Krivitsky wrote: > > Hi, Inaki, > > On Sun, 2019-05-19 at 16:59 +0200, Iñaki Ucar wrote: > > IMO the simplest way to do this is to check who the caller was: > > > > foo <- function(x) UseMethod("foo") > >

Re: [R-pkg-devel] Three-argument S3method declaration does not seem to affect dispatching from inside the package.

On Sat, 18 May 2019 at 23:34, Pavel Krivitsky wrote: > > > The issue here is that you are registering a non-standard name > > (.gen.formula) for that generic and then defining what would be the > > standard name (gen.formula) for... what purpose? IMHO, this is a bad > > practice and should be

Re: [R-pkg-devel] Check Results ERROR on Windows R release

On Fri, 17 May 2019 at 18:05, Jarrett Phillips wrote: > > Hello, > > On submitting an update of my R package (HACSim), checks fail on > r-release-windows-ix86+x86_64 > > > The updated package, in addition

Re: [R-pkg-devel] Compilation used the "non-portable flag"

On Wed, 15 May 2019 at 15:43, Goldfeld, Keith wrote: > So - even though I am getting the same note: > > Compilation used the following non-portable flag(s): > > from Ubuntu Linux, I should go ahead and submit? Definitely. Iñaki __

Re: [R-pkg-devel] Three-argument S3method declaration does not seem to affect dispatching from inside the package.

On Tue, 14 May 2019 at 12:31, Pavel Krivitsky wrote: > > > Note that disabling name-based dispatch implies two things: 1) the > > inability to override your method by defining gen.formula in the > > global environment, and 2) another package can break yours (i.e., > > internal calls to gen()) by

Re: [R-pkg-devel] data.frame compression and no visible global function

On Tue, 14 May 2019 at 12:08, Christian Peikert wrote: > > Dear all, > I have tried to upload my R-package to CRAN but this package was sadly > reject due to a Warning and a Note. I already know this warning/note but > I could find out to solve this. > > * checking data for ASCII and uncompressed

Re: [R-pkg-devel] Three-argument S3method declaration does not seem to affect dispatching from inside the package.

CCing r-devel. On Tue, 14 May 2019 at 02:11, Pavel Krivitsky wrote: > > Dear All, > > I've run into this while updating a package with unfortunately named > legacy functions. It seems like something that might be worth changing > in R, and I want to get a sense of whether this is a problem

Re: [R-pkg-devel] Problem with using parallel runtime system with R

On Fri, 10 May 2019 at 17:38, Sameh M. Abdulah wrote: > > I will try to talk to my team to fork it for more investigation from your > side. Disclaimer: I'm not saying that I'll have time to have a look. Just that somebody might help if you provide more information, especially the actual code,

Re: [R-pkg-devel] R CMD check ERROR (strange to me)

On Fri, 10 May 2019 at 17:30, Dirk Eddelbuettel wrote: > > > On 10 May 2019 at 16:49, Iñaki Ucar wrote: > | On Fri, 10 May 2019 at 15:42, Wang, Zhu wrote: > | > > | > 00install.out > | > > | > ** testing if installed package can be loaded from temporary locati

Re: [R-pkg-devel] Problem with using parallel runtime system with R

On Fri, 10 May 2019 at 17:06, Sameh M. Abdulah wrote: > > Actually not yet. It is on Github but in a private repo. If it helps I can > fork it for public access for now. Providing the code always improves your chances of getting help. Otherwise, the information is probably too limited. Iñaki

Re: [R-pkg-devel] Problem with using parallel runtime system with R

On Fri, 10 May 2019 at 13:48, Sameh M. Abdulah wrote: > Hi, > > I have a C package which includes the usage of the StarPU runtime system to > allow running my code on different HW architectures. I included this to an > R-package and I found that R is using only one core and all the thread >

Re: [R-pkg-devel] "unable to verify current time" in R CMD check

On Fri, 10 May 2019 at 13:22, Juhee Lee wrote: > > Hi, I'm checking my package for CRAN. > > In fact, I already complete checking CMD in 3.5.3ver. > but for the latest ver., 3.6.0, I get '1 note' when checking CMD. > > I wonder how I can solve this note. > > > checking for future file timestamps

Re: [R-pkg-devel] package problems

On Thu, 25 Apr 2019 at 18:57, Uwe Ligges wrote: > > On 25.04.2019 02:09, Dennis Boos wrote: > > R Package Folks, > > > > The automatic checks rejected my package submission. A year ago, I got > > past the automatic checks, but a CRAN person told me to add a doi and > > use \donttest{}. > > > > 1.

Re: [R-pkg-devel] [EXTERNAL] Re: CRAN Debian File Handling Differences?

On Tue, 23 Apr 2019 at 17:24, David Blodgett wrote: > > OK. Thank you. I'm always nervous about closing and re-opening a tempfile() > but I suppose it is safe. > > Should I interpret your response as saying that creating and mutating files > in "tests/testthat/data" is not possible on CRAN?

Re: [R-pkg-devel] CRAN Debian File Handling Differences?

On Tue, 23 Apr 2019 at 15:57, David Blodgett via R-package-devel wrote: > > I'm working on some CRAN Debian test failures > (https://win-builder.r-project.org/incoming_pretest/ncdfgeom_1.0.0_20190423_031452/). > The tests all pass on rhub Debian, CRAN windows, local OSX, and Travis > Ubuntu.

Re: [R-pkg-devel] Vignette timing out on test server

On Wed, 17 Apr 2019 at 02:41, Roy Mendelssohn - NOAA Federal via R-package-devel wrote: > -- Forwarded message -- > From: Roy Mendelssohn - NOAA Federal > To: "Maëlle SALMON via R-package-devel" > Cc: > Bcc: > Date: Tue, 16 Apr 2019 17:41:21 -0700 > Subject: Vignette timing out

Re: [R-pkg-devel] Package suggested but not available for checking: 'rPeaks'; Additional_repositories

On Tue, 16 Apr 2019 at 20:54, Tan Zhou wrote: > > Hi Iñaki and Ralf, > Thank you very much for your help and suggestions. > Yes, I followed instruction and did that. Now I have the > https://tankwin08.github.io/drat. > But I test > > install.packages("rPeaks") > Installing package into

Re: [R-pkg-devel] Submitting a package whose unit tests sometimes fail because of server connections

On Tue, 16 Apr 2019 at 19:57, Will wrote: > > Hello everyone, > > I'm sorry to bother you, but I would like some help getting a package ( > *suppdata*; https://github.com/ropensci/suppdata) available through CRAN. > The package downloads supplementary materials from papers and data > repositories

Re: [R-pkg-devel] Package suggested but not available for checking: 'rPeaks'; Additional_repositories

You could convince the original author to submit rPeaks to CRAN, or volunteer to be the maintainer and do it yourself if he doesn't want to maintain it. That would be easier for you and better for everyone, because the package would be well-checked under the watchful eye of CRAN maintainers.

Re: [R-pkg-devel] Analysing namespace reverse dependencies

On Sat, 9 Mar 2019 at 15:07, Roger Bivand wrote: > > Hi, > > Is anyone aware of tools permitting the listing of functions in the > namespace of package A used by package B when package B declares that it > depends on A, suggests A, or imports(A) without specifying the functions > from A that B is

Re: [R-pkg-devel] List of reverse dependencies, including archived packages

On Tue, 26 Feb 2019 at 18:38, Oliver Dechant wrote: > > Somewhat relatedly is there a way to monitor when a package has new > reverse depends or imports added? I don't know of any service currently providing this, if that's what you're asking. But it's pretty straightforward to set up a cron job

Re: [R-pkg-devel] List of reverse dependencies, including archived packages

On Tue, 26 Feb 2019 at 05:29, Peter Carbonetto wrote: > > I'm wondering if there is a way to get a list of reverse dependencies on > CRAN that includes archived packages. > > I am asking because "ashr", an R package I maintain, was recently removed > from CRAN, and now it is back after I fixed

  1   2   >