Re: [Bioc-devel] covr

2017-02-27 Thread Stephanie M. Gogarten
Hi Estefania, After you commit to your github repository, you will need to explicitly push those changes to svn to get them into Bioconductor devel. I recommend following the instructions under "Dealing with prior history / merge conflicts" on this page: http://www.bioconductor.org/developer

Re: [Bioc-devel] Single Package Builder

2017-02-27 Thread Shepherd, Lori
The Single Package Builder is now online. Thank you for your patience. Lori Shepherd Bioconductor Core Team Roswell Park Cancer Institute Department of Biostatistics & Bioinformatics Elm & Carlton Streets Buffalo, New York 14263 From: Bioc-devel on behalf

[Bioc-devel] Single Package Builder

2017-02-27 Thread Shepherd, Lori
The Single Package Builder is currently offline. We are working on restoring and will update when it is back online. Lori Shepherd Bioconductor Core Team Roswell Park Cancer Institute Department of Biostatistics & Bioinformatics Elm & Carlton Streets Buffalo, New York 14263 This email me

Re: [Bioc-devel] Bioc releases and Bioconda

2017-02-27 Thread Kasper Daniel Hansen
On Mon, Feb 27, 2017 at 3:54 AM, Elena Grassi wrote: > > Bioconda developers are reasoning on a way to annotate bioc version, this > should fix the issue without any work needed on single packages versions. > You need this; your current approach will not work. You cannot assume that package aut

Re: [Bioc-devel] Bioc releases and Bioconda

2017-02-27 Thread Elena Grassi
On Fri, Feb 24, 2017 at 9:09 PM, Nitesh wrote: > Could you tell me more about which package you are trying to wrap a recipe > for? > Right now my packages: the recipes are working, but the helper skeleton script that create dependencies gets them from DESCRIPTION and if lower limits for version