Re: [R-pkg-devel] Assignments to the global environment and use of on.exit

2021-06-22 Thread Oliver Madsen
The problem is solved by either 1) creating an environment variable within the package namespace (as you would a function) using new.env(). This can then be used instead of the global environment. 2) assigning variables to the namespace of the function running the shiny app. 1) is the second

Re: [R-pkg-devel] Assignments to the global environment and use of on.exit

2021-06-22 Thread Jeff Newmiller
Just don't. E.g. https://stackoverflow.com/questions/12598242/global-variables-in-packages-in-r On June 22, 2021 1:47:56 AM PDT, Siddhanta Phuyal wrote: > Hello, > >A few weeks ago, I submitted a package to CRAN. The automated system >rejected the package showing the following note: > >Found

[R-pkg-devel] Assignments to the global environment and use of on.exit

2021-06-22 Thread Siddhanta Phuyal
Hello, A few weeks ago, I submitted a package to CRAN. The automated system rejected the package showing the following note: Found the following assignments to the global environment: File 'EuclideanSD/R/EuclideanSD.R': assign("nums", x, envir = globalenv()) Context of the problem: The

Re: [R-pkg-devel] How to communicate WARNINGS fixed from *last* CRAN version of a package

2021-06-22 Thread Duncan Murdoch
On 22/06/2021 8:36 a.m., Spencer Graves wrote: Have you followed the advice in chapter 20 of Wickham and Bryan, R Packages: https://r-pkgs.org/release.html In particular, does your package include a file "cran-comments.md", as described therein? I wouldn't be so sure about that.

Re: [R-pkg-devel] How to communicate WARNINGS fixed from *last* CRAN version of a package

2021-06-22 Thread Alberto Garre
Yes, the submission contains a cran-comments.md, which mentions these changes. El mar, 22 jun 2021 a las 14:36, Spencer Graves (< spencer.gra...@effectivedefense.org>) escribió: > Have you followed the advice in chapter 20 of Wickham and Bryan, R > Packages: > > >

Re: [R-pkg-devel] How to communicate WARNINGS fixed from *last* CRAN version of a package

2021-06-22 Thread Spencer Graves
Have you followed the advice in chapter 20 of Wickham and Bryan, R Packages: https://r-pkgs.org/release.html In particular, does your package include a file "cran-comments.md", as described therein? I believe that's where the CRAN maintainers look for info like that.

Re: [R-pkg-devel] How to communicate WARNINGS fixed from *last* CRAN version of a package

2021-06-22 Thread Alberto Garre
Thanks. I just "replied-to-all" again. Gmail then sends the email to cran-submissi...@r-project.org. Is this the correct address? El mar, 22 jun 2021 a las 12:38, Georgi Boshnakov (< georgi.boshna...@manchester.ac.uk>) escribió: > >... Hence please reply-all and explain: Have these been fixed? >

Re: [R-pkg-devel] How to communicate WARNINGS fixed from *last* CRAN version of a package

2021-06-22 Thread Georgi Boshnakov
>... Hence please reply-all and explain: Have these been fixed? Maybe 'reply-all' to CRAN team's email? Georgi Boshnakov -Original Message- From: R-package-devel On Behalf Of Alberto Garre Sent: 22 June 2021 09:11 To: R-package-devel@r-project.org Subject: [R-pkg-devel] How to

Re: [R-pkg-devel] How to communicate WARNINGS fixed from *last* CRAN version of a package

2021-06-22 Thread Alberto Garre
Yes, I answered on 21 jun at 18:56 El mar, 22 jun 2021 a las 11:26, Martin Maechler (< maech...@stat.math.ethz.ch>) escribió: > > Alberto Garre > > on Tue, 22 Jun 2021 10:52:26 +0200 writes: > > > Thanks! It is the first time I got this message, so I was a bit > puzzled > >

Re: [R-pkg-devel] How to communicate WARNINGS fixed from *last* CRAN version of a package

2021-06-22 Thread Martin Maechler
> Alberto Garre > on Tue, 22 Jun 2021 10:52:26 +0200 writes: > Thanks! It is the first time I got this message, so I was a bit puzzled > about what to do. I will be patient, then :) > Alberto well, as Sebastian said >> The auto-check e-mail said "Hence please

[R-pkg-devel] fviz_nbclust

2021-06-22 Thread csmatyi
Hello all, I am having difficulty installing the factoextra package. I want to run the fviz_nbclust command. Error message [truncated]: The downloaded source packages are in ‘/tmp/RtmpXEQfNc/downloaded_packages’ Installation paths not writeable, unable to update packages path:

Re: [R-pkg-devel] How to communicate WARNINGS fixed from *last* CRAN version of a package

2021-06-22 Thread Alberto Garre
Thanks! It is the first time I got this message, so I was a bit puzzled about what to do. I will be patient, then :) Alberto El mar, 22 jun 2021 a las 10:50, Sebastian Meyer () escribió: > Am 22.06.21 um 10:11 schrieb Alberto Garre: > > Hi, > > > > I submitted yesterday a new version of the

Re: [R-pkg-devel] How to communicate WARNINGS fixed from *last* CRAN version of a package

2021-06-22 Thread Sebastian Meyer
Am 22.06.21 um 10:11 schrieb Alberto Garre: > Hi, > > I submitted yesterday a new version of the biogrowth package ( > https://cran.r-project.org/package=biogrowth). In the automatic response, I > got the following message: > > The auto-check found additional issues for the *last* version

[R-pkg-devel] How to communicate WARNINGS fixed from *last* CRAN version of a package

2021-06-22 Thread Alberto Garre
Hi, I submitted yesterday a new version of the biogrowth package ( https://cran.r-project.org/package=biogrowth). In the automatic response, I got the following message: The auto-check found additional issues for the *last* version released on CRAN: donttest

Re: [R-pkg-devel] fviz_nbclust

2021-06-22 Thread Uwe Ligges
On 22.06.2021 07:10, csmatyi wrote: Hello all, I am having difficulty installing the factoextra package. I want to run the fviz_nbclust command. Error message [truncated]: The downloaded source packages are in ‘/tmp/RtmpXEQfNc/downloaded_packages’ Installation paths not writeable, unable