On Oct 30, 2017, at 6:57 AM, sergi.picart at upc.edu wrote:
Dear Nitesh,
We were able to fix the error on MAIT under the bioc-devel official docker.
We pushed upstream two days ago to meet the deadline, but the system has not seen the changes and no build has been issued since then.
What should we do?
Thank you for your help,
Quoting sergi.picart at upc.edu:
Dear Nitesh,
The build has not been triggered yet, is everything correct?
Thank you,
Quoting "Turaga, Nitesh" <Nitesh.Turaga at roswellpark.org>:
The builds are ?nightly builds? i.e they trigger in the evening time EST. Please wait till tomorrow to see your build report.
On Oct 26, 2017, at 11:16 AM, sergi.picart at upc.edu wrote:
We have bumped the version and removed the ^M characters.
This did not trigger the build by the time I am writing now, though.
Thank you,
Quoting "Turaga, Nitesh" <Nitesh.Turaga at roswellpark.org>:
Please issue another version bump.
It might also help if you removed the ^M characters after the version bump.
On Oct 26, 2017, at 10:37 AM, sergi.picart at upc.edu wrote:
Yes, as far as I know.
Running:
git clone git at git.bioconductor.org:packages/MAIT
and showing the DESCRIPTION file yields to
Version: 1.11.3
Is this right? Thank you,
Quoting "Turaga, Nitesh" <Nitesh.Turaga at roswellpark.org>:
Did you push to upstream i.e git at git.bioconductor.org?
And did you bump the version?
On Oct 26, 2017, at 9:06 AM, sergi.picart at upc.edu wrote:
Dear Nitesh,
We have pushed one changeset to git at git.bioconductor.org:packages/MAIT, but I cannot see an updated build report on http://bioconductor.org/checkResults/devel/bioc-LATEST/MAIT/
Are we doing something wrong or is it a matter of time that it builds automatically?
Thank you,
Quoting "Turaga, Nitesh" <Nitesh.Turaga at roswellpark.org>:
On Sep 29, 2017, at 10:39 AM, sergi.picart at upc.edu wrote:
Dear Bioconductor team,
Our lab is in charge of maintaining the MAIT package.
MAIT is about to get deprecated due to an error in its vignette.
We have a fix for it, and would also add a new author/maintainer to patch it.
Which steps do we need to follow?
Thank you for your help,
Sergio
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.
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.
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.
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.