-
Notifications
You must be signed in to change notification settings - Fork 4
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
"remotes" downloads incorrect SOILWAT2 submodule commit #175
Comments
Attempting with PR #172 remotes::install_github('DrylandEcology/rSOILWAT2#172') ... and it works! So maybe I just need to wait for this to be merged? |
Sorry for your trouble and the late response, @dylanbeaudette! Great to see that you figured out how to get it working. I can reproduce the error on my machine. The current rSOILWAT2 main branch works only with the second to latest version of SOILWAT2 main branch: the error message you see is due to changes in the latest version of SOILWAT2 that have not been reflected in rSOILWAT2. This is done on the development branch that you used with in the pull request #172. I had assumed that the specific commit that is registered for the SOILWAT2 submodule (in this case the second to last version) would be pulled when installing rSOILWAT2, but apparently it doesn't work and pulls the latest commit instead. Thanks for posting the error! |
Thanks @dschlaep. Any suggestions on when these changes will be merged with the main branch? I don't mind using the PR, but would like to eventually use rSOILWAT2 in production code. |
It seems that the issue we are having here is due to r-lib/remotes#260, i.e., "remotes" downloads the zip archive (instead of as a git repository) from github. Because of this, "remotes" cannot do what would be the correct way, i.e., Unfortunately, it appears that this is not something that we can fix on our side -- except avoiding the problem by attempting to not let SOILWAT2 and rSOILWAT2 get out of sync ... The only way to get an installation of rSOILWAT2 working correctly in this situation, as far as I know, that is until "remotes" correctly handles submodules, is to avoid using "remotes" (please tell me if you know of a way to make this work with the current "remotes"!), e.g.,
I am working on finalizing #172 and hopefully it will be done in the near future. Thanks for your interest in rSOILWAT2, @dylanbeaudette ! |
@dylanbeaudette For your information: I finalized the pull request, released as v5.0.1, and |
Excellent thank you! Issue closed then? |
Hi @dschlaep, thanks for all of the assistance. I'm finally returning to SOILWAT2 and rSOILWAT2. This time attempting to compile on Windows, using
R version 4.2.1 (2022-06-23 ucrt) Any suggestions? |
Sorry, that this is not working for you. I'm not sure what is going wrong, however, I don't believe it is an issue with rSOILWAT2:
The error message may suggest that Rtools42 doesn't fully work, e.g., that "make" is not working properly? |
Thanks for testing. I'll keep trying. I wasn't able to get a usable build from rhub because R CMD build won't complete locally. Could this have anything to do with our local installation of RTools? |
It seems that our non-standard installation directory for RTools was the problem. Thanks to @brownag, the solution is: Sys.setenv("RTOOLS42_HOME" = "C:/PROGRA~1/rtools42")
remotes::install_github("DrylandEcology/rSOILWAT2", build_vignettes = FALSE) |
Hi, trying to compile on Mac OS, R 4.0.2.
Any suggestions?
The text was updated successfully, but these errors were encountered: