Hi Tim,
This package should be fixed now. I've synced your github repo with the one on
git.bioconductor.org.
Please check to make sure everything is as expected including the size.
Best,
Nitesh
On 4/1/21, 6:22 AM, "Bioc-devel on behalf of Triche, Tim"
<bioc-devel-boun...@r-project.org on behalf of tim.tri...@vai.org> wrote:
Hi all,
We had a couple of chr22 BAMs in this package that kept sneaking in, so I
nuked them with the BFG and would like to request a reset (force pull) upstream
into the BioC git server repo (g...@git.bioconductor.org:packages/spiky). This
should allow for us to proceed with committing the various bugfixes and changes
that have occurred downstream of BioC (about 46 last time I checked) and make
sure we have cleaned up everything on the spb.
I nuked everything larger than 10M (realistically I could have whacked
everything larger than 3M but 10M was sufficient to catch the BAMs).
Thanks!
Timothy J. Triche, Jr., PhD
Assistant Professor of Bioinformatics, Van Andel Institute
330 Bostwick Avenue NE, Grand Rapids, MI, 49503
(616) 234-5316 (office)
(626) 375-9663 (mobile)
(616) 234-5252 (administrative, courtesy of Lauren Dunkelberg)
https://trichelab.vai.org/
_______________________________________________
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel
_______________________________________________
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel
