Closed pawelru closed 4 months ago
That is impossible because there are many unimportant packages on CRAN that will fail to install, or sometimes randomly. But usually the check for the package will still work.
So the best we can do is show you the error.
I think it's all depends on the dependency type. For hard deps (Depends, Imports, LinkingTo) I cannot imagine r-cmd-check to pass. For soft deps (Suggests, Enhances) things might pass actually.
All in all it comes down to the way how you install those deps. I noticed that you choose remotes
package. Recently I found myself more and more like the way how pak
(actually pkgdepends
) does it with caching, config possibilities and all of that. I do get this potentially could be a fundamental change to the logic so for the time being I'm looking for exposing error info more.
Yes we will switch to pak when the problems are resolved: https://github.com/r-universe-org/help/issues/393
Example: https://github.com/r-universe/pharmaverse/actions/runs/8878640984/job/24375069874
R CMD CHECK fails with a following error
The root-cause however is in the step earlier
"Install package dependencies"
:Let's not focus here on why install failed. My take away from this is that R CMD CHECK should not be started if the install deps step failed. It cannot be successfully completed if any of the hard deps is missing and this somewhat gives inaccurate message to the pkg maintainers. I immediately went checking deps specification and after confirming it's correct I have found out that the issue is elsewhere.