Re: [R-pkg-devel] problems with Maintainers in DESCRIPTION file

Dear Olga Viedma, Welcome to R-package-devel! When looking for advice here, it's best to link to the package code and the R CMD check report you have received. On Thu, 7 Dec 2023 20:58:01 + María Olga Viedma Sillero wrote: > Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64 >

Re: [R-pkg-devel] problems with Maintainers in DESCRIPTION file

Thank you very much, Dirk. I am going to change it. Best regards, Olga -Mensaje original- De: Dirk Eddelbuettel Enviado el: viernes, 8 de diciembre de 2023 0:18 Para: María Olga Viedma Sillero CC: r-package-devel@r-project.org Asunto: Re: [R-pkg-devel] problems with Maintainers in

Re: [R-pkg-devel] problems with Maintainers in DESCRIPTION file

On 7 December 2023 at 20:58, María Olga Viedma Sillero wrote: | I receive the same note after fixing it, removing it, and checking Authors@R. I think the rejection is a false positive. | | Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64 | Check: CRAN incoming feasibility, Result

[R-pkg-devel] problems with Maintainers in DESCRIPTION file

Dear all, I receive the same note after fixing it, removing it, and checking Authors@R. I think the rejection is a false positive. Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64 Check: CRAN incoming feasibility, Result: NOTE Maintainer: 'Olga Viedma mailto:olga.vie...@uc

Re: [R-pkg-devel] Problems with devtools::build() in R

This thread went way off the rails and was cross-posted so the solution is on R-SIG-Mac. It was simply wrong Fortran with wrong R - installing latest R and Fortran (from CRAN or https://mac.r-project.org/tools/) is the easiest way to solve the problem. Note that R binaries and tools go togethe

Re: [R-pkg-devel] Problems with devtools::build() in R

В Wed, 17 May 2023 11:05:46 -0400 Jarrett Phillips пишет: > `which gfortran` returns > > /usr/local/bin/gfortran I think you ran the other gfortran. Is there a gfortran installation in /opt/gfortran? > libraries: > =/usr/local/gfortran/lib/gcc/aarch64-apple-darwin22/12.2.0/:/usr/local/gfortran

Re: [R-pkg-devel] Problems with devtools::build() in R

Hi Ivan, Yes, I can build a Fortran program successfully. cat >hello.f90 < wrote: > Can you build a Fortran program? I.e., does the following work? > > cat >hello.f90 < program hello > print *, 'Hello world' > end program > EOF > gfortran -o hello hello.f90 && ./hello > > Does `which gfortran`

Re: [R-pkg-devel] Problems with devtools::build() in R

Can you build a Fortran program? I.e., does the following work? cat >hello.f90

Re: [R-pkg-devel] Problems with devtools::build() in R

Actually, no, only locally… but so far all proposed solutions have failed. On Tue, May 16, 2023 at 7:11 PM Dirk Eddelbuettel wrote: > > Hi Jarrett > > On 16 May 2023 at 19:06, Jarrett Phillips wrote: > | I wonder if my problem is related to the question you posed about the > CRAN > | macOS build

Re: [R-pkg-devel] Problems with devtools::build() in R

Hi Jarrett On 16 May 2023 at 19:06, Jarrett Phillips wrote: | I wonder if my problem is related to the question you posed about the CRAN | macOS builders being down. If it is, then according to @Simon Urbanek, this | should be resolved in a few hours. | | Can you confirm?  Oh, maybe -- were yo

Re: [R-pkg-devel] Problems with devtools::build() in R

Hi Dirk, I wonder if my problem is related to the question you posed about the CRAN macOS builders being down. If it is, then according to @Simon Urbanek, this should be resolved in a few hours. Can you confirm? Thanks. Cheers, Jarrett On Tue, May 16, 2023 at 1:11 PM Dirk Eddelbuettel wrote:

Re: [R-pkg-devel] Problems with devtools::build() in R

I'm using R 4.3.0, newer than you, so that might affect things. Duncan On 16/05/2023 2:48 p.m., Jarrett Phillips wrote: Strange... the GitHub repo is up to date and that's what I'm trying to bundle up for a CRAN update. So, I'm thinking it's some kind of a system issue (I recently purchased a

Re: [R-pkg-devel] Problems with devtools::build() in R

Strange... the GitHub repo is up to date and that's what I'm trying to bundle up for a CRAN update. So, I'm thinking it's some kind of a system issue (I recently purchased a new MacBook Pro).. I'll investigate. Thanks! On Tue, May 16, 2023 at 2:09 PM Duncan Murdoch wrote: > I don't know what t

Re: [R-pkg-devel] Problems with devtools::build() in R

I don't know what the issue would be. I just tried remotes::install_github("jphill01/HACSim.R") and it worked fine, but I think that's not the same version that you are working with. Duncan Murdoch On 16/05/2023 2:01 p.m., Jarrett Phillips wrote: On Tue, May 16, 2023 at 2:00 PM Jarrett

Re: [R-pkg-devel] Problems with devtools::build() in R

On Tue, May 16, 2023 at 2:00 PM Jarrett Phillips wrote: > Yes, in addition to doing what @DirkEddelbuettel suggests. I keep getting > the same error... > > On Tue, May 16, 2023 at 1:47 PM Duncan Murdoch > wrote: > >> On 16/05/2023 1:14 p.m., Jarrett Phillips wrote: >> > Installing from the URL y

Re: [R-pkg-devel] Problems with devtools::build() in R

On 16/05/2023 1:14 p.m., Jarrett Phillips wrote: Installing from the URL you provide, as well as doing R CMD build HACSim as suggested by @JeffNewmiller fails. When trying the latter solution, I get the same error as the one provided in my original post. Any thoughts? Did you try Serguei's

Re: [R-pkg-devel] Problems with devtools::build() in R

Seems like you are on R 4.2.x, so you could try this one: https://github.com/R-macos/gcc-darwin-arm64/releases Gabor On Tue, May 16, 2023 at 7:16 PM Jarrett Phillips wrote: > > Installing from the URL you provide, as well as doing R CMD build HACSim as > suggested by @JeffNewmiller fails. > > Wh

Re: [R-pkg-devel] Problems with devtools::build() in R

Installing from the URL you provide, as well as doing R CMD build HACSim as suggested by @JeffNewmiller fails. When trying the latter solution, I get the same error as the one provided in my original post. Any thoughts? On Tue, May 16, 2023 at 12:52 PM Jarrett Phillips < phillipsjarre...@gma

Re: [R-pkg-devel] Problems with devtools::build() in R

On 16 May 2023 at 18:32, Serguei Sokol wrote: | Try to add in /src/Makevars: | | PKG_LIBS=$(FLIBS) Good catch. For every RcppArmadillo package we recommend (and inject if you use the RcppArmadillo.package.skeleton() helper) (and omit the earlier comment lines) PKG_CXXFLAGS = $(SHLIB_OPENMP_C

Re: [R-pkg-devel] Problems with devtools::build() in R

Hi Duncan, I actually installed gfortran from https://github.com/fxcoudert/gfortran-for-macOS/releases but I can instead install from the URL you provide. Hopefully this fixes the problem. I will respond here if there are still issues. Thanks. Cheers, Jarrett On Tue, May 16, 2023 at 12:39

Re: [R-pkg-devel] Problems with devtools::build() in R

On 16/05/2023 12:07 p.m., Jarrett Phillips wrote: Hi All, I'm trying to generate a `tar.gz` file on a Mac for R package submission to CRAN but am having issues. I'm using `devtools`, specifically `build()` and `install()`. My package relies on compiled code via `Rcpp/RcppArmadillo`. buil

Re: [R-pkg-devel] Problems with devtools::build() in R

Le 16/05/2023 à 18:07, Jarrett Phillips a écrit : Hi All, I'm trying to generate a `tar.gz` file on a Mac for R package submission to CRAN but am having issues. I'm using `devtools`, specifically `build()` and `install()`. My package relies on compiled code via `Rcpp/RcppArmadillo`. buil

Re: [R-pkg-devel] Problems with devtools::build() in R

В Tue, 16 May 2023 12:07:05 -0400 Jarrett Phillips пишет: >ld: warning: directory not found for option > '-L/opt/R/arm64/gfortran/lib/gcc/aarch64-apple-darwin20.6.0/12.0.1' >ld: warning: directory not found for option > '-L/opt/R/arm64/gfortran/lib' >ld: library not found

Re: [R-pkg-devel] Problems with devtools::build() in R

Your mistake is confusing a tool designed for _iterative development_ for a tool designed for _delivery_. Use R CMD build the way WRE says you should. On May 16, 2023 9:07:05 AM PDT, Jarrett Phillips wrote: >Hi All, > >I'm trying to generate a `tar.gz` file on a Mac for R package submission to

[R-pkg-devel] Problems with devtools::build() in R

Hi All, I'm trying to generate a `tar.gz` file on a Mac for R package submission to CRAN but am having issues. I'm using `devtools`, specifically `build()` and `install()`. My package relies on compiled code via `Rcpp/RcppArmadillo`. build("HACSim_OO") ── R CMD build ───

Re: [R-pkg-devel] Problems with news in ‘NEWS’

On 10/13/22 4:34 AM, Ivan Krylov wrote: В Wed, 12 Oct 2022 20:16:20 -0500 Spencer Graves пишет: I copied NEWS to NEWS.md and tried to format it as described in: https://r-pkgs.org/other-markdown.html#news Sadly, I still get the same error. It seems to be ignoring my NEWS.md f

Re: [R-pkg-devel] Problems with news in ‘NEWS’

В Wed, 12 Oct 2022 20:16:20 -0500 Spencer Graves пишет: > I copied NEWS to NEWS.md and tried to format it as described in: > > > https://r-pkgs.org/other-markdown.html#news > > > Sadly, I still get the same error. It seems to be ignoring > my NEWS.md file and continuing to tell me I

[R-pkg-devel] Problems with news in ‘NEWS’

Hello, All: devtools::check_rhub("Ecdat") complained: Problems with news in ‘NEWS’: Cannot process chunk/lines: 2022-10-12: Cannot process chunk/lines: Ecdat 0.4-2 updated "terrorism" to 2020. ... For more see below. This is with the current version of

Re: [R-pkg-devel] problems with HTML version of manual

My suggestion is to check with a recent version of R-devel which should produce god results, i.e. produces messages that need our attention. Best, Uwe Ligges On 31.05.2022 16:17, John Fox wrote: Dear Adelchi, This problem has been reported before: see

[R-pkg-devel] problems with HTML version of manual

Hi. I am preparing a new version of package mnormt. The package installs OK locally, but R CMD check --as-cran --run-donttest mnormt_2.1.0.tar.gz runs fine only up to * checking PDF version of manual … OK and then it says * checking HTML version of manual ... NOTE Found the following p

Re: [R-pkg-devel] Problems with too much testing

One of the basic principles of testing is "test interface, not implementation." Tests that violate this principle become "change detector tests" instead of "correctness tests" and essentially prevent any improvements to the code. In C++ objects have "public" and "private" methods, and the testing

Re: [R-pkg-devel] Problems with too much testing

I'm generally in accord with Duncan on this. There are inevitably situations where general rules don't apply. Our challenge is to find practical ways to keep the overall workload of all participants in the process to a minimum. JN On 2021-04-16 10:18 a.m., Duncan Murdoch wrote: > On 16/04/2021

Re: [R-pkg-devel] Problems with too much testing

On 16/04/2021 9:49 a.m., J C Nash wrote: Another approach is to change the responsibility. My feeling is that tests in the TESTING package should be modifiable by the maintainer of the TESTED package, with both packages suspended if the two maintainers cannot agree. We need to be able to move

Re: [R-pkg-devel] Problems with too much testing

Another approach is to change the responsibility. My feeling is that tests in the TESTING package should be modifiable by the maintainer of the TESTED package, with both packages suspended if the two maintainers cannot agree. We need to be able to move forward when legacy behaviour is outdated o

Re: [R-pkg-devel] Problems with too much testing

An offline message said "Oh, you mean you're asking for an actual object-oriented language that hides the internal representations of objects from users of a package. Unfortunately for all of us, that isn't R." Actually, I don't think that's what I want. We already have lots of languages l

Re: [R-pkg-devel] Problems with too much testing

> On 16 Apr 2021, at 14:06, Duncan Murdoch wrote: > > On 16/04/2021 7:54 a.m., Hugh Parsonage wrote: >> My 2c is that if a package has actually tested something like that >> (say, the ordering of a list's elements), then it is 100% likely that >> a script out there depends on that behaviour too

Re: [R-pkg-devel] Problems with too much testing

On 16/04/2021 7:54 a.m., Hugh Parsonage wrote: My 2c is that if a package has actually tested something like that (say, the ordering of a list's elements), then it is 100% likely that a script out there depends on that behaviour too. I suspect this test is not intentional, and it really wouldn

Re: [R-pkg-devel] Problems with too much testing

On 16/04/2021 7:40 a.m., brodie gaslam wrote: An all.equal method?  This might not work with 3rd edition though (untested), and I'm not sure what method registration requirements would exist for the user. It already has one, but it isn't used by testthat 3. Duncan Murdoch

Re: [R-pkg-devel] Problems with too much testing

My 2c is that if a package has actually tested something like that (say, the ordering of a list's elements), then it is 100% likely that a script out there depends on that behaviour too. In other words, the change is not inconsequential. R users are in debt to package developers but I think it be

Re: [R-pkg-devel] Problems with too much testing

An all.equal method?  This might not work with 3rd edition though (untested), and I'm not sure what method registration requirements would exist for the user. Best, B. On Friday, April 16, 2021, 6:09:24 AM EDT, Duncan Murdoch wrote: I'm updating the rgl package, and have come across the

[R-pkg-devel] Problems with too much testing

I'm updating the rgl package, and have come across the following problem. Some packages that depend on rgl and do careful testing are detecting inconsequential changes. A typical case is the nat package, which has extensive testing, some of which comes down to checking results from rgl functi

Re: [R-pkg-devel] problems with .mod files

files when building your > >> package. >> >> I hope this is helpful. >> >> Best, >> >> Remi >> >> >> On 2/26/19 10:00 PM, r-package-devel-requ...@r-project.org wrote: >>> Date: Mon, 25 Feb 2019 17:13:51 +0100 >>> From:

Re: [R-pkg-devel] problems with .mod files

t; > Best, > > Remi > > > On 2/26/19 10:00 PM, r-package-devel-requ...@r-project.org wrote: >> Date: Mon, 25 Feb 2019 17:13:51 +0100 >> From: "Rampal S. Etienne" >> To:R-package-devel@r-project.org >> Subject: [R-pkg-devel] problems with .mod files &

Re: [R-pkg-devel] problems with .mod files

-requ...@r-project.org wrote: > Date: Mon, 25 Feb 2019 17:13:51 +0100 > From: "Rampal S. Etienne" > To:R-package-devel@r-project.org > Subject: [R-pkg-devel] problems with .mod files > Message-ID: > Content-Type: text/plain; charset="utf-8" > > Hello, >

[R-pkg-devel] problems with .mod files

Hello, I have been trying for weeks to get a package on CRAN, but keep receiving warnings and notes, and errors using R-hub. The problems started when I used FORTRAN code to speed up some functions. This FORTRAN code introduces .mod files which are not accepted in the src folder. I followed sugges

Re: [R-pkg-devel] Problems with Notes for Package IncDTW

I modified a toy package I use for teaching to do the registration right (to serve as an example). See https://github.com/cjgeyer/foo/tree/master/package where packages foo and fooRegister do the same thing except for registration. Diffing them shows what is needed. -- Charles Geyer Professor, Sc

Re: [R-pkg-devel] Problems with Notes for Package IncDTW

On 22.06.2017 10:47, Maximilian Leodolter wrote: Hello, I would like to ask for your help. I want to contribute a package and fail because of two Notes. Here is the temporary directory: https://win-builder.r-project.org/incoming_pretest/170621_173212_IncDTW_010/ The first Note asks for spell

[R-pkg-devel] Problems with Notes for Package IncDTW

Hello, I would like to ask for your help. I want to contribute a package and fail because of two Notes. Here is the temporary directory: https://win-builder.r-project.org/incoming_pretest/170621_173212_IncDTW_010/ The first Note asks for spelling mistakes, which is a false positive. "DTW" means

Re: [R-pkg-devel] Problems with :::

> Kirill Müller > on Thu, 28 Jan 2016 17:42:12 +0100 writes: > On 28.01.2016 14:20, Duncan Murdoch wrote: >> If the class is just "mytable", then you'll have to >> change it to "ftable" before calling stats::format(). > Side note: The following will fail, because forma

Re: [R-pkg-devel] Problems with :::

On 28.01.2016 14:20, Duncan Murdoch wrote: If the class is just "mytable", then you'll have to change it to "ftable" before calling stats::format(). Side note: The following will fail, because format.ftable double-checks the class of its argument: format_ftable <- utils::getS3method("format",

Re: [R-pkg-devel] Problems with :::

On 28/01/2016 7:47 AM, David Scott wrote: I am trying to incorporate a print method for flat tables into the package xtable which I maintain. To format the flat table before printing, I wish to use format.ftable from the base package stats. This is unfortunately not exported, so R CMD check --as

Re: [R-pkg-devel] Problems with :::

Ho David, just rename the copied function to sg else. It does not even has to be s3, probably. Gabor On 28 Jan 2016 13:16, "David Scott" wrote: > I am trying to incorporate a print method for flat tables into the package > xtable which I maintain. > > To format the flat table before printing, I

[R-pkg-devel] Problems with :::

I am trying to incorporate a print method for flat tables into the package xtable which I maintain. To format the flat table before printing, I wish to use format.ftable from the base package stats. This is unfortunately not exported, so R CMD check --as-cran produces a warning because I acces