[Bioc-devel] Catching SVN up to Github

[Shepherd, Lori]

It seems like you renamed your package after it was submitted based on the current version in svn and the current ERROR occurring on the build report.


Could you check your git config -l   and see if the svn-remote* in the config file are updated to reflect the naming change?



Lori Shepherd

Bioconductor Core Team

Roswell Park Cancer Institute

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263

________________________________
From: Bioc-devel <bioc-devel-bounces at r-project.org> on behalf of Matt Richards <Matt.Richards at systemsbiology.org>
Sent: Thursday, July 27, 2017 4:36:47 PM
To: bioc-devel at r-project.org
Subject: [Bioc-devel] Catching SVN up to Github

Hi all,

Since our package, "trena", was accepted, we've made some pretty extensive
changes to the package on Github. Our version has so far jumped from
0.99.10 to 0.99.135. These changes are all contained on a forked version of
the Bioconductor mirror, as specified (https://www.bioconductor.org/
developers/how-to/git-mirrors/). We haven't yet put these changes onto SVN.

My question is regarding how to get the Github repo and the SVN on the same
page. I've followed the procedure outlined on the linked page and also
tried the cherry picking procedure, but any `git svn` command
(info/rebase/dcommit) run on the devel branch returns me the same message:

Unable to determine upstream SVN information from HEAD history.

I've also tried a `git svn log`, which returns: fatal: your current branch
appears to be broken

Any ideas what's going on here? I'm a self-admitted novice when it comes to
SVN.

Thanks
Matt

--
Matthew Richards
Postdoctoral Fellow
Institute for Systems Biology

        [[alternative HTML version deleted]]

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