On 05/02/2016 12:37 PM, Ludwig Geistlinger wrote:
So yes, you should update the NAMESPACE file following the warning
message you see in your build report.
Hi Martin, I did not encounter such a note on importing from base packages
ever before - but ok, I followed your suggestion and added the
> So yes, you should update the NAMESPACE file following the warning
> message you see in your build report.
Hi Martin, I did not encounter such a note on importing from base packages
ever before - but ok, I followed your suggestion and added the imports.
However all remaining NOTEs and WARNINGs t
On 05/02/2016 11:11 AM, Ludwig Geistlinger wrote:
I encounter the same issue with EnrichmentBrowser - and apparently,
several other packages too, e.g. ensembldb, erma, ExiMiR ...
The warnings seem to be, at first glance, linked to messages e.g. for
masking:
---
I encounter the same issue with EnrichmentBrowser - and apparently,
several other packages too, e.g. ensembldb, erma, ExiMiR ...
The warnings seem to be, at first glance, linked to messages e.g. for
masking:
---
* checking S3 ge
On Fri, 29-04-2016, at 23:49, Martin Morgan
wrote:
> On 04/29/2016 05:23 PM, Ramon Diaz-Uriarte wrote:
>> Dear All,
>>
>> In case it matters, and since we are past the 22, I just noticed that a
>> package I maintain (ADaCGH2) is giving warnings in Linux and Mac (e.g.,
>> https://www.bioconduct
On 04/29/2016 05:23 PM, Ramon Diaz-Uriarte wrote:
Dear All,
In case it matters, and since we are past the 22, I just noticed that a
package I maintain (ADaCGH2) is giving warnings in Linux and Mac (e.g.,
https://www.bioconductor.org/checkResults/devel/bioc-LATEST/ADaCGH2/zin2-checksrc.html)
th
Dear All,
In case it matters, and since we are past the 22, I just noticed that a
package I maintain (ADaCGH2) is giving warnings in Linux and Mac (e.g.,
https://www.bioconductor.org/checkResults/devel/bioc-LATEST/ADaCGH2/zin2-checksrc.html)
that, if I recall correctly, were not being given around
