On Wed, Dec 06, 2006 at 04:46:00PM -0600, Aaron Spike wrote:

MenTaLguY wrote:

...

I'm interested in setting up a git mirror of Inkscape SVN; who's the person in charge of our server currently? We'll need to have a fairly current version of git, libsvn, and the libsvn perl bindings installed to do this.

I think there are a few people, but I would be happy to assist you.

Me too. I've kicked off an install of git 1.4.1 and upgrade of subversion to 1.3.2, including perl and ruby use flags. Hope that helps; let me know if something newer is required.

Bryce

On Wed, 2006-12-06 at 15:33 -0800, Bryce Harrington wrote:

Me too. I've kicked off an install of git 1.4.1 and upgrade of subversion to 1.3.2, including perl and ruby use flags. Hope that helps; let me know if something newer is required.

Hmm, did you mean 1.4.1 or 1.4.4.1?

I think we need 1.4.4 at least to get git-svn.

-mental

Was an inkscape git mirror ever established? I'd like to change my checkout from svn to git.

FWIW, Cloning with: git svn clone -s https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape inkscape

halted for me somewhere around r10060 (2006). I couldn't get any error output to see why subsequent clone or fetch operations wouldn't retrieve later revisions.

Thanks.

On Wed, 11 Jun 2008 19:39:15 -0700, Ted Gould wrote:

I had real problems making a proper Bzr mirror. I happened to be at a conference with a bunch of Bzr people so they looked into it, it seems that there is a real delay with getting properties on the SF SVN servers. That was the bottleneck, I'm assuming it's the same for git.

BTW, my bzr trunk is here for those who are interested:

https://code.launchpad.net/~ted-gould/inkscape/trunk

I presume SF makes a backup of the svn repository available to admins. git (and/or bzr) svn clone might run much better from a file:// URL. After that, the remote URL could be set back to SF https://.

Thanks, Jeff

On Thu, 12 Jun 2008 01:38:43 -0400, MenTaLguY wrote:

On Thu, 2008-06-12 at 00:36 -0400, Jeff Kowalczyk wrote:

...

...

BTW, my bzr trunk is here for those who are interested:

https://code.launchpad.net/~ted-gould/inkscape/trunk

I presume SF makes a backup of the svn repository available to admins. git (and/or bzr) svn clone might run much better from a file:// URL. After that, the remote URL could be set back to SF https://.

I've done that, it certainly does work better. The main issue is that the URL gets baked into the imported history, so it is unsuitable for use with git-svn to commit back to SVN. (Though it is possible, with some custom software, to rewrite the imported history to get around that.)

It sounds like rewriteRoot would help:

http://www.kernel.org/pub/software/scm/git/docs/git-svn.html

svn-remote.<name>.rewriteRoot

This allows users to create repositories from alternate URLs. For example, an administrator could run git-svn on the server locally (accessing via file://) but wish to distribute the repository with a public http:// or svn:// URL in the metadata so users of it will see the public URL.

Since the noMetadata, rewriteRoot, useSvnsyncProps and useSvmProps options all affect the metadata generated and used by git-svn; they must be set in the configuration file before any history is imported and these settings should never be changed once they are set.

Additionally, only one of these four options can be used per-svn-remote section because they affect the git-svn-id: metadata line.