`R CMD check` failure on Linux for CoRegNet
1
0
Entering edit mode
@6f6493f5
Last seen 7 months ago
Bulgaria

Hi,

The checks of CoRegNet fail on Linux due to missing Suggest declarations for BiocGenerics and RUnit:

* checking tests ...
  Running "runTests.R"
 ERROR
Running the tests in "tests/runTests.R" failed.
Last 13 lines of output:
  Loading required package: shiny
  Loading required package: arules
  Loading required package: Matrix

  Attaching package: "arules"

  The following objects are masked from "package:base":

      abbreviate, write

  [1] TRUE
  > BiocGenerics:::testPackage("CoRegNet")
  Error in loadNamespace(x) : there is no package called "BiocGenerics"
  Calls: loadNamespace -> withRestarts -> withOneRestart -> doWithOneRestart
  Execution halted

I've opened a Pull Request with a fix.

Regards,

Martin

CoRegNet • 344 views
ADD COMMENT
0
Entering edit mode
@james-w-macdonald-5106
Last seen 18 hours ago
United States

As with your other question, the answer is there for you to read!

Error in loadNamespace(x) : there is no package called "BiocGenerics"

Any time R says "there is no package", that's a big hint that you need to install the package that R says isn't there.

0
Entering edit mode

Hi James,

Thanks again for your responses!

As I explained in my other question the dependencies should be declared in the package's DESCRIPTION file. In Bioc 3.18 a special property (_R_CHECK_SUGGESTS_ONLY_=true) is set which purpose is to break the builds/checks for all packages which were using globally installed dependencies without declaring them in their DESCRIPTION file. In devel/3.18 the package maintainers should fix the issues by explicitly listing all package's dependencies.

Regards, Martin

ADD REPLY
0
Entering edit mode

Oh, right. All questions about package development should go to the developers listserv at bioc-devel@r-project.org

ADD REPLY

Login before adding your answer.

Traffic: 734 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6