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

Thanks Lluís, I did not know I could find it there. For this archive, CRAN sent me an e-mail urging me to stop downloading from crates.io and vendoring all Rust source code, even if it exceeds 5MB. On 2023/08/31 23:24, Lluís Revilla wrote: > The reasons that CRAN has for this (from: > https://c

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

To clarify: A packae must be single under a single license or a license and alternative licenes. You cannot have 2 licenses at the same time, hence ou have to relicense anyway. Of course, you have to check whether the licneses allow for it or seek confirmation from all copyright holders. If t

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

About licensing, On Sun, 27 Aug 2023 at 17:30, SHIMA Tatsuya wrote: > > Hi Ivan, thanks for taking the time to look at all the details of this. > > > You licensed the package as MIT. Are your dependencies compatible > with MIT? All direct dependencies of your Rust code seem to be licensed > unde

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

The reasons that CRAN has for this (from: https://cran.r-project.org/src/contrib/PACKAGES.in) are: X-CRAN-History: Archived on 2023-08-19 for policy violation. Downloading on installation from github. Unarchived on 2023-08-30. X-CRAN-Comment: Archived on 2023-08-31 for policy violation. .

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

On 31 August 2023 at 07:32, SHIMA Tatsuya wrote: | I submitted prqlr 0.5.1 yesterday, which is almost identical to prqlr | 0.5.0, and prqlr is now available again on CRAN. | Thanks to the CRAN reviewers for their quick reaction. And it is gone again (per CRANberries). Never a dull moment with C

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

I submitted prqlr 0.5.1 yesterday, which is almost identical to prqlr 0.5.0, and prqlr is now available again on CRAN. Thanks to the CRAN reviewers for their quick reaction. Best, Tatsuya On 2023/08/29 19:12, SHIMA Tatsuya wrote: Hi Uwe, thanks for the summary of the background. Let me ask you

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

Hi Uwe, thanks for the summary of the background. Let me ask you a few questions about a couple of points. > Accepting a package that downloads crates from github I don't think prqlr 0.5.0 downloads crates on GitHub. prqlr <= 0.4.0 use crate on GitHub which I patched to support old Rust on Debi

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

Friends, CRAN wrote initially to some rust using maintainers: The CRAN policy on authorship/copyright is very clear: "(’All components’ includes any downloaded at installation or during use.) " Please explain how your package complies if you believe it does. Further, we ask that you use the '

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

Hi Tim, thank you for sharing this information. i didn't know this. If this is the cause, the problem seems to have been resolved in the latest serde , so it seems to be possible to deal with it. Best, Tatsuya On 2023/08/27 20:24, Tim Taylor wrote

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

Hi Ivan, thanks for taking the time to look at all the details of this. > You licensed the package as MIT. Are your dependencies compatible with MIT? All direct dependencies of your Rust code seem to be licensed under either MIT or Apache-2.0, which seems to be compatible. I am not a legal exp

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

Simon, Thank you for taking a look at this. > One related issue with respect to CRAN policies that I don't see a good solution for is that inst/AUTHORS is patently unhelpful, because most of them say "foo (version ..): foo authors" with no contact, or real names or any links. I understand yo

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

Sarah, Thanks for taking a look at this. But what we see in the results page is the compiled size, and I think it is common for it to be huge. For example, looking at the arrow package 12.0.1.1 >, the size of t

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

Could you have been caught out with the precompiled binary that serde started distributing in a few of it’s versions (https://github.com/serde-rs/serde/issues/2538)? That could have been a reason if you pinned a version with it present but only CRAN could confirm if that was the reason. Tim >

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 ow

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 i

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: Version

[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.