* checking package dependencies ... ERROR Package suggested but not available: 'ropls' The suggested packages are required for a complete check. variable _R_CHECK_FORCE_SUGGESTS_ to a false value. Checking can be attempted without them by setting the environment See section 'The DESCRIPTION file' in the 'Writing R Extensions' manual.
biocViews:to the DESCRIPTION file
Congrats on the CRAN acceptance!
I wonder whether it's something related to stuff discussed inr-hub/rhub#38, the wrong URL seems to be used on the builder https://builder.r-hub.io/status/holodeck_0.1.0.tar.gz-283b3d146341419893250c279f67f155#L276
Seems to be working well for me now, thanks!
One question: I tried a simple intregration with GitLab CI with good success, but currently I am accessing the check results via private fields pretty much like so:
cr <- rhub::check(platform = platform, show_status = TRUE) statuses <- cr[[".__enclos_env__"]][["private"]][["status_"]]
What would be a better (recommended) way to process results ? Eg. Number of errors, warnings and notes?
Fulls script for reference: https://gitlab.com/jozefhajnala/jhaddins/blob/experimental/inst/rhubcheck.R
Preparing to build
Remotesfield to the DESCRIPTION file, see. e.g. https://github.com/r-lib/remotes/blob/master/vignettes/dependencies.Rmd R-hub will see this and install that dependency from the referred GitHub (or other) repository.
This is my first use of R-hub and I am wondering what if anything I can do about the follow results.
I have an OK for Fedora Linux, R-devel, clang, gfortran, a Note on the USERDOMAIN WIN-BUILDER-3 about the license, and an Error on RHUB_PLATFORM=linux-x86_64-ubuntu-gcc -- 1: In i.p(...) :
6186#> installation of package ‘openssl’ had non-zero exit status
6187#> 2: In i.p(...) : installation of package ‘httr’ had non-zero exit status
6188#> 3: In i.p(...) : installation of package ‘covr’ had non-zero exit status
6189#> 4: In i.p(...) :
6190#> installation of package ‘Rlabkey’ had non-zero exit status
6191#> 5: In i.p(...) :
6192#> installation of package ‘pkgdown’ had non-zero exit status
6193#> 6: In i.p(...) :
6194#> installation of package ‘/tmp/RtmpOpdAZC/file1313a7348e2/nprcmanager_0.5.31.tar.gz’ had non-zero exit status
fedora-clang-devel(https://builder.r-hub.io/status/dupree_0.2.0.tar.gz-2a2ad3c22aa6408499d5a2fcb42c82d2); this seems to result from not being able to install xml2=1.2.2 (due to the absence of libxml2). My package built ok on a couple of other platforms and on appveyor/travis - so I'm wondering if there's anything I need to do to ensure xml2 can be installed on rhub's fedora platform
standalone.cls(https://builder.r-hub.io/status/texPreview_1.4.2.tar.gz-8f384c90899541f296ad7034829a77d4). What is the appropriate way to reslove this issue? I do not seem to be getting this same error on CRAN checks (the failure there is more downstream after the tex is rendered) https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-fedora-clang/texPreview-00check.html.
this is my first time using R-hub. As the maintainer of the mousetrap package, I received an email today from CRAN about an error message that occurs when the package is checked with r-devel-linux-x86_64-debian-clang. To replicate the error, I ran the following code (in the local copy of my GitHub repository):
check_results <- rhub::check_for_cran()
However, the code always gets stuck at:
I also tried using the web interface but it failed (https://builder.r-hub.io/status/mousetrap_3.1.3.tar.gz-beb8e6f6d385740880017a3c766d2067)
Do you have any idea what went wrong and if I made a mistake?
Thanks! Best, Pascal
rhub::list_my_checks()to see if your check(s) are in progress or not.
rhub::get_check(<id>)$livelog()to get the live log.