Re: [R-pkg-devel] correcting errors in an existing package

2023-04-04 Thread Lionel Henry
Hi Dennis, I'm reincluding the list so that other people can see the clarifications too. On 4/4/23, Dennis Boos wrote: > Thanks so much. Could you give me a little more clarity? > > 1. Where do I add > > #' @importFrom stats var sd etc > > Within the R functions? Each one separately > > 2. Was

Re: [R-pkg-devel] correcting errors in an existing package

2023-04-04 Thread Lionel Henry
> Here is my namespace. It says not to edit, but I had been told to add > the importFrom. So I didn't use > devtools::document() for fear roxygen2 would get rid of it. `devtools::check()` calls `document()` automatically so your changes to the NAMESPACE file get overwritten. You can see this in t

Re: [R-pkg-devel] correcting errors in an existing package

2023-04-04 Thread Dirk Eddelbuettel
On 4 April 2023 at 10:04, Duncan Murdoch wrote: | I'd suggest this: build the tarball, and check the tarball. Strong second. The _Writing R Extensions_ manual does not mention devtools. As Uwe often reminds everybody here the package is not used by CRAN either. This may sound harsh but one of

Re: [R-pkg-devel] correcting errors in an existing package

2023-04-04 Thread Duncan Murdoch
Your message is posted using HTML, which mangles a lot of it. For example, the NAMESPACE file you posted has URLs mixed in with the text. But if I can guess correctly what was in those files, it looks as though the package being checked doesn't have those files in it. I don't know exactly wh

Re: [R-pkg-devel] correcting errors in an existing package

2023-04-04 Thread Dennis Boos
Thanks so much to all of you. If you have time, I'm getting really contradictory results. 1. It first seemed to have passed the check in Rstudio (I used device::build() in the R window and then clicked on check in the drop down menu under build). ==> devtools::check(document = FALSE, args = c('-

Re: [R-pkg-devel] correcting errors in an existing package

2023-04-02 Thread Uwe Ligges
On 02.04.2023 12:12, Michael Dewey wrote: Comment in-line On 02/04/2023 06:37, Ivan Krylov wrote: On Fri, 31 Mar 2023 16:51:40 -0400 Dennis Boos wrote: Also, I keep getting the message in the Rstudio check WARNING     'qpdf' is needed for checks on size reduction of PDFs but I got the

Re: [R-pkg-devel] correcting errors in an existing package

2023-04-02 Thread Michael Dewey
Comment in-line On 02/04/2023 06:37, Ivan Krylov wrote: On Fri, 31 Mar 2023 16:51:40 -0400 Dennis Boos wrote: Also, I keep getting the message in the Rstudio check WARNING 'qpdf' is needed for checks on size reduction of PDFs but I got the latest versions of R and Rstudio and was able

Re: [R-pkg-devel] correcting errors in an existing package

2023-04-01 Thread Ivan Krylov
On Fri, 31 Mar 2023 16:51:40 -0400 Dennis Boos wrote: > Also, I keep getting the message in the Rstudio check > > WARNING >'qpdf' is needed for checks on size reduction of PDFs > > > but I got the latest versions of R and Rstudio and was able to get > qpdf to install and loaded with librar

Re: [R-pkg-devel] correcting errors in an existing package

2023-04-01 Thread Duncan Murdoch
On 31/03/2023 4:51 p.m., Dennis Boos wrote: Recently I got a message from CRAN that my package Monte.Carlo.se (on CRAN for the last few years) does not pass current testing. There seemed to be 2 problems: **

Re: [R-pkg-devel] correcting errors in an existing package

2023-04-01 Thread Kevin R. Coombes
1. Yes, remove the "lazyData" line from the DESCRIPTION file. 2. Do you have "stats" in the "Imports" line in the DESCRIPTION file? If not, put it in along with the "importFrom" line in the NAMESPACE file. On 3/31/2023 4:51 PM, Dennis Boos wrote: Recently I got a message from CRAN that my pac

[R-pkg-devel] correcting errors in an existing package

2023-04-01 Thread Dennis Boos
Recently I got a message from CRAN that my package Monte.Carlo.se (on CRAN for the last few years) does not pass current testing. There seemed to be 2 problems: *** 1. * checking LazyData