Known Issues & Solutions
If your issue is not listed here, please email Uri about it, or create an issue on groundhog's github page.
Current issues
Issue #1. Failure to install from source There are two likely causes behind a failure to install from source. Possible cause #1. Outdated database used by groundhog to find packages. (you do need three :::, not the usual two ::) Possible cause #2. Missing package in the operating system. MAC example the installation of the package Matrix will fail. Among the copious output in your console you will find this line indicating that gfortran is missing. You just need to install it from here https://mac.r-project.org/tools/, then Old Issue #1. Persistent package version conflict With groundhog v<2.0, conflicts with a different version of the same package would sometimes persist after restarting R session (when R Studio would automatically load needed packages) and the solution was to uninstall the packages creating the conflict. Since v2.0 that is handled automatically. Old Issue #2. 'This does not look like a tar archive' With groundhog v<1.5, older Windows machines would produce error 'This does not look like a tar archive' when installing binaries.
This affects some 'recommended' packages (typically 'MASS' or 'Matrix'), when attempting to load them with a groundhog day in 2022. To solve this issue, update groundhog's internal database by running:
groundhog:::load.cran.toc(TRUE)
A more likely problem is actually unrelated to groundhog. It involves not having a piece of software that R needs to install packages from 'source'. If you read the error message in your console you are likely to find the piece of software that's missing indicated.
If on Mac Big Sur OSX 11, you run
groundhog.library('lme4', '2020-12-01')
Matrix
, and thus lme4
, will successfully install.Solved issues, affecting older versions of groundhog