Message-ID: <F966B62B-120E-428B-84FF-235B7BBCAAB3@gmail.com>
Date: 2018-09-15T17:01:03Z
From: John Gagnon
Subject: [Bioc-devel] Updating information on Bioconductor site
In-Reply-To: <439a671b-fd00-1398-2de5-5fc6295f1942@gmail.com>
Thanks, I used the link you provided to the build report and it seems that the information did push through.
Best,
John
> On Sep 15, 2018, at 9:38 AM, Martin Morgan <mtmorgan.bioc at gmail.com> wrote:
>
>
>
> On 09/15/2018 12:34 PM, Levi Waldron wrote:
>> John, is your new version number reflected on the devel version of the
>> package landing page and the build report? After you push a new version
>> number to master, it will propagate the next day after overnight
>> building/testing.
>> AFAIK, there are only a few explanations for why git pushes do not show up
>> on the package landing page (have I missed any?):
>> 1. You didn't actually push to the relevant branch at git.bioconductor.org
>> (e.g. you pushed to GitHub only, or pushed to master but checked the
>> release landing page)
>> 2. You didn't bump the version number
>> 3. There was an error in the package build
>
> maybe useful to remember that the build report is at
>
> http://bioconductor.org/checkResults/devel/bioc-LATEST/plotGrouper/
>
> (replace 'devel' with 'release' for the release branch).
>
> Martin
>
>
>> 4. You haven't waited until the next day for software packages, or for the
>> twice a week builds of experimental data packages
>> 5. Occasionally, there is a problem with the build systems that affects
>> many packages
>> [[alternative HTML version deleted]]
>> _______________________________________________
>> Bioc-devel at r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/bioc-devel