Re: [Bioc-devel] Pushing updates in the release branch

2016-05-26 Thread Dario Strbenac
Hello, As a Bioconductor package user, I would prefer that the data didn't change at all in the release variety of ENCODExplorer. It makes a user's research results more stable and reproducible and there's an opportunity every six months to change it when the Bioconductor development variety be

Re: [Bioc-devel] there is no package called 'zlibbioc' on WINDOWS

2016-05-26 Thread Dan Tenenbaum
It's an as yet unknown problem with the build system. It's very likely that it will resolve itself in tonight's builds. Dan On May 26, 2016 5:04:43 PM PDT, Monther Alhamdoosh wrote: >​Hi developers, > >Our package named EGSEA seems to fail to be built on Windows​ as it >depends >on "gage" whi

Re: [Bioc-devel] Pushing updates in the release branch

2016-05-26 Thread Obenchain, Valerie
Hi Charles, Yes, the usual advice is that you touch release for bug fixes only but can update as often as you like in devel. This is the same pattern followed for our experimental data and annotation packages. Once we have a release those data are frozen and for 6 months are considered the 'curren

[Bioc-devel] there is no package called 'zlibbioc' on WINDOWS

2016-05-26 Thread Monther Alhamdoosh
​Hi developers, Our package named EGSEA seems to fail to be built on Windows​ as it depends on "gage" which depends on zlibbioc. The problem appears in the release branch and not in the devel branch. Error in loadNamespace(i, c(lib.loc, .libPaths()), versionCheck = vI[[i]]) : there is no package