Hi, This is in reply to Simon's request that I post on this topic separately from Hans' prior thread on rlang related problems. In the course of looking at a few CRAN packages for that thread, including my own, I noted on the CRAN checks page for each package, that the results logs indicate the use of "R Under development", rather than the current R release version. Specific example: The CRAN check page for rlang: https://cran.r-project.org/web/checks/check_results_rlang.html shows in row 10: r-release-macos-x86_64 OK If I click on OK to get the CRAN check log with the following URL: https://www.r-project.org/nosvn/R.check/r-release-macos-x86_64/rlang-00check.html noting that the above URL shows: .../r-release-macos-x86_64/... However, the log header shows: "using R Under development (unstable) (2021-02-19 r80028)" Thus, if I read correctly, while the link should be for the CRAN check results log for the package using R release (4.1.0), it appears to be using an R development version from February 19, 2021. If I check the same R Release logs for Linux and Windows for rlang: https://www.r-project.org/nosvn/R.check/r-release-linux-x86_64/rlang-00check.html and: https://www.r-project.org/nosvn/R.check/r-release-windows-ix86+x86_64/rlang-00check.html respectively, both indicate: using R version 4.1.0 (2021-05-18) in the log headers. If I check the rlang logs for other OSs on "r-devel", they indicate: "using R Under development (unstable) (2021-05-20 r80347)" Thus, a more recent development version of R from May 20, 2021. So, perhaps naively, I would presume a configuration issue for the macOS binaries on CRAN. Simon, does that clarify the point I was making in the prior thread? Thanks, Marc
CRAN Checks for R-Release appear to use R-Devel
3 messages · Simon Urbanek, Marc Schwartz
Marc, thanks, now it makes sense to me. Yes, the checks results don't seem to be synced and it is also missing the arm64 checks. I'll investigate. Thanks, Simon
On May 26, 2021, at 8:35 AM, Marc Schwartz <marc_schwartz at me.com> wrote: Hi, This is in reply to Simon's request that I post on this topic separately from Hans' prior thread on rlang related problems. In the course of looking at a few CRAN packages for that thread, including my own, I noted on the CRAN checks page for each package, that the results logs indicate the use of "R Under development", rather than the current R release version. Specific example: The CRAN check page for rlang: https://cran.r-project.org/web/checks/check_results_rlang.html shows in row 10: r-release-macos-x86_64 OK If I click on OK to get the CRAN check log with the following URL: https://www.r-project.org/nosvn/R.check/r-release-macos-x86_64/rlang-00check.html noting that the above URL shows: .../r-release-macos-x86_64/... However, the log header shows: "using R Under development (unstable) (2021-02-19 r80028)" Thus, if I read correctly, while the link should be for the CRAN check results log for the package using R release (4.1.0), it appears to be using an R development version from February 19, 2021. If I check the same R Release logs for Linux and Windows for rlang: https://www.r-project.org/nosvn/R.check/r-release-linux-x86_64/rlang-00check.html and: https://www.r-project.org/nosvn/R.check/r-release-windows-ix86+x86_64/rlang-00check.html respectively, both indicate: using R version 4.1.0 (2021-05-18) in the log headers. If I check the rlang logs for other OSs on "r-devel", they indicate: "using R Under development (unstable) (2021-05-20 r80347)" Thus, a more recent development version of R from May 20, 2021. So, perhaps naively, I would presume a configuration issue for the macOS binaries on CRAN. Simon, does that clarify the point I was making in the prior thread? Thanks, Marc
Simon, Thanks! Marc Simon Urbanek wrote on 5/25/21 4:47 PM:
Marc, thanks, now it makes sense to me. Yes, the checks results don't seem to be synced and it is also missing the arm64 checks. I'll investigate. Thanks, Simon
On May 26, 2021, at 8:35 AM, Marc Schwartz <marc_schwartz at me.com> wrote: Hi, This is in reply to Simon's request that I post on this topic separately from Hans' prior thread on rlang related problems. In the course of looking at a few CRAN packages for that thread, including my own, I noted on the CRAN checks page for each package, that the results logs indicate the use of "R Under development", rather than the current R release version. Specific example: The CRAN check page for rlang: https://cran.r-project.org/web/checks/check_results_rlang.html shows in row 10: r-release-macos-x86_64 OK If I click on OK to get the CRAN check log with the following URL: https://www.r-project.org/nosvn/R.check/r-release-macos-x86_64/rlang-00check.html noting that the above URL shows: .../r-release-macos-x86_64/... However, the log header shows: "using R Under development (unstable) (2021-02-19 r80028)" Thus, if I read correctly, while the link should be for the CRAN check results log for the package using R release (4.1.0), it appears to be using an R development version from February 19, 2021. If I check the same R Release logs for Linux and Windows for rlang: https://www.r-project.org/nosvn/R.check/r-release-linux-x86_64/rlang-00check.html and: https://www.r-project.org/nosvn/R.check/r-release-windows-ix86+x86_64/rlang-00check.html respectively, both indicate: using R version 4.1.0 (2021-05-18) in the log headers. If I check the rlang logs for other OSs on "r-devel", they indicate: "using R Under development (unstable) (2021-05-20 r80347)" Thus, a more recent development version of R from May 20, 2021. So, perhaps naively, I would presume a configuration issue for the macOS binaries on CRAN. Simon, does that clarify the point I was making in the prior thread? Thanks, Marc