Re: [R-pkg-devel] What to do when a package is archived from CRAN

Simon, Ok, let's take a look at a real example. The first item of inst/AUTHORS of prqlr (GitHub version) is this: addr2line (version 0.20.0): addr2line authors You can find addr2line's owners on crates.io [1], while its manifest file (Cargo.toml) [2] doesn't contain the names of its

Re: [R-pkg-devel] What to do when a package is archived from CRAN

Yutani, > On Aug 27, 2023, at 2:19 PM, Hiroaki Yutani wrote: > > Simon, > > > it's assumed that GitHub history is the canonical source with the > > provenance, but that gets lost when pulled into the package. > > No, not GitHub. You can usually find the ownership on crates.io >

Re: [R-pkg-devel] What to do when a package is archived from CRAN

Simon, > it's assumed that GitHub history is the canonical source with the provenance, but that gets lost when pulled into the package. No, not GitHub. You can usually find the ownership on crates.io. So, if you want a target to blame, it's probably just a problem of the script to auto-generate

Re: [R-pkg-devel] Re-building vignettes had CPU time 9.2 times elapsed time

Tim, I think that things like data.table have a different set of problems depending on the environment. Working out what the right degree of parallelism for an IO workload is is a hard question that depends on the characteristics of the IO subsystem, the characteristics of the dataset and on what

Re: [R-pkg-devel] What to do when a package is archived from CRAN

Tatsuya, What you do is contact CRAN. I don't think anyone here can answer your question, only CRAN can, so ask there. Generally, packages with sufficiently many Rust dependencies have to be handled manually as they break the size limit, so auto-rejections are normal. Archival is unusual, but

Re: [R-pkg-devel] What to do when a package is archived from CRAN

On Sat, 26 Aug 2023 11:46:44 +0900 SHIMA Tatsuya wrote: > I noticed that my submitted package `prqlr` 0.5.0 was archived from > CRAN on 2023-08-19. > > > I submitted prqlr 0.5.0 on 2023-08-13. I believe I have since only > received word from CRAN that

Re: [R-pkg-devel] What to do when a package is archived from CRAN

Hi, You can generally see what the reason is from the archive page, where it says: A summary of the most recent check results can be obtained from the check results archive. On that page, https://cran-archive.r-project.org/web/checks/2023/2023-08-19_check_results_prqlr.html is the note:

[R-pkg-devel] What to do when a package is archived from CRAN

Hi, I noticed that my submitted package `prqlr` 0.5.0 was archived from CRAN on 2023-08-19. I submitted prqlr 0.5.0 on 2023-08-13. I believe I have since only received word from CRAN that it passed the automated release process.

Re: [R-pkg-devel] Re-building vignettes had CPU time 9.2 times elapsed time

I’m definitely sympathetic to both sides but have come around to the view of Greg, Dirk et al. It seems sensible to have a default that benefits the majority of “normal” users and require explicit action in shared environments not vice-versa. That is not to say that data.table could not do