Re: [R-pkg-devel] Deprecating apparent S3 method, changing name

2024-10-01 Thread Murray Efford via R-package-devel
: Wednesday, 2 October 2024 00:45 To: Jan van der Laan Cc: Murray Efford ; Murray Efford via R-package-devel Subject: Re: [R-pkg-devel] Deprecating apparent S3 method, changing name � Tue, 1 Oct 2024 09:00:24 +0200 Jan van der Laan �: > S3method(esa, plot, esaplotmethod) > > To

Re: [R-pkg-devel] Deprecating apparent S3 method, changing name

2024-09-29 Thread Murray Efford via R-package-devel
ort(esa) export(esa.plot) export(esaPlot) Am I doing something different than you are? Jan On 9/25/24 07:13, Murray Efford via R-package-devel wrote: > A package of mine on CRAN has some old function names (not S3 methods) that > include "." (e.g., "esa.plot").

Re: [R-pkg-devel] Deprecating apparent S3 method, changing name

2024-09-26 Thread Murray Efford via R-package-devel
September 2024 08:48 To: Murray Efford via R-package-devel Cc: Murray Efford Subject: Re: [R-pkg-devel] Deprecating apparent S3 method, changing name � Wed, 25 Sep 2024 05:13:31 + Murray Efford via R-package-devel �: > When I deprecate the old functions (by exporting a shell funct

[R-pkg-devel] Deprecating apparent S3 method, changing name

2024-09-24 Thread Murray Efford via R-package-devel
A package of mine on CRAN has some old function names (not S3 methods) that include "." (e.g., "esa.plot"). In a new version I want to simultaneously 1. rename these functions to e.g. "esaPlot" 2. export a new S3 generic with the base name (e.g. "esa") and methods for different model types (e.g.

Re: [R-pkg-devel] Additional issues: Intel segfault

2024-03-10 Thread Murray Efford
From: Ivan Krylov Sent: Saturday, 2 March 2024 20:45 To: Murray Efford Cc: R-package-devel@r-project.org Subject: Re: [R-pkg-devel] Additional issues: Intel segfault � Sat, 2 Mar 2024 02:07:47 +0000 Murray Efford �: > Gabor suggested > https://apc01.safelinks.protection.outlook

Re: [R-pkg-devel] Additional issues: Intel segfault

2024-03-01 Thread Murray Efford
mains a mystery, but not one I need to pursue. Murray From: Ivan Krylov Sent: Friday, 1 March 2024 21:46 To: Murray Efford Cc: R-package-devel@r-project.org Subject: Re: [R-pkg-devel] Additional issues: Intel segfault В Fri, 1 Mar 2024 07:42:01 + Murray Efford пишет: > R CMD check sug

[R-pkg-devel] Additional issues: Intel segfault

2024-02-29 Thread Murray Efford
nts me submitting a new version to CRAN, or whether I should submit regardless. Murray Efford __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] macOS results not mirrored/updated at CRAN

2023-07-15 Thread Murray Efford
For the record, the problem is more general: the r-release-macos-x86_64 CRAN checks of my package secr failed to update for 4.6.0 (2023-05-23) or 4.6.1 (2023-07-10) and remain stuck at version 4.5.10 (all MacOS binaries updated OK). From: R-package-devel

Re: [R-pkg-devel] CRAN submission with warnings

2021-07-26 Thread Murray Efford
FWIW my package 'secr' has for some time had the same 'abort', 'exit' or 'printf' issue when checked locally on Windows. It is happily accepted by CRAN, and I have learned to ignore the local message. The only common element I can see between secr 4.4.5 and rtree 0.2.0 is that both import and li

Re: [R-pkg-devel] package test returns error when R version 4.1.0

2021-07-07 Thread Murray Efford
Likewise: secr now passes on Winbuilder for R-release. Thanks Murray From: Gianmarco Alberti Sent: 08 July 2021 08:21 To: r-package-devel@r-project.org Cc: Murray Efford; Duncan Murdoch; Alex Chubaty; Uwe Ligges Subject: Re: [R-pkg-devel] package test

Re: [R-pkg-devel] package test returns error when R version 4.1.0

2021-07-06 Thread Murray Efford
had a new version on CRAN 18th June. Murray Efford From: R-package-devel on behalf of Duncan Murdoch Sent: 07 July 2021 08:28 To: Alex Chubaty Cc: r-package-devel@r-project.org Subject: Re: [R-pkg-devel] package test returns error when R version 4.1.0 On

Re: [R-pkg-devel] State of stringi and stringr

2021-05-13 Thread Murray Efford
Thanks for clearing that up so quickly. Murray From: Uwe Ligges Sent: 14 May 2021 13:12 To: Murray Efford; r-package-devel@r-project.org Subject: Re: [R-pkg-devel] State of stringi and stringr On 14.05.2021 02:32, Murray Efford wrote: > CRAN checks

[R-pkg-devel] State of stringi and stringr

2021-05-13 Thread Murray Efford
CRAN checks of 'secr' 4.4.1 (https://CRAN.R-project.org/package=secr) show an error on r-oldrel-windows-ix86+x86_64 : ** byte-compile and prepare package for lazy loading Error in loadNamespace(i, c(lib.loc, .libPaths()), versionCheck = vI[[i]]) : there is no package called 'stringi' 'secr' i

Re: [R-pkg-devel] Default number of cores <=2

2020-02-09 Thread Murray Efford
e understand. Murray From: Uwe Ligges Sent: Monday, 10 February 2020 1:37 a.m. To: Murray Efford; r-package-devel@r-project.org Subject: Re: [R-pkg-devel] Default number of cores <=2 On 09.02.2020 09:56, Murray Efford wrote: > The CRAN Repository Policy

[R-pkg-devel] Default number of cores <=2

2020-02-09 Thread Murray Efford
The CRAN Repository Policy (revision 4170) states "If running a package uses multiple threads/cores it must never use more than two simultaneously: the check farm is a shared resource and will typically be running many checks simultaneously" and I try to respect this limit in package example cod

Re: [R-pkg-devel] Simple URL error

2017-12-02 Thread Murray Efford
Thanks. I have not seen any problem with that site (checking several times this afternoon) and I assume it is now OK. Package resubmitted. Murray From: Uwe Ligges Sent: Saturday, 2 December 2017 12:23 p.m. To: Murray Efford; r-package-devel@r-project.org

[R-pkg-devel] Simple URL error

2017-12-01 Thread Murray Efford
Hi all This is no doubt a trivial question but I haven't found a direct answer on searching. My package passes R CMD check locally and on winbuilder (R-release and R-devel) but stalled in CRAN submission with - Found the following (possibly) invalid URLs: URL: http://www.phidot.org/forum/inde

[R-pkg-devel] C function dbinom_raw missing on r-oldrel-windows-ix86+x86_64

2015-12-07 Thread Murray Efford
My recent revision of the package 'secr' has been accepted by CRAN, but I see from the Check Results that installation fails (see link below) on r-oldrel-windows-ix86+x86_64 (alone) because it cannot find dbinom_raw (which I now call directly). Is there an easy fix, and should I bother? https://ww