Re: [R-pkg-devel] "Writing R Extensions" manual needs update [was: Error handling in C code]

2024-06-23 Thread Tomas Kalibera
On 6/24/24 08:25, Agner Fog wrote: Jarrod Hadfield wrote: Using Rf_error() rather than error() fixed the problem. Not sure why the problem was only flagged on Debian, but it seems to have been triggered by R_NO_REMAP being defined (which will be default in R 4.5.0). I had the same problem.

[R-pkg-devel] "Writing R Extensions" manual needs update [was: Error handling in C code]

2024-06-23 Thread Agner Fog
Jarrod Hadfield wrote: > Using Rf_error() rather than error() fixed the problem. Not sure why the > problem was only flagged on Debian, but it > seems to have been triggered by R_NO_REMAP being defined (which will be > default in R 4.5.0). I had the same problem. A lot of functions in my packag

Re: [R-pkg-devel] Windows binary package not at mirrors

2024-06-23 Thread Agner Fog
It is probably checking the version anyway. If a binary package is available for a later version, then it may say something like: "The latest version of the binary package does not match your currently installed version of R. You may update R, or you may compile the package for the installed v

Re: [R-pkg-devel] Windows binary package not at mirrors

2024-06-23 Thread Duncan Murdoch
On 2024-06-23 8:01 a.m., Agner Fog wrote: Also, I think the system should recommend to the user to update RStudio when a package is not available for the installed version. The current message does not tell the cause of the problem. It just says: Do you want to install from sources the package

Re: [R-pkg-devel] Windows binary package not at mirrors

2024-06-23 Thread Agner Fog
Also, I think the system should recommend to the user to update RStudio when a package is not available for the installed version. The current message does not tell the cause of the problem. It just says: Do you want to install from sources the package which needs compilation? - Agner _

Re: [R-pkg-devel] Windows binary package not at mirrors

2024-06-23 Thread Helmut Schütz
Duncan Murdoch wrote on 2024-06-23 13:04: […] One exception is the one run by Posit: because it is cloud based, I think they spend quite a lot of money on it. […] it means that it is very reliable, and it's the one I use almost all the time. I agree. It is also helpful for developers of pack

Re: [R-pkg-devel] Windows binary package not at mirrors

2024-06-23 Thread Duncan Murdoch
On 2024-06-23 5:44 a.m., Agner Fog wrote: On 23/06/2024 09.56, Duncan Murdoch wrote: CRAN only builds Windows binaries for the devel version, the current release, and the previous release, so nothing older than 4.3.0 will get it. Thank you. Updating R helped. BTW, I don't think we need so ma

Re: [R-pkg-devel] Windows binary package not at mirrors

2024-06-23 Thread Agner Fog
On 23/06/2024 09.56, Duncan Murdoch wrote: CRAN only builds Windows binaries for the devel version, the current release, and the previous release, so nothing older than 4.3.0 will get it. Thank you. Updating R helped. BTW, I don't think we need so many mirrors. They were needed only a long

Re: [R-pkg-devel] Windows binary package not at mirrors

2024-06-23 Thread Duncan Murdoch
On 2024-06-23 2:18 a.m., Agner Fog wrote: On 23/06/2024 00.15, Duncan Murdoch wrote: As far as I know, CRAN doesn't push changes to the mirrors, the mirrors pull changes from CRAN.  So if you are seeing that message, the problem is likely with the mirror you're using.  Which mirror is that? All