Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMake new dependency checks happy #1
Comments
|
edit Scratch that. This can't be the reason. I believe this issue is related to an issue I've started having building a package that imports gamboostLSS and mboost. Before R version 3.4.0, it worked fine. Now I cannot build the package and get the following error: Error in (function (dep_name, dep_ver = NA, dep_compare = NA) : I think I'm going to have to go back to a previous R version and version of all packages it imports and depends on in order for my package to no longer be broken. |
|
@hofnerb, I am still having trouble with my package, which depends on gamboostLSS. I have the latest versions of R and gamboostLSS (and all of its dependencies) installed as of R 3.4.1. I am importing both gamboostLSS and mboost. I'm using roxygen2 to build my package. I've confirmed that gamboostLSS is indeed the issue blocking a build of my package (by removing the imports from DESCRIPTION and NAMESPACE). Do I need to follow this recipe for gamboostLSS to work in my package? |
|
The above solution is only with regard to imported functions and was only there to get rid of a warning in the process of building / testing... So as you already figured out (if I understand the timing of your posts correctly) this cannot be the reason. I am having such problems when the library used for building/testing is not the standard library. I do not really know how and when this happens but it does. Sometimes it helps to switch from devtools to standard R tools (or vice versa, I am not sure) and / or to ignore that issue and rely on testing on travis-ci, appveyor (both via github) or win-builder (simply upload your package). Does this help or is it a real bug? |
|
Btw. I do not understand why gamboostLSS would block building your package (if you do not re-build vignettes which depend on gamboostlSS). For me such errors just occur when testing... |
To make the new dependency checks on CRAN happy go along the following recipe (as suggested by Kurt Hornik).
1.) Copy the functions listed after
Undefined global functions or variables:in the output fromR CMD checkin a variabletxt:2.) With the function
one can obtain the imports via
3.) Copy and paste the output to
NAMESPACE.4.) Add the packages to
ImportsinDESCRIPTION.