7:39 a.m.
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.
-mental
7:46 a.m.
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.
Aaron Spike
8:33 a.m.
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
8:52 a.m.
On Wed, Dec 06, 2006 at 03:33:59PM -0800, Bryce Harrington wrote:
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.
Installed. Let Aaron or I know if there are any issues.
Bryce
1:01 p.m.
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
1:32 p.m.
On Wed, Dec 06, 2006 at 11:01:12PM -0500, MenTaLguY wrote:
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
Yes, I meant 1.4.1. I'll upgrade to 1.4.4.1 next.
Bryce
9:21 a.m.
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.
11:39 a.m.
On Tue, 2008-06-10 at 20:21 -0400, Jeff Kowalczyk wrote:
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.
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
--Ted
1:36 p.m.
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
2:38 p.m.
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.)
-mental
2:56 p.m.
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.
8:51 p.m.
>>>> "Jeff" == Jeff Kowalczyk
<jtk@...36...> writes:
Jeff> I presume SF makes a backup of the svn repository available to
Jeff> admins.
for inkscape it is at:
rsync://inkscape.svn.sourceforge.net/svn/inkscape/
In general, for SF projects which use CVS or SVN the forms are:
rsync://${project}.cvs.sourceforge.net/cvsroot/${project}/
rsync://${project}.svn.sourceforge.net/svn/${project}/
-JimC
--
James Cloos <cloos@...1016...> OpenPGP: 1024D/ED7DAEA6
5459
days inactive
6019
days old
inkscape-devel@lists.inkscape.org
11 comments
6 participants
participants (6)
-
Aaron Spike -
Bryce Harrington -
James Cloos -
Jeff Kowalczyk -
MenTaLguY -
Ted Gould