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

Daniele Segato <daniele.bilug@gmail.com> wrote:
> 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

Hi Daniele,

First I thought this was a problem fixed in
83c2fcff214fe89649fcd88e095d9961a36b53dd (git v1.6.2 or later),
but then I tried running it just to make sure.

> $ 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.

This is a namespace conflict, the "trunk" ref is conflicting with a
(what seems to be a miscreated) branch named "trunk".  I anticipated
this problem originally but figured it was rare/uncommon enough that I
didn't want to burden users by prefixing all branches with something:

  ------------------------------------------------------------------------
  r25364 | michael.hashimoto | 2009-01-21 14:06:53 -0800 (Wed, 21 Jan 2009) | 1 line
  Changed paths:
     A /plugins/branches/trunk

  Created directory 'plugins/branches/trunk'.
  ------------------------------------------------------------------------
  r25365 | michael.hashimoto | 2009-01-21 14:07:15 -0800 (Wed, 21 Jan 2009) | 1 line
  Changed paths:
     D /plugins/branches/trunk

  Removed plugins/branches/trunk

Since it looks pretty obvious that "trunk" was miscreated here from the
revision history, you can skip these two revisions in your import by
recontinuing the clone with "git svn fetch -r25365:HEAD"

If you encounter this problem further in a non-workaroundable way,
you can prefix the local branches refs:

Replace:
  [svn-remote "svn"]
    branches = plugins/branches/*:refs/remotes/svn/*

With:

  [svn-remote "svn"]
    branches = plugins/branches/*:refs/remotes/svn/branches/*

I didn't do this by default since I figured very few people would create
a branch named "trunk" (and those who did, did it accidentally as it
seems to be the case here).

Hope that helps.

-- 
Eric Wong

  reply	other threads:[~2009-10-12 18:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 15:48 Filesystem has no item: Working copy path [...] does not exist in repository at /usr/bin/git-svn line 3856 Daniele Segato
2009-10-12 18:20 ` Eric Wong [this message]
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=20091012182018.GA14143@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=daniele.bilug@gmail.com \
    --cc=git@vger.kernel.org \
    /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