[Bioc-devel] How much does it takes for a package to appear at Bioconductor.org after a push?

[Martin Morgan]

How come you guys are so secretive about what package you're talking 
about? ;)

Check the 'nightly' builds to see that your package has been built.

   http://bioconductor.org/checkResults/3.7/bioc-LATEST/

Note that the nightly builds do sometimes fail, so check the date at the 
top center of the page, and the date of your package snapshot. And be 
sure that you're pushing to devel and checking devel availability, or 
similar for release.

I guess you're talking about cbaf. The Monday build report indicates 
that the last commit incorporated in the build was on 2017-11-10 
17:00:16 -0500. Is that before or after the commit you're interested in? 
cbaf built successfully on Linux (so should be available as a 'source' 
tar ball) but not Windows or Mac (Windows is problematic at the moment, 
for the reasons described in 
https://stat.ethz.ch/pipermail/bioc-devel/2017-November/012340.html )

Clicking on 'cbaf' in the build report takes one to the devel landing 
page, where cbaf version 1.1.1 is available (also via biocLite).

Similar reasoning applies to the release branch, with the report at

   http://bioconductor.org/checkResults/3.6/bioc-LATEST/

Martin

On 11/13/2017 02:57 PM, Arman Shahrisa wrote:
> 
> Hi, how much does it take for a package to appear at Bioconductoe.org
> after pushing changes. I pushed changes after fixing a few bugs
> around 32 hours ago. But I still see the previous version of my package.
> Package check also shows successful system check for the previous
> Version.
> 
> Best regards,
> Arman
> 
> 
> 	[[alternative HTML version deleted]]
> 
> _______________________________________________
> Bioc-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel
> 


This email message may contain legally privileged and/or...{{dropped:2}}