[Bioc-devel] A question about r package update

Kern, Lori Lor|@Shepherd @end|ng |rom Ro@we||P@rk@org
Fri Oct 16 15:54:43 CEST 2020

We apologize.  It was announced on the Bioconductor slack but we forgot to post on the bioc-devel mailing list. There was an issue with the builders and there was no report generated yesterday Thursday October 15.  The issue should be resolved and we expect a build report today.
I do see 1.5.2 in our git repository so it should be reflected in the report today.
We apologize for the confusion and the inconvenience


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 Xiaowen Chen <Xiaowen.Chen using jax.org>
Sent: Friday, October 16, 2020 9:49 AM
To: bioc-devel using r-project.org <bioc-devel using r-project.org>
Subject: [Bioc-devel] A question about r package update

Hi bioc-devel,
I am sorry for email you so often, this morning I checked the check report website, it did not change.
And I noticed that the data is �This page was generated on 2020-10-14 11:07:41 -0400 (Wed, 14 Oct 2020).�

Indeed I pushed my package on 2020-10-14. But its version is 1.5.2, not 1.5.1 shown in the website.
Even it is not the one I pushed, now it have been two days.

So this morning I push epihet again. The command is as following
(base) [chenx using helix epihet]$ git remote add upstream git using git.bioconductor.org:packages/epihet.git
(base) [chenx using helix epihet]$ git fetch --all
Fetching origin
Fetching upstream
Enter passphrase for key '/home/c-chenx/.ssh/id_rsa':
From git.bioconductor.org:packages/epihet
* [new branch]      RELEASE_3_10 -> upstream/RELEASE_3_10
* [new branch]      RELEASE_3_11 -> upstream/RELEASE_3_11
* [new branch]      RELEASE_3_9 -> upstream/RELEASE_3_9
* [new branch]      master     -> upstream/master
(base) [chenx using helix epihet]$ git checkout master
Already on 'master'
(base) [chenx using helix epihet]$ git merge origin/master
Already up-to-date.
(base) [chenx using helix epihet]$ git merge upstream/master
Already up-to-date.
(base) [chenx using helix epihet]$ git push upstream master
Enter passphrase for key '/home/c-chenx/.ssh/id_rsa':
Everything up-to-date
(base) [chenx using helix epihet]$ git push origin master
Everything up-to-date

Previously, when I typed �git merge upstream/master�, it returned something like this
Merge made by recursive.
NEWS        |    7 +++++--
2 files changed, 6 insertions(+), 3 deletions(-)
mode change 100755 => 100644 DESCRIPTION

So I am curious whether epihet1.5.2 successfully push to upstream?
Could you help me to check? Since tomorrow is weekend.
Thank you pretty much.

The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible.

        [[alternative HTML version deleted]]

Bioc-devel using r-project.org mailing list

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]]

More information about the Bioc-devel mailing list