[Bioc-devel] RegEnrich problems reported in the Multiple platform build/check report for BioC 3.12

Kern, Lori Lor|@Shepherd @end|ng |rom Ro@we||P@rk@org
Thu Mar 4 14:14:40 CET 2021

Please remember there are always two branches of Bioconductor active at one time, a release and a devel branch.
Pushing to master and changing to 1.1.1 was on the devel branch and is indeed building cleanly as indicated on the build report:

The emails you receive are for the release 3.12 branch (in git.bioconductor.org RELEASE_3_12).  You need to make changes on the release branch and push forward a 1.0.1

Please see this helpful git documentation


Lori Shepherd

Bioconductor Core Team

Roswell Park Comprehensive Cancer Center

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263

From: Bioc-devel <bioc-devel-bounces using r-project.org> on behalf of Tao-2, W. (Weiyang) <W.Tao-2 using umcutrecht.nl>
Sent: Thursday, March 4, 2021 2:32 AM
To: bioc-devel using r-project.org <bioc-devel using r-project.org>
Subject: [Bioc-devel] FW: RegEnrich problems reported in the Multiple platform build/check report for BioC 3.12

Dear Bioconductor Core Team,

I was reported several days ago that my package (RegEnrich stable release version 1.0.0) had a problem in the building step.
Then I fixed the bug and bumped the version number to 1.1.1, then I pushed the changes to GitHub and git.bioconductor.org.
But today I still got the same report, which seems the report was still based on the version I did not change.

Could you please let me know how I can fix this problem? Thank you in advance!


On 03/03/2021, 19:00, "BBS-noreply using bioconductor.org" <BBS-noreply using bioconductor.org> wrote:

    [This is an automatically generated email. Please don't reply.]

    Hi RegEnrich maintainer,

    According to the Multiple platform build/check report for BioC 3.12,
    the RegEnrich package has the following problem(s):

      o ERROR for 'R CMD build' on malbec1. See the details here:

    Please take the time to address this by committing and pushing
    changes to your package at git.bioconductor.org


      * This was the status of your package at the time this email was sent to you.
        Given that the online report is updated daily (in normal conditions) you
        could see something different when you visit the URL(s) above, especially if
        you do so several days after you received this email.

      * It is possible that the problems reported in this report are false positives,
        either because another package (from CRAN or Bioconductor) breaks your
        package (if yours depends on it) or because of a Build System problem.
        If this is the case, then you can ignore this email.

      * Please check the report again 24h after you've committed your changes to the
        package and make sure that all the problems have gone.

      * If you have questions about this report or need help with the
        maintenance of your package, please use the Bioc-devel mailing list:


        (all package maintainers are requested to subscribe to this list)

    For immediate notification of package build status, please
    subscribe to your package's RSS feed. Information is at:


    Thanks for contributing to the Bioconductor project!


De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is
uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht
ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct
te informeren door het bericht te retourneren. Het Universitair Medisch
Centrum Utrecht is een publiekrechtelijke rechtspersoon in de zin van de W.H.W.
(Wet Hoger Onderwijs en Wetenschappelijk Onderzoek) en staat geregistreerd bij
de Kamer van Koophandel voor Midden-Nederland onder nr. 30244197.

Denk s.v.p aan het milieu voor u deze e-mail afdrukt.


This message may contain confidential information and is...{{dropped:30}}

More information about the Bioc-devel mailing list