threads / discuss / 31522

Failing svn imports from apache.org

Subject: Failing svn imports from apache.org

## tl;dr

4 messages between Sep 13, 2012 and Sep 17, 2012.

replies: 3people: 3as markdown or json

Enrico Weigelt· Sep 13, 2012, 13:32 UTC · lore
Hi folks,

I'm currently trying to import apache.org svn server, without success. See:

git@moonshine:~/projects/common/libs$ git svn clone --stdlayout http://svn.apache.org/repos/asf/commons/proper/discovery/
Initialized empty Git repository in /home/git/projects/common/libs/discovery/.git/
W: Ignoring error from SVN, path probably does not exist: (160013): Filesystem has no item: '/repos/asf/!svn/bc/100/commons/proper/discovery' path not found
W: Do not be alarmed at the above message git-svn is just searching aggressively for old history.
This may take a while on large repositories
mkdir .git: No such file or directory at /usr/lib/git-core/git-svn line 3669
Does anyone have an idea, what might be wrong here / how to fix it ?
thx
-- 
Mit freundlichen Grüßen / Kind regards 

Enrico Weigelt 
VNC - Virtual Network Consult GmbH 
Head Of Development 

Pariser Platz 4a, D-10117 Berlin
Tel.: +49 (30) 3464615-20
Fax: +49 (30) 3464615-59

enrico.weigelt@vnc.biz; www.vnc.de 
Michael J Gruber· Sep 14, 2012, 10:11 UTC · re: Enrico Weigelt · lore

Re: Failing svn imports from apache.org

Enrico Weigelt venit, vidit, dixit 13.09.2012 15:32:
Show 13 quoted lines
> Hi folks,
> 
> I'm currently trying to import apache.org svn server, without success.
> See:
> 
> git@moonshine:~/projects/common/libs$ git svn clone --stdlayout http://svn.apache.org/repos/asf/commons/proper/discovery/
> Initialized empty Git repository in /home/git/projects/common/libs/discovery/.git/
> W: Ignoring error from SVN, path probably does not exist: (160013): Filesystem has no item: '/repos/asf/!svn/bc/100/commons/proper/discovery' path not found
> W: Do not be alarmed at the above message git-svn is just searching aggressively for old history.
> This may take a while on large repositories
> mkdir .git: No such file or directory at /usr/lib/git-core/git-svn line 3669
> 
> Does anyone have an idea, what might be wrong here / how to fix it ?
Here: git svn --version
git-svn version 1.7.12.592.g41e7905 (svn 1.6.18)
What's yours?
I'm getting
Initialized empty Git repository in /tmp/discovery/.git/
Using higher level of URL:
http://svn.apache.org/repos/asf/commons/proper/discovery =>
http://svn.apache.org/repos/asf
W: Ignoring error from SVN, path probably does not exist: (160013):
Dateisystem hat keinen Eintrag: File not found: revision 100, path
'/commons/proper/discovery'
W: Do not be alarmed at the above message git-svn is just searching
aggressively for old history.
This may take a while on large repositories
and then it checks the revisions. I didn't want to wait for r1301705...
Does your git svn abort earlier or after checking all revs?
Enrico Weigelt· Sep 15, 2012, 10:07 UTC · re: Michael J Gruber · lore

Re: Failing svn imports from apache.org

Show 7 quoted lines
> > Does anyone have an idea, what might be wrong here / how to fix it
> > ?
> 
> Here: git svn --version
> git-svn version 1.7.12.592.g41e7905 (svn 1.6.18)
> 
> What's yours?
1.7.9.5 (ubuntu precise)
 
Show 17 quoted lines
> I'm getting
> 
> Initialized empty Git repository in /tmp/discovery/.git/
> Using higher level of URL:
> http://svn.apache.org/repos/asf/commons/proper/discovery =>
> http://svn.apache.org/repos/asf
> W: Ignoring error from SVN, path probably does not exist: (160013):
> Dateisystem hat keinen Eintrag: File not found: revision 100, path
> '/commons/proper/discovery'
> W: Do not be alarmed at the above message git-svn is just searching
> aggressively for old history.
> This may take a while on large repositories
> 
> and then it checks the revisions. I didn't want to wait for
> r1301705...
> 
> Does your git svn abort earlier or after checking all revs?
It also scanned through thousands of revisions and then failed:
W: Do not be alarmed at the above message git-svn is just searching aggressively for old history.
This may take a while on large repositories
mkdir .git: No such file or directory at /usr/lib/git-core/git-svn line 3669
cu
-- 
Mit freundlichen Grüßen / Kind regards 

Enrico Weigelt 
VNC - Virtual Network Consult GmbH 
Head Of Development 

Pariser Platz 4a, D-10117 Berlin
Tel.: +49 (30) 3464615-20
Fax: +49 (30) 3464615-59

enrico.weigelt@vnc.biz; www.vnc.de 
David Michael Barr· Sep 17, 2012, 11:05 UTC · re: Enrico Weigelt · lore

Re: Failing svn imports from apache.org

Hi Enrico,
Repositories as old and large as ASF are the reason I created svn-fe.  
git-svn is known to choke on these repositories.
If you have plenty of bandwidth, it might well be faster to:
* Grab an ASF archive (16GB)
* Use svn-fe to import the entire tree into git.
* Use a simple script to extract the standard layout into a new repo.
* Use git-svn to keep the new repo up-to-date.

-- David Michael Barr

On Saturday, 15 September 2012 at 8:07 PM, Enrico Weigelt wrote:
Show 55 quoted lines
>  
> > > Does anyone have an idea, what might be wrong here / how to fix it
> > > ?
> >  
> >  
> >  
> > Here: git svn --version
> > git-svn version 1.7.12.592.g41e7905 (svn 1.6.18)
> >  
> > What's yours?
>  
> 1.7.9.5 (ubuntu precise)
>  
> > I'm getting
> >  
> > Initialized empty Git repository in /tmp/discovery/.git/
> > Using higher level of URL:
> > http://svn.apache.org/repos/asf/commons/proper/discovery =>
> > http://svn.apache.org/repos/asf
> > W: Ignoring error from SVN, path probably does not exist: (160013):
> > Dateisystem hat keinen Eintrag: File not found: revision 100, path
> > '/commons/proper/discovery'
> > W: Do not be alarmed at the above message git-svn is just searching
> > aggressively for old history.
> > This may take a while on large repositories
> >  
> > and then it checks the revisions. I didn't want to wait for
> > r1301705...
> >  
> > Does your git svn abort earlier or after checking all revs?
>  
> It also scanned through thousands of revisions and then failed:
>  
> W: Do not be alarmed at the above message git-svn is just searching aggressively for old history.
> This may take a while on large repositories
> mkdir .git: No such file or directory at /usr/lib/git-core/git-svn line 3669
>  
>  
> cu
> --  
> Mit freundlichen Grüßen / Kind regards  
>  
> Enrico Weigelt  
> VNC - Virtual Network Consult GmbH  
> Head Of Development  
>  
> Pariser Platz 4a, D-10117 Berlin
> Tel.: +49 (30) 3464615-20
> Fax: +49 (30) 3464615-59
>  
> enrico.weigelt@vnc.biz; www.vnc.de (http://www.vnc.de)  
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org (mailto:majordomo@vger.kernel.org)
> More majordomo info at http://vger.kernel.org/majordomo-info.html

← back to recent threads