-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
re-ordered steps in CRAN template #390
Conversation
There are snapshot tests which might fail since you updated templates |
Hm, it did not work it seems:
|
Let's add this version printing to not-cran templates as well. |
I have now added this to the non-cran templates as well. This PR is supposed to fix the no rustc version reported prior to compilation error that you reported. Maybe it is failing because I did not also add the changes to the non-cran templates? Will see if this next round of CI tests passes. |
Now version is reported but R check does not recognize it |
This pattern seems to be invalid |
Note that this is not true as of https://github.com/extendr/rextendr/pull/379/files. The new See https://cran.r-project.org/web/checks/check_results_fio.html and https://cran.r-project.org/web/checks/check_results_arcpbf.html which are using this new check. |
@beniaminogreen please update {rextendr} and call We can use this PR to remove the |
Thanks for this, will do! and I'll make those changes to the makevars files. @Ilia-Kosenkov I was looking at that regex last night and it also looks weird to me. I think there's an extra brace in there. Doesn't look like this issue affects the Best, |
This is resolved in the main branch. |
Hi all,
The new version of R CMD check now tests whether the rustc version is reported before any rust code is compiled (the new R CMD check source code is linked here).
As it stands the rextendr templates report the rustc and cargo version after the code is compiled, which does not pass the new tests. This PR switches two lines in the Makevars files so that the code first reports the rustc version, and then compiles the rust code.
I have used this change to successfully update my package, zoomerjoin so it passes the new CRAN tests, but the changes haven't fully propagated through to the CRAN package page yet. I will update the PR immediately if there end up being any issues with this approach.
Best,
Ben