Re: [Bioc-devel] Imports, depends and warnings

So a preliminary diagnosis is that some packages are not building even though they build in the nightly builds. The problem could be a newer compiler, newer R-devel, slightly different OS (debian vs ubuntu) or something else. Investigating further. However, in the meantime,

Re: [Bioc-devel] Imports, depends and warnings

Can you be more specific about which docker image you pulled? Dan - Original Message - > From: "Federico Marini" > To: "Martin Morgan" , "bioc-devel" > > Sent: Thursday, March 3, 2016 1:20:46 AM > Subject:

Re: [Bioc-devel] License question for experimental data package

Thank you all for the useful suggestions and links. I like the idea of using a CC0 license. That's likely what I will go for. Best, davide On Fri, Mar 4, 2016 at 7:42 AM Tim Triche, Jr. wrote: > I was going to mention droit d'auteur under EU common law, but somehow >

Re: [Bioc-devel] Package reference manuals in html

Using the integrated help system is nice, but isn't always ideal. Just for example: when I'm ssh'd into my work cluster I don't get a nice web page, I instead get the ascii-formatted version, which is considerably harder to read and doesn't include proper links. Running a second local instance

Re: [Bioc-devel] spliceSites Vignette build error

I can reproduce the error quite consistently by running either R CMD build or by sourcing the Stangled vignette. Here is my sessionInfo after doing the latter. If you are running an older R devel please update it. > sessionInfo() R Under development (unstable) (2016-02-25 r70222) Platform:

Re: [Bioc-devel] Identify Bioc build machines

There are a number of variables defined. You could check to see if the variable BBS_HOME is defined (it does not matter what the value is in your case, just whether it is defined or not). Dan - Original Message - > From: "Thomas Dybdal Pedersen" > To:

Re: [Bioc-devel] spliceSites Vignette build error

Are you using R-devel on your computer? - Original Message - > From: "Wolfgang Kaisers" > To: "bioc-devel" > Sent: Friday, March 4, 2016 12:41:30 AM > Subject: [Bioc-devel] spliceSites Vignette build error > Dear All, > >

Re: [Bioc-devel] License question for experimental data package

I am pretty sure in general "data" is not copyrightable per se ( http://www.lib.umich.edu/copyright/facts-and-data), so while I might contact the original authors as a courtesy, if the data has been released into any public database, then you should be free to do with it as you please. Providing

Re: [Bioc-devel] Package reference manuals in html

Hi, this is just to clarify the relation between the two github repos https://github.com/Bioconductor-mirror/BiocStyle and https://github.com/Bioconductor/BiocStyle mentioned by Martin: actually, these two are perfectly in sync right now. The "This branch is 3 commits ahead, 3 commits behind

Re: [Bioc-devel] Package reference manuals in html

One thing about accessing the html versions locally (e.g., via ? with options(help_type="html")] or help.start() or Rstudio) is that you get the version relevant to your R / Bioconductor, rather than whatever is at the top of google; I guess the same applies to the pdf versions, and the reason

[Bioc-devel] Identify Bioc build machines

Hi Are there any environment variables set on the bloc build machines that unique identify them as such? The reason I ask is that I’m planning to create a testthat PR that adds a skip_on_bioc (similar to skip_on_cran) function. While I know you generally shouldn’t skip unit tests on build

Re: [Bioc-devel] SVN Commit - Problem with the Version Number

Dear all, Thanks a lot for your help. I managed to commit the new version of the package to the release branch. Many thanks again for your replies. Best, Sandro On 3 Mar 2016 16:28, "Dan Tenenbaum" wrote: > You can merge from devel into release (as long as it's only bug