You'll just need to wait for that build error to resolve.
On Tue, Mar 26, 2019 at 10:45 AM Yue Zhao (Jason) wrote:
> Thanks, Michael. I saw this error in the bioC 3.9 package building step for
> my package, so I'm not sure how to specify the S4Vector version in that.
>
> On Tue, Mar 26, 2019 at
Thanks, Michael. I saw this error in the bioC 3.9 package building step for
my package, so I'm not sure how to specify the S4Vector version in that.
On Tue, Mar 26, 2019 at 1:35 PM Michael Lawrence
wrote:
> DESeq2 seems to be working with S4Vectors 0.21.19. If you're using an
> older version,
That first error has resolved, and I have new errors on the build on
Windows and on OSX, while the Linux build goes fine.
I have build and check and test on OSX and Windows on my end and everything
works. There must be something different on the Bioc build servers I am not
matching up with. The
DESeq2 seems to be working with S4Vectors 0.21.19. If you're using an older
version, you'll need to update once that version appears in the repository.
Sorry for the mess. Trying to clean up the [<- stuff on DataFrame and
Vector to make them easier to extend.
On Tue, Mar 26, 2019 at 10:19 AM Yue
A new error showed up: logical subscript contains NAs
*--*
*Yue (Jason) Zhao*
PhD Candidate, Bioinformatics Program
Boston University
yu...@bu.edu
On Sat, Mar 23, 2019 at 11:22 AM Michael Lawrence via Bioc-devel <
bioc-devel@r-project.org> wrote:
> This is due to some buggy changes to the
Is there a standard system loadout I should be matching? Something must be
different between my Windows build server and the bioconductor one.
I need to reproduce the error in order to debug it, but everything is
building fine locally.
On Tue, Mar 26, 2019 at 12:21 PM Yue Zhao (Jason) wrote:
>
Hi all,
I noticed that bioc_check on devel checks for R version dependency, and
produces a warning to change R dependency to 3.6 (currently set as R >=
3.5.0). Just quickly looking at Bioconductor packages, it seems that at
least half of the packages will have this warning, if tested. It also
well, we can't fix this in old branches of Bioc.
Sure, but one could say that about breaking changes to any CRAN package.
Nothing particularly special about BH on that point.
My POV is that we need to consider - in some sense - lock down CRAN with
a Bioc release.
That's probably worth
