Hello, I was wondering how I can go about updating information on the Bioconductor package landing page. I would like to update the author, summary, and GitHub website address. Thanks! John
[Bioc-devel] Updating information on Bioconductor site
7 messages · John Gagnon, Robert M. Flight, Levi Waldron +1 more
John, I think that is all pulled directly from the corresponding sections in the DESCRIPTION file. So you would have to modify the DESCRIPTION, version bump, and push the changes up. After the next build, the changes should propagate to the website. Note that if you only do this on the master branch, I think the differences will only appear for development version of the package. But next release should be coming up in October some time, so that shouldn't be that big a deal. Cheers, Robert
On Fri, Sep 14, 2018, 7:44 PM John Gagnon <john.gagnon.42 at gmail.com> wrote:
Hello, I was wondering how I can go about updating information on the Bioconductor package landing page. I would like to update the author, summary, and GitHub website address. Thanks! John
_______________________________________________ Bioc-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
Thanks, Robert, I have updated the files on master GitHub, merged with upstream/master and pushed to both but I have not seen the website change on Bioconductor in two days. Am I doing something wrong? I am following these instructions: https://bioconductor.org/developers/how-to/git/sync-existing-repositories/ Thanks for your help! John
On Sep 14, 2018, at 7:59 PM, Robert M. Flight <rflight79 at gmail.com> wrote: John, I think that is all pulled directly from the corresponding sections in the DESCRIPTION file. So you would have to modify the DESCRIPTION, version bump, and push the changes up. After the next build, the changes should propagate to the website. Note that if you only do this on the master branch, I think the differences will only appear for development version of the package. But next release should be coming up in October some time, so that shouldn't be that big a deal. Cheers, Robert
On Fri, Sep 14, 2018, 7:44 PM John Gagnon <john.gagnon.42 at gmail.com> wrote: Hello, I was wondering how I can go about updating information on the Bioconductor package landing page. I would like to update the author, summary, and GitHub website address. Thanks! John
_______________________________________________ Bioc-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
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 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
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
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
If the build report shows the right version, and the page doesn't appear to be updated (make sure you are checking development page), try a hard refresh on the page to make sure browser isn't using a cached version (I think it is Ctrl+shift+F5 on chrome). Robert
On Sat, Sep 15, 2018, 1:05 PM John Gagnon <john.gagnon.42 at gmail.com> wrote:
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
_______________________________________________ Bioc-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel