From: Daniele Segato <daniele.bilug@gmail.com>
To: Eric Wong <normalperson@yhbt.net>
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 23:26:04 +0200 [thread overview]
Message-ID: <1255382764.15646.5.camel@localhost> (raw)
In-Reply-To: <20091012182018.GA14143@dcvr.yhbt.net>
Il giorno lun, 12/10/2009 alle 11.20 -0700, Eric Wong ha scritto:
> 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.
thank you for taking the time
> 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"
I thought it could be a problem like this but I asked before re-fetching
all the repository (just to be sure)..
unfurtunately I already deleted all the .git directory so i'll have to
start again...
> 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.
Yes it really help...
But I'll change it like this instead:
[svn-remote "svn"]
url = http://svn.liferay.com/repos/public
fetch = plugins/trunk:refs/remotes/svn/master
branches = plugins/branches/*:refs/remotes/svn/*
I think it will do as long as they didn't created some branch named
"master" :)
In this case the repo was public, what should I do to debug some git-svn
issue like that if I encounter a problem with a non-public repo?
May be there is some debug flag I could enable? Or I had to
guess/explore the svn tree?
thank you Eric
regards,
Daniele
next prev parent reply other threads:[~2009-10-12 21:35 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
2009-10-12 21:26 ` Daniele Segato [this message]
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=1255382764.15646.5.camel@localhost \
--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