Re: [Bioc-devel] a pattern to be avoided? mcols(x)$y <- z

2018-11-06 Thread Pages, Herve
Hi Vince, It looks like Michael took care of this in devel (thanks Michael):   https://github.com/Bioconductor/GenomicRanges/issues/11 H. On 10/3/18 08:20, Hervé Pagès wrote: > Hi Vince, > > This issue was reported here a couple of weeks ago: > >

Re: [Bioc-devel] How would you identify a package causing a NAMESPACE issue that you don't depend on in your DESCRIPTION/NAMESPACE?

2018-11-06 Thread Leonardo Collado Torres
Thank you for the info Martin and Michael! In the particular situation with recount and the xts warning, re-installing data.table 1.11.8 worked with xts 0.11.2. Details are further below. Best, Leo On Mon, Nov 5, 2018 at 6:49 PM Michael Lawrence wrote: > > For the general problem of

[Bioc-devel] Commits not appearing in bioconductor build

2018-11-06 Thread Clare Pacini
Hi all, I have pushed some changes to a package DrugVsDisease but after 2 builds on bioconductor it is not showing any updates to the package. Any suggestions? Thanks Clare dhcp-10-248-132-213:DrugVsDisease clare$ git commit -m "add import From" [master c8faca2] add import From 1 file

Re: [Bioc-devel] Commits not appearing in bioconductor build

2018-11-06 Thread Turaga, Nitesh
After a push is made it can take up to 48 hours for it to appear on the build report and landing pages - i.e. we do one pull, build, check, propagate in 24 hours - so if your commit was after the pull for the day it wont be until the following day.

Re: [Bioc-devel] Commits not appearing in bioconductor build

2018-11-06 Thread Shepherd, Lori
The version we have in git and that is building on devel is 2.25.1 which was pushed on November 4th. If you made any additional changes please make sure they are pushed to g...@git.bioconductor.org:packages/DrugVsDisease.git There have been no pushes to the RELEASE_3_8 branch. Lori Shepherd

Re: [Bioc-devel] Commits not appearing in bioconductor build

2018-11-06 Thread Shepherd, Lori
And as Nitesh said additional pushes can take up to 48 hours to appear - They also would need a valid version bump in order to be picked up by the builders. Lori Shepherd Bioconductor Core Team Roswell Park Cancer Institute Department of Biostatistics & Bioinformatics Elm & Carlton Streets

[Bioc-devel] WARNING on tokay1 for SIAMCAT package

2018-11-06 Thread Konrad Zych
Hi all, our package got a check warning on tokay1 and I cannot figure out where it is coming from. The Warning: * checking whether package 'SIAMCAT' can be installed ... WARNING Found the following significant warnings: Rd warning:

[Bioc-devel] About the reproducibility of BioC server environment

2018-11-06 Thread 露崎 弘毅
Dear Bioc Core Team I have created many Bioconductor packages, but it is always hard to pass the R CMD CHECK/BiocCheck. Especially, it is still difficult to construct the identical environment of single/daily package builder in the local machine. Sometimes the error is caused by the

Re: [Bioc-devel] WARNING on tokay1 for SIAMCAT package

2018-11-06 Thread Shepherd, Lori
Similarly answered here: https://stat.ethz.ch/pipermail/bioc-devel/2018-October/014139.html I think there is a reference here https://stackoverflow.com/questions/48430093/how-do-i-resolve-rd-warning-missing-file-link-when-building-packages-in-rstudio So for example: Where the actual name of

Re: [Bioc-devel] About the reproducibility of BioC server environment

2018-11-06 Thread Martin Morgan
Thanks for the comments. A docker image doesn't help with differences between operating systems. A docker image wouldn't be practical for the build system, where there are 1000's of packages installed. A docker image would need to be updated daily, since that is what the build system does;

Re: [Bioc-devel] About the reproducibility of BioC server environment

2018-11-06 Thread Kasper Daniel Hansen
In my experience, if I aggressively update my development installation of Bioconductor (including occasional updates of R-devel when appropriate) I can usually replicate most-all failures on the build server which has the same OS as my local machine. It does require aggressive updating though.