Git development
 help / color / mirror / Atom feed
From: Daniele Segato <daniele.bilug@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Eric Wong <normalperson@yhbt.net>
Subject: Filesystem has no item: Working copy path [...] does not exist in  repository at /usr/bin/git-svn line 3856
Date: Mon, 12 Oct 2009 17:48:46 +0200	[thread overview]
Message-ID: <9accb4400910120848n6a1e4036l5e45ce3882deb5aa@mail.gmail.com> (raw)

Hi,
i'm trying to clone a public SVN repo (user = guest, password is
empty/blank/not neeeded)

this was my steps:

$ git --version
git version 1.5.6.5
$ mkdir plugins
$ cd plugins
$ git svn init http://svn.liferay.com/repos/public/plugins -T trunk -b
branches # doesn't have tags
$ git svn fetch
[...]
# it takes hours.....
[...]
r25355 = ee13a19e656e6f96b1ebb562b10ee7fa688921df (svn/trunk)
Filesystem has no item: Working copy path 'plugins/branches/trunk'
does not exist in repository at /usr/bin/git-svn line 3856


after that revision it give me that error... and then stops.
if I issue again the git svn fetch it keep telling me the error and I
can't complete the cloning.

I've edited my .git/config between git svn init and git svn fetch
adding "svn" to the target branch and url name

[core]
	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
[svn-remote "svn"]
	url = http://svn.liferay.com/repos/public
	fetch = plugins/trunk:refs/remotes/svn/trunk
	branches = plugins/branches/*:refs/remotes/svn/*

you can use
git svn fetch --revision 25255:HEAD

to make it take less time (hours anyway)...

Any help will be appreciated,

thanks,
regards,
Daniele

             reply	other threads:[~2009-10-12 15:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 15:48 Daniele Segato [this message]
2009-10-12 18:20 ` Filesystem has no item: Working copy path [...] does not exist in repository at /usr/bin/git-svn line 3856 Eric Wong
2009-10-12 21:26   ` Daniele Segato
2009-10-12 22:45     ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9accb4400910120848n6a1e4036l5e45ce3882deb5aa@mail.gmail.com \
    --to=daniele.bilug@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox