Re: [R-pkg-devel] Update timing of machines on CRAN?

blems like the current Fedora machine that continues to use the old Rust. Hope to see an update soon. Thanks to the staff for maintaining the infrastructure. Best, Tatsuya On 2023/12/01 23:43, Uwe Ligges wrote: On 01.12.2023 13:28, SHIMA Tatsuya wrote: Hi, I maintain the prqlr package

[R-pkg-devel] Update timing of machines on CRAN?

Hi, I maintain the prqlr package that uses rustc for compiling, so I regularly check the version of Rust on CRAN. And I have noticed that the Rust version of Fedora has been stagnant for the past few months and was wondering why, but upon investigation I realized that this is because Fedora on

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

ing on installation from github. > > I see your file src/rust/Cargo.lock has some references to github.com > <http://github.com> which is probably what has triggered this. I'm > sorry I cannot help further. > Good luck! > > On Thu, 31 Aug 2023 at 14:54, Dirk Eddelbue

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

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

ntined already to get the authorship straight. Best, Uwe Ligges On 27.08.2023 17:28, SHIMA Tatsuya wrote: 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 <https://github.com/serde

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

ason. Tim On 26 Aug 2023, at 22:22, Ivan Krylov wrote: 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. <https://CRAN.R-project.org/package=prqlr> I submitted prqlr 0.5.0 on 2023-08-13.

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

e first submission of prqlr 0.5.0, CRAN pointed out that the role of "The authors of the dependency Rust crates" should be changed to author, but nothing else was pointed out. Best, Tatsuya On 2023/08/27 6:22, Ivan Krylov wrote: > On Sat, 26 Aug 2023 11:46:44 +0900 > SHIMA T

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

find out is >> to ask. >> >> 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 >&

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

ons apply to other forms of “data”, e.g., .jar files. > > Source package tarballs should if possible not exceed 10MB. It is much > preferred that third-party source software should be included within > the package (as e.g. a vendor.tar.xz file) than be downloaded at > installation: if this req

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