[Bioc-devel] fatal: 'upstream/RELEASE_3_11' is not a commit and a branch 'RELEASE_3_11' cannot be created from it

Bhagwat, Aditya Ad|ty@@Bh@gw@t @end|ng |rom mp|-bn@mpg@de
Fri Jun 12 17:47:23 CEST 2020


Owkies, thx!

Aditya

From: Shepherd, Lori <Lori.Shepherd using RoswellPark.org>
Sent: Freitag, 12. Juni 2020 17:42
To: Bhagwat, Aditya <Aditya.Bhagwat using mpi-bn.mpg.de>; bioc-devel using r-project.org
Subject: Re: [Bioc-devel] fatal: 'upstream/RELEASE_3_11' is not a commit and a branch 'RELEASE_3_11' cannot be created from it

If you git clone the git.bioconductor.org repository for your package in a different folder location you would be able to see the copy and commits we have on our server (I understand not very convenient)

There is a delay from commits to updates on the building reports and landing page.  It is discussed at the top of the page and has been answered numerous times on the mailing list

http://bioconductor.org/developers/how-to/troubleshoot-build-report/

We are in the process of potentially expanding the submission process tracker building on commit to the daily builder.  There is still no time period on when that would be available as it has just started being explored.

Cheers,


Lori Shepherd

Bioconductor Core Team

Roswell Park Comprehensive Cancer Center

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263

________________________________
From: Bhagwat, Aditya <Aditya.Bhagwat using mpi-bn.mpg.de<mailto:Aditya.Bhagwat using mpi-bn.mpg.de>>
Sent: Friday, June 12, 2020 11:33 AM
To: Shepherd, Lori <Lori.Shepherd using RoswellPark.org<mailto:Lori.Shepherd using RoswellPark.org>>; bioc-devel using r-project.org<mailto:bioc-devel using r-project.org> <bioc-devel using r-project.org<mailto:bioc-devel using r-project.org>>
Subject: RE: [Bioc-devel] fatal: 'upstream/RELEASE_3_11' is not a commit and a branch 'RELEASE_3_11' cannot be created from it


Thankyou Lori,



Is there a way to get a visual overview of recent commits at https://git.bioconductor.org/packages/multicrispr<https://secure-web.cisco.com/1DzTC21Xsa01UK-VZkKk4yvwj_VU6qp85rqzcKCvvPMtm2vah4-NZjCAOKXcKftajD-J_w4XNYR6kLkwlc3GHf2OiIPJgqZyL75sZ8VqF0VU14xhmRORFhrGnYF9LaVvgeCdpIHt6nYIpOP1Iqtm4SxSlQZxBPes6PuXMj0O8IKEzoYniEDKV8i0Om9zJq0V6MZ5t82_OwcYqQlomckoYFnPfegBOQTE0zImOFpX4OVb7EbkBxnsULFIX__s_wylxcSctW2sWmwOs1YzSytASDL87V2RYWBOBRZ6vrGyj7WCe3ucom8SmlnU_D9whWOO34I4eG4ErtNZIravWIuPUXw/https%3A%2F%2Fgit.bioconductor.org%2Fpackages%2Fmulticrispr>? (as in e.g. github)

Asking because I cannot see recent commits (pushed to upstream successfully yesterday) reflected in build reports<https://secure-web.cisco.com/1jJOzEyoW2u-3tHDFcgIXdMcB7kOXmu9Nm8ZW3YJPv38b7AL5FKIwuPDG-mk-VK2RdohHNb094i-Jw69AJKUHMEPRCwSDJc3epGdu1oXfs3y1pB4y9EIq5qq64scEvOXk4qo434vvfrRlgLpROeZnAVed-P0lE-Wg3VADtxGOEomvwrpyClTfASKZR3hzSGuZI7oP522KScMh4MwjaWXtAvFU6AX54GaGDPWsBy2-LvKJhkK5MXA88qDQPAps3DTlT9OOx3QBU3Vn-K3rD4-PosS7lXJ7JkrlXfSzmnMzctmZx8fpRukHIFeC7zo7VIE1D3-7SqwQriVj90ow34NVGW2G_s4ro-fKJSxtqlNzak8/https%3A%2F%2Fbioconductor.org%2FcheckResults%2F3.12%2Fbioc-LATEST%2F> or landing page<https://secure-web.cisco.com/1A2W_b5ZAOGQ8Ht9ZFzC1E_hGsPYkaraU-OYX5DQLKHG1CDSVVsO3z1RrEZifTEa7Be45ASdmCX4DLcPoH3dlRN9kF-SCtD1Cqzd1h74rL-bm97PldOPsCjm_QrIhfwXtWbjmgjCOqdc4z_LYwHKcUQXizoM8Twn_0y0mvBIg_kXlp9AzxF31kdHa33NPA-VVAAk1VuF1yJWS2bFMg_LU51SXt24BoFVNmtsGKIyWbU5C2UB1yLcTq5EvalNJzI7eBgOwPDLObUy0W8SYa5A24zf3N6GDwchPgOXL5EOhsK-_W4VZnHnQFeNr82ysGdn38SUlyqrf_UwczMyBW5nC6ARU77Kgfl72pViMawG0aok/https%3A%2F%2Fbioconductor.org%2Fpackages%2Fdevel%2Fbioc%2Fhtml%2Fmulticrispr.html>.

A related question: the CI/CD feature during package submission (master branch push to github triggers build attempt on the BioC servers) was actually very useful, but I can understand that you don't provide this for accepted packages to keep the load on your servers manageable.

What CI/CD setup would you recommend (from the perspective of being maximally relevant for BioC).



Travis?



Thank you for helping!



Aditya



________________________________

From: Shepherd, Lori [Lori.Shepherd using RoswellPark.org]
Sent: Thursday, June 11, 2020 6:18 PM
To: Bhagwat, Aditya; bioc-devel using r-project.org<mailto:bioc-devel using r-project.org>
Subject: Re: [Bioc-devel] fatal: 'upstream/RELEASE_3_11' is not a commit and a branch 'RELEASE_3_11' cannot be created from it

Newly accepted packages are added into devel only.  They will be a release branch as soon as the next scheduled Bioconductor release occurs.



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<mailto:bioc-devel-bounces using r-project.org>> on behalf of Bhagwat, Aditya <Aditya.Bhagwat using mpi-bn.mpg.de<mailto:Aditya.Bhagwat using mpi-bn.mpg.de>>
Sent: Thursday, June 11, 2020 12:15 PM
To: bioc-devel using r-project.org<mailto:bioc-devel using r-project.org> <bioc-devel using r-project.org<mailto:bioc-devel using r-project.org>>
Subject: [Bioc-devel] fatal: 'upstream/RELEASE_3_11' is not a commit and a branch 'RELEASE_3_11' cannot be created from it



Dear Bioc Core,

Thank you for accepting multicrispr on BioC<https://secure-web.cisco.com/1Y5aHfpLYwxVOA6Cj3bxEVuenqe6D8K2mYcqfAmwz6Fi6eyzj9ZL85VY2H0PZrFkpkFbO_w5JIWkUIDUjYSFPRsOWFmm_pDVgAJBRmO1uCb9LgJF5mh_FUnj2zUAPVJbk9HPy9BzwWn8pHCQOyHp9T_xfBrl1tFAkt7ZrYGptTyl0u1HYKnjYTmc-l5OjWQoyG3bIOTfYV1lc_cNItl7XwfDdyx4NkyoksEKEZfvA_2PlrkF8te0_49BJxVw47JVUK1Tjj-F-nuVxx2gAF3nDoPiQl1f5bOcc1zKgTYrgh1x2so6QfUHbqu_M7rEFHBQ9OFgeC30W0bOLRd4YEfu5XA/https%3A%2F%2Fgithub.com%2FBioconductor%2FContributions%2Fissues%2F1486>.
I was going through the instructions on how to sync existing repositories<https://secure-web.cisco.com/1Xe9o5uhiFHsFKbmSBGQuqpBQbV-hql0tIGwW7TBNOQyRT67-xND5I-TSMoVXC2pXrgYxNb-5-sPbt5rOOjgawuDHJv7Y7yJFhVBV51tIj9xSy4Nk-GlEPEtV_1RG79MZbJ5d7LZ82dFp-BZmzPwrjKRAib7x8vphKaRW4qc_q6EIPMOrs282w4JaJxxRd-Jsxi6X_gw41rihMwaTa84WG62bi5im6SkX3hoyYq6qwitZdOiUeNN9FYJHB_VREnXcM16haB2xWae5BwiJJdtuP3Y1T-wW9L0HnO14_bhkOd794PH_lDa0cdICiv2NVJVoaSyYZK93SX5T2wpON1FgO_xhi1D5Z45H163FH75DerE/https%3A%2F%2Fbioconductor.org%2Fdevelopers%2Fhow-to%2Fgit%2Fsync-existing-repositories%2F>.
All instructions up to point 9 work.

Point 10, however fails, when creating the release branch:
$ git checkout -b RELEASE_3_11 upstream/RELEASE_3_11
fatal: 'upstream/RELEASE_3_11' is not a commit and a branch 'RELEASE_3_11' cannot be created  from it

I wonder what I am doing wrong (seems like it should be something trivial, but I am not seeing it).

Thank you for helping!

Aditya

        [[alternative HTML version deleted]]

_______________________________________________
Bioc-devel using r-project.org<mailto:Bioc-devel using r-project.org> mailing list
https://secure-web.cisco.com/1dD24Fmu9gjmLPt6fORbREp3nCtIbsBT2Cqq9kX7NWPdnENsspbw0obk03UOZoUcHCDqDJWOZ5LqGeBEON5GsAOUcxgLaOIPiHdXbUkUYRI0JJpGgw9gxTbtdNb5tOM-Tcn6oSrOEmurcRssmw-W7BYV3C5hGKbLQi-Ykb7JeZLS-9VgZSsSCiVcRcC12WqKjR0OmBY6UK1bpRAs--1MCuX1a-WnFzbBEIcdBgOf2IDH6hYDxiFUmniKrXYc52F2MYBhX1qSx1zfJDqxP1bPI1d_4A9MTbwsAuGI9764_XDo3xrBlhnd75yY6a0PaYCvwifkIOcQ2KhxLc0TWUamlFg/https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fbioc-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.

	[[alternative HTML version deleted]]



More information about the Bioc-devel mailing list