[Bioc-devel] Daily build

[Obenchain, Valerie]

That sounds like a bug. Thanks for the report, we'll look into it.

Valerie


On 03/09/2018 07:48 AM, Nicolas Descostes wrote:
I mean that on the landing page: https://bioconductor.org/packages/3.7/bioc/html/ChIPSeqSpike.html

If you click on NEWS (https://bioconductor.org/packages/3.7/bioc/news/ChIPSeqSpike/NEWS), the file is not up to date. However, if you download ChIPSeqSpike_0.99.21.tar.gz and open the file NEWS, it is indeed the last one. So the modification is not reported on the landing page.

2018-03-09 10:40 GMT-05:00 Obenchain, Valerie <Valerie.Obenchain at roswellpark.org<mailto:Valerie.Obenchain at roswellpark.org>>:
What do you mean by 'the NEWS file has not been properly updated'? Did you commit a change before the builds started, bumped the package version and the package you downloaded with biocLite() was somehow out of date? Or was a download from the landing page out of date ... ?

Valerie




On 03/09/2018 07:25 AM, Nicolas Descostes wrote:
Dear Valerie,

My package has been correctly updated except for the file NEWS. https://bioconductor.org/packages/3.7/bioc/news/ChIPSeqSpike/NEWS

Is it an issue that I should report on the bioc-devel. Have you been aware of this problem with other users?

Thanks.

Nicolas

2018-03-07 17:02 GMT-05:00 Obenchain, Valerie <Valerie.Obenchain at roswellpark.org<mailto:Valerie.Obenchain at roswellpark.org>>:
Do a pull and check the log. Your commit should appear in the log.

The builds run once a day and start at 5pm EST. The report posts the following day (see time at top of report). If your commit was before 5pm it will be included in the build tonight. Otherwise the changes will be picked up tomorrow (posted Friday).

Valerie




On 03/07/2018 01:56 PM, Nicolas Descostes wrote:
Hi Valerie,

I corrected a few things and followed the instructions from the beginning (using the eclipse interface). I pushed successfully. I would like to know if the commit date should appear right away at https://bioconductor.org/checkResults/devel/bioc-LATEST/#C or if there can be a delay?

I double checked with the command:

descostes at reinbergLab:~/git/bioconductor/ChIPSeqSpike$ git push
Everything up-to-date

Thank you,

Nicolas

2018-03-07 12:47 GMT-05:00 Obenchain, Valerie <Valerie.Obenchain at roswellpark.org<mailto:Valerie.Obenchain at roswellpark.org>>:
Hi Nicolas,

This is the last commit I see in the master branch for ChIPSeqSpike:

commit abce855631cb5689bd345df41e71cfee356a1c6f (HEAD -> master, origin/master, origin/HEAD)
Author: kitano902 <nicolas.descostes at nyumc.org><mailto:nicolas.descostes at nyumc.org>
Date:   Fri Jan 26 14:29:26 2018 -0500

    remove '{' in count.Rd

The most recent commits are not making it to git at git.bioconductor.org<mailto:git at git.bioconductor.org>. At one point you had the workflow down and were able to make commits. You may want to revisit the documentation for troubleshooting tips:

https://www.bioconductor.org/developers/how-to/git/

Valerie




On 03/07/2018 05:12 AM, Nicolas Descostes wrote:

Dear community,

When my package ChIPSeqSpike was accepted, I have been noticed that no
further action was required regarding my github (
https://github.com/descostesn/ChIPSeqSpike).

I did two commits with version bump yesterday and I did not receive any
notification. I checked the version at
https://bioconductor.org/checkResults/devel/bioc-LATEST/#C
 and the commits
of yesterday do not appear. I am using egit with eclipse oxygen. I went
through the bioc doc but I think that I followed everything.

Did I miss something?

Thanks.

Nicolas

        [[alternative HTML version deleted]]

_______________________________________________
Bioc-devel at r-project.org<mailto:Bioc-devel at r-project.org> mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel




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.
	[[alternative HTML version deleted]]