threads / discuss / 18588

problems syncing with svn

Subject: problems syncing with svn

## tl;dr

2 messages between Mar 27, 2009 and Mar 27, 2009.

replies: 1people: 1as markdown or json

Jeff Brown· Mar 27, 2009, 13:17 UTC · lore

I have found numerous folks having a similar problem but have not found a solution that works for me. This is what I have:

I have svn clone'd a repo. I have added a git remote to the project. I have pulled from the git repo. When I attempt to "svn dcommit", the commit fails with...

Unable to extract revision information from commit 26c8e90f67d40d9193fe276f3bcbfdd4e9161730~1

What I really want to do is move our primary development support to git (github in particular right now). I want to setup a job that will periodically grab the latest code from github and push those changes to our svn repo. These will be the only commits made to svn. Developers will no longer be committing to svn. We need the svn repo kept up to date for a few reasons but do not want to do development against svn directly.

Any advice would be much appreciated.
Thanks in advance.
jeff
-- 
Jeff Brown
SpringSource
http://www.springsource.com/

Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
http://www.autismspeaks.org/
Jeff Brown· Mar 27, 2009, 13:58 UTC · re: Jeff Brown · lore

Re: problems syncing with svn

On Fri, Mar 27, 2009 at 9:17 AM, Jeff Brown <jeff@jeffandbetsy.net> wrote:
Show 22 quoted lines
> I have found numerous folks having a similar problem but have not
> found a solution that works for me.  This is what I have:
>
> I have svn clone'd a repo.  I have added a git remote to the project.
> I have pulled from the git repo.  When I attempt to "svn dcommit", the
> commit fails with...
>
> Unable to extract revision information from commit
> 26c8e90f67d40d9193fe276f3bcbfdd4e9161730~1
>
> What I really want to do is move our primary development support to
> git (github in particular right now).  I want to setup a job that will
> periodically grab the latest code from github and push those changes
> to our svn repo.  These will be the only commits made to svn.
> Developers will no longer be committing to svn.  We need the svn repo
> kept up to date for a few reasons but do not want to do development
> against svn directly.
>
> Any advice would be much appreciated.
>
> Thanks in advance.
>

If repo details will help, the git repo is at http://github.com/grails/grails/tree/master and the original svn repo which that came from is at https://svn.codehaus.org/grails/trunk/.

Thanks again.
Jeff
-- 
Jeff Brown
SpringSource
http://www.springsource.com/

Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
http://www.autismspeaks.org/

← back to recent threads