Re: [Bioc-devel] build cache on bioconductor build system?

2018-05-31 Thread Vivek Bhardwaj
The name of my package is icetea. Here's the link to the submission. I checked today and VariantAnnotation build was passing now, so simply re-pushed with bumped version and it worked! (well not exactly, I still have the RSubread issue

Re: [Bioc-devel] build cache on bioconductor build system?

2018-05-31 Thread Shepherd, Lori
The single package builder has not built in the functionality to obey this particular BBSoption but should be active on the builder once officially accepted into Bioconductor. Your reviewer will be aware of this and be able to proceed with the review. Lori Shepherd Bioconductor Core Team Ro

Re: [Bioc-devel] Windows, normalizePath(), and non-ASCII characters

2018-05-31 Thread Obenchain, Valerie
Hi Mike, Is this still an issue or has it been resolved? Val On 05/22/2018 02:19 PM, Mike Smith wrote: In trying to diagnose this issue at https://support.bioconductor.org/p/108548/ I've found some weird behaviour with Windows, normalizePath(), and non-ASCII characters. Essentially, if I run no

[Bioc-devel] onLoad failed for rJava in nigthly 'devel' build

2018-05-31 Thread Lulu Chen
Dear Bioc Team, My package "CAMTHC" has been accepted and included in the nigthly 'devel' build . However, build error appears in "Windows Server 2012 R2 Standard / x64": install for i386 * installing *source* package 'CAMTHC' ... ** R ** data ** inst ** byte-compile and prepare package for laz

Re: [Bioc-devel] onLoad failed for rJava in nigthly 'devel' build

2018-05-31 Thread Obenchain, Valerie
Hi Lulu, Thanks for keeping an eye on the build report! It looks like something went wrong when the new version of rJava was installed on the Windows builders yesterday. Unfortunately today's builds started before we realized this so your package will likely have the same error on tomorrow's r

[Bioc-devel] rJava on Windows builders

2018-05-31 Thread Obenchain, Valerie
Just a heads up that the new version of rJava that came out 5/29/2018 failed to install on the Windows builders yesterday. Because of this we see an increased number of failures in both release and devel. Unfortunately I didn't notice this before the builds started today so we'll see the same er