* git svn clone just stops
@ 2009-12-15 22:19 Mark Jerkovic
2009-12-16 8:15 ` Eric Wong
0 siblings, 1 reply; 6+ messages in thread
From: Mark Jerkovic @ 2009-12-15 22:19 UTC (permalink / raw)
To: git
Hi all,
I am new to Git and I am attempting to clone a SVN repository
(containing approximately 60,000 commits) to Git.
Using Git v1.6.0.4 with the following command:
git svn clone https://path/to/svn/repo/trunk project.git
--authors-file=svnauthors.txt --no-metadata
the process just ends without any messages and the Git repository is
empty. I have attempted this four times already, and each time it has
stopped after a different revision, so I can't pin it down to a
particular commit.
Has anyone experienced this before? Is there a log anywhere that
records what is happening during this process?
Thanks,
Mark.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git svn clone just stops
2009-12-15 22:19 git svn clone just stops Mark Jerkovic
@ 2009-12-16 8:15 ` Eric Wong
2009-12-16 20:47 ` Mark Jerkovic
2009-12-18 15:00 ` Pascal Obry
0 siblings, 2 replies; 6+ messages in thread
From: Eric Wong @ 2009-12-16 8:15 UTC (permalink / raw)
To: Mark Jerkovic; +Cc: git
Mark Jerkovic <mjerkovic@aconex.com> wrote:
> Hi all,
>
> I am new to Git and I am attempting to clone a SVN repository
> (containing approximately 60,000 commits) to Git.
>
> Using Git v1.6.0.4 with the following command:
>
> git svn clone https://path/to/svn/repo/trunk project.git
> --authors-file=svnauthors.txt --no-metadata
>
> the process just ends without any messages and the Git repository is
> empty. I have attempted this four times already, and each time it has
> stopped after a different revision, so I can't pin it down to a
> particular commit.
Hi Mark,
Any chance you're OOM-ing (extremely large file) or running
out of space somewhere? What exit code do you get when it exits?
> Has anyone experienced this before? Is there a log anywhere that
> records what is happening during this process?
Not without error messages of some sort. git svn was designed with poor
network conditions in mind and clone is resumable, so you can just
resume like this:
cd project.git && git svn fetch
I wouldn't use --no-metadata at this point, though, as it makes it much
harder to debug/fix things or recover from errors.
Once you're comfortable with it, you should be able to write
"git filter-branch" invocation to remove the metadata lines.
--
Eric Wong
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git svn clone just stops
2009-12-16 8:15 ` Eric Wong
@ 2009-12-16 20:47 ` Mark Jerkovic
2009-12-18 15:00 ` Pascal Obry
1 sibling, 0 replies; 6+ messages in thread
From: Mark Jerkovic @ 2009-12-16 20:47 UTC (permalink / raw)
To: Eric Wong; +Cc: git
On Wed, 2009-12-16 at 00:15 -0800, Eric Wong wrote:
> Mark Jerkovic <mjerkovic@aconex.com> wrote:
> > Hi all,
> >
> > I am new to Git and I am attempting to clone a SVN repository
> > (containing approximately 60,000 commits) to Git.
> >
> > Using Git v1.6.0.4 with the following command:
> >
> > git svn clone https://path/to/svn/repo/trunk project.git
> > --authors-file=svnauthors.txt --no-metadata
> >
> > the process just ends without any messages and the Git repository is
> > empty. I have attempted this four times already, and each time it has
> > stopped after a different revision, so I can't pin it down to a
> > particular commit.
>
> Hi Mark,
>
> Any chance you're OOM-ing (extremely large file) or running
> out of space somewhere? What exit code do you get when it exits?
>
> > Has anyone experienced this before? Is there a log anywhere that
> > records what is happening during this process?
>
> Not without error messages of some sort. git svn was designed with poor
> network conditions in mind and clone is resumable, so you can just
> resume like this:
>
> cd project.git && git svn fetch
>
That is an excellent tip. Thanks a lot!
> I wouldn't use --no-metadata at this point, though, as it makes it much
> harder to debug/fix things or recover from errors.
>
> Once you're comfortable with it, you should be able to write
> "git filter-branch" invocation to remove the metadata lines.
I have done some more investigating and it appears that at some point a
branch was moved to replace our trunk. When the migration process hits
this I it goes back to the beginning and starts migrating the branch
history too. I think when it gets to the end of it is not able to
resume from the "move" point.
I will try your resume tip to see if I can get it started again.
Many thanks,
Mark.
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git svn clone just stops
2009-12-16 8:15 ` Eric Wong
2009-12-16 20:47 ` Mark Jerkovic
@ 2009-12-18 15:00 ` Pascal Obry
2009-12-20 8:57 ` Eric Wong
1 sibling, 1 reply; 6+ messages in thread
From: Pascal Obry @ 2009-12-18 15:00 UTC (permalink / raw)
To: Eric Wong; +Cc: Mark Jerkovic, git
Eric,
> Not without error messages of some sort. git svn was designed with poor
> network conditions in mind and clone is resumable, so you can just
> resume like this:
>
> cd project.git && git svn fetch
What about --revision option. I mean if I have this clone interrupted:
$ git svn clone --revision=345:HEAD svn+ssh://...
Should I specify --revision when restarting with fetch? I think I had an
issue with this...
Maybe some other options are also to be passed to fetch?
Thanks.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net - http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git svn clone just stops
2009-12-18 15:00 ` Pascal Obry
@ 2009-12-20 8:57 ` Eric Wong
2009-12-20 9:44 ` Pascal Obry
0 siblings, 1 reply; 6+ messages in thread
From: Eric Wong @ 2009-12-20 8:57 UTC (permalink / raw)
To: Pascal Obry; +Cc: Mark Jerkovic, git
Pascal Obry <pascal@obry.net> wrote:
> Eric,
>
> > Not without error messages of some sort. git svn was designed with poor
> > network conditions in mind and clone is resumable, so you can just
> > resume like this:
> >
> > cd project.git && git svn fetch
>
> What about --revision option. I mean if I have this clone interrupted:
>
> $ git svn clone --revision=345:HEAD svn+ssh://...
>
> Should I specify --revision when restarting with fetch? I think I had an
> issue with this...
>
> Maybe some other options are also to be passed to fetch?
Hi Pascal,
--revision may be passed to fetch, but its optional. fetch should
always know where to pickup after it left off.
"git svn $command -h" shows you all options a particular $command
allows.
--
Eric Wong
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git svn clone just stops
2009-12-20 8:57 ` Eric Wong
@ 2009-12-20 9:44 ` Pascal Obry
0 siblings, 0 replies; 6+ messages in thread
From: Pascal Obry @ 2009-12-20 9:44 UTC (permalink / raw)
To: Eric Wong; +Cc: Mark Jerkovic, git
Hi Eric,
> --revision may be passed to fetch, but its optional. fetch should
> always know where to pickup after it left off.
Ok, thanks for the info.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net - http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-12-20 9:44 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-15 22:19 git svn clone just stops Mark Jerkovic
2009-12-16 8:15 ` Eric Wong
2009-12-16 20:47 ` Mark Jerkovic
2009-12-18 15:00 ` Pascal Obry
2009-12-20 8:57 ` Eric Wong
2009-12-20 9:44 ` Pascal Obry
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).