On Tue, 7 Jan 2020 13:54:38 + Christian Martin Hennig wrote: > Are there any other options apart from rhub/docker to get wiser about > my errors and issues (error on debian-clang in a routine that shows > nothing suspicious on my machine I cannot answer your original questions, but I can
I was tracking down problems with my package yesterday that were specific to r-devel and I had trouble reproducing the errors. I believe the issue is that the rhub and the docker/rocker r-devel were not using the most recent version of r-devel. My solution was to add r-devel to my travis ci.
That's good to know. I'm still at a loss what to do though. How are you checking your packages on systems that are not available to you, other than using rhub? Chances are if something from Bioconductor is required by one of the packages that I require, I can't get rid of it, right? Thanks,
It is an R-hub bug: https://github.com/r-hub/rhub/issues/318 Gabor On Tue, Jan 7, 2020 at 2:05 PM Christian Martin Hennig wrote: > > I should maybe add that I'm not even sure why I need Bioconductor, the > package has: > > Imports: MASS, cluster, mclust, flexmix, prabclus, class, diptest, >
I should maybe add that I'm not even sure why I need Bioconductor, the package has: Imports: MASS, cluster, mclust, flexmix, prabclus, class, diptest, robustbase, kernlab, grDevices, graphics, methods, stats, utils, parallel Suggests: tclust, pdfCluster, EMMIXskew, mvtnorm Christian On 1/7/20
Hi there, I'm trying to track down some errors and issues of my fpc package. As I can't reproduce any of these on my machine, I'm using rhub and docker. I'm getting Bioconductor related issues with both local_check_linux("fpc_2.2-3.tar.gz", image = "rhub/debian-clang-devel") and