Re: [Bioc-devel] Best practice use pkgdown, docker with Bioconductor

Haven't used this, but I think you could use Github Action to merge master branch in the branch for pkgdown whenever changes on master are made. https://github.com/marketplace/actions/merge-branch BW, Andris -Original Message- From: Bioc-devel On Behalf Of Murphy, Alan E Sent: 06 April

[Bioc-devel] Change of maintainer of pmp package

Hi, Gavin Rhys Lloyd (g.r.ll...@bham.ac.uk) has agreed to take over maintaining of the pmp package. He already has Bioconductor credentials account as he is a maintainer on several other packages. Description file of the pmp package has been updated to reflect the ch

Re: [Bioc-devel] Help with setting up a build environment to match

Hi, Are you using R 4.00 on Ubuntu? Travis error indicates that you are using class(), output of this command has changed. https://www.bioconductor.org/developers/how-to/troubleshoot-build-report/#classEq BW, Andris On 24 Apr 2020 20:40, kone...@bcgsc.ca wrote: A package I maintain, contiBAI

Re: [Bioc-devel] ptime ERROR

ols package using R-devel (4.0.0) and the latest devtools package. I am using R command class to determine what data structure object belong to. Based on the object ty... BW, Andris From: lori.sheph...@roswellpark.org Sent: 06 February 2020 16:21:14 To: And

Re: [Bioc-devel] ptime ERROR

Hi Chris, Error message is caused by changes in R 4.0.0. You can find more details here https://developer.r-project.org/Blog/public/2019/11/09/when-you-think-class.-think-again/index.html. In short you have to check all cases where you are using `class()` in your code. BW, Andris

Re: [Bioc-devel] Install and Build ERROR - CeTF package

Build of clusterProfiler is failing because it depends on enrichplot 1.7.1, while only 1.7.0 is available. I guess you will have to wait or contact maintainers of these two packages. BW, Andris From: Bioc-devel on behalf of cbiag...@gmail.com Sent: 06 Febru

Re: [Bioc-devel] Question about github repo

Hi Krutik, You are looking at the "problem" from a wrong angle. If there are no any reasons raised by your PhD funding body to keep your repository closed, it's of your own benefit to have all the code public: a) There is chance that someone else in the world is working on something very sim