Open marandet opened 1 week ago
This is not a bug, it is a requirement. setup-r-dependencies
requires access to GitHub Pages currently.
A workaround is to do these before using setup-r-dependencies
:
R_LIB_FOR_PAK
environment variable to point to a package librarypak-version: none
for setup-r-dependencies
.It is best to install pak into a different library than the one you use for your regular packages, in case some of those also required pak and need a different version.
Describe the bug
I am using these actions in a on-premise Github Enterprise installation. We are using our own package-manager that is configured to mirror several kind of repositories (from Docker artefacts and OS-Distributions to languages-specific libraries, including CRAN). The point is that all of this is within our internal network so that we do not allow our github runner to have access to the internet.
I successfully run the setup-r action, leveraging the RSPM environment variable and the extra-repositories option in order to point to our Artifactory. I also add a step in order to write the options.repos value within the Rprofile configuration file.
But the installation of the pak package still fails.
A clear and concise description of what the bug is.
To Reproduce
Here is an example of my use-case :
And the following error occurs in the Run r-lib/actions/setup-r-dependencies@v2 step, in the Run # Install pak substep.
Expected behavior
The installation of every package should leverage the options.repos configuration.
Additional context
I guess that the problem is in this specific line of code
https://github.com/r-lib/actions/blob/e6be4b3706e0f39bc7a4cf4496a5f2c4cb840040/setup-r-dependencies/action.yaml#L110