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

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'

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 confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.

I apologize. It was better to mention the package name. Thank you very

Much for your assistance.



The devel branch of cbaf has the version of 1.1.1 . The error happened for

Windows and Linux check is caused by the genefilter package. The error for

genefilter package Itself is caused by two unavailable CRAN packages.

So, there is nothing I can do about it.



At the stable 3.6 branch, cbaf 1.0.1 had a few minor issues

(not problematic though), so I decided to fix. I had pushed 1.0.1

exactly 24 hours before pushing 1.0.2, and I pushed 1.0.2 about 32

hours ago. The citation part of the previous presion (cbaf 1.0.1)

was changed to 1.0.2 about thirty minutes ago, so I guess server

is checking the new version right now.





Best regards,

Arman



________________________________
From: Martin Morgan <martin.morgan at roswellpark.org>
Sent: Monday, November 13, 2017 11:38:02 PM
To: Arman Shahrisa; bioc-devel
Subject: Re: [Bioc-devel] How much does it takes for a package to appear at Bioconductor.org after a push?

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'

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 confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.

        [[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 confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.