Re: Trouble with git-svn when upstream svn URL changed

From: Eric Wong <normalperson@yhbt.net>
Date: Dec 8, 2006, 19:13 UTC
Message-ID: <20061208191301.GA13944@localdomain>
In-Reply-To: <m2wt52fd8p.fsf@ziti.local>

Seth Falcon <sethfalcon@gmail.com> wrote:

Show 8 quoted lines

> Eric Wong <normalperson@yhbt.net> writes:
> > This is incorrect, rebuild is not designed to handle new urls.  
> 
> ok, I was lead astray by this part of the doc for rebuild:
> 
>          A Subversion URL may be optionally specified at the
>          command-line if the directory/repository you're tracking has
>          moved or changed protocols.

Hmm.. it seems that rebuild will work as intended iff you didn't clone (and therefore still have .git/svn/git-svn/.rev_db intact). Otherwise, it will rebuild the .rev_db file and ignore your specified URL. Perhaps running rebuild twice (specifying the URL on a second clone) after a clone would work. I honestly haven't used or looked at rebuild in a while.

Show 20 quoted lines

> > However, git/git-svn are very flexible beasts :)
> >
> >> I guess I can create a fresh git repos using git-svn init and then
> >> fetch all of my dev branches from the original repository.
> >
> > You can look at "Advanced Example: Tracking a Reorganized Repository"
> > in the manpage.  Ignore the text about --follow-parent since you
> > already have the old stuff fetched, and start following the instructions
> > beginning with "# And now, we continue tracking the new revisions:"
> 
> Oh, sorry I didn't find that example.  This worked perfectly, thanks!
> 
> One question: My fingers are in the habit of typing remotes/git-svn.
> Can I do:
>    cd .git/svn
>    rm -r git-svn
>    mv git-newsvn git-svn
> 
> Or is there a safer way to rename?  Or are there other config-file
> ways to make this work -- to provide an alias?

You need to mv refs/remotes/git-newsvn refs/remotes/git-svn, too. Then it should be safe.