Skip to content

Conversation

@schloerke
Copy link

👋 terra Team! The Shiny Team has a few Apps that require {terra} for our nightly testing. While it isn't a blocker, it'd be nice to remove the false positives involving installation errors for {terra} and R 4.1 / 4.2.

We are testing using the same r-lib/actions to install the packages. I've updated the GHA script to test on all Windows versions to reprex the behavior within this PR. (Marking PR as "draft" as it isn't intended to be merged)

Request: If I could get an incantation (or code changes) for {terra} to install, I would be most grateful!

Thank you!

cc @karangattu


I believe if terra is able to be installed, then windows binaries will also be created for R 4.1 / 4.2... which also benefits older R windows users.

PPM+terra: (Must change the OS and R version manually near bottom of page)
Screenshot 2025-11-13 at 1 34 42 PM
Screenshot 2025-11-13 at 1 35 13 PM

Updated R CMD check workflow to include additional R versions and removed macOS system dependencies step.
@rhijmans
Copy link
Member

Happy to help if I can, but I do not understand what false positives you are talking about, nor do I understand what you would like me to do.

@brownag
Copy link
Contributor

brownag commented Nov 13, 2025

Happy to help if I can, but I do not understand what false positives you are talking about, nor do I understand what you would like me to do.

I think @schloerke wants you to approve the workflows to run so the error that is apparently preventing build will show up in CI.
image

Since it is Windows, I am wondering if there is an issue with libs provided with the particular version of RTools being used by posit package manager for 4.1/4.2--perhaps something similar to this: #881

@schloerke
Copy link
Author

Yes. If you can approve the workflows, you'll see the R4.1 and R4.2 fail to compile terra.

Goal: compile terra for GitHub Actions on Windows for R4.1/4.2.

@schloerke
Copy link
Author

@rhijmans
Copy link
Member

I looked into this but I was not able to fix the problem. It should be possible to fix this, of course, but I do not have the time for it as this does not appear to be a big problem. I appreciate your extensive testing and that this is a bit of a nuisance. I will try to better in the future.

@schloerke
Copy link
Author

Thank you for taking a look, @rhijmans ! I appreciate it.

Closing the PR

@schloerke schloerke closed this Nov 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants