git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Vilz <niv@iaglans.de>
To: git@vger.kernel.org
Subject: git-svn throwing assertion on old svn tracking branch
Date: Thu, 21 Dec 2006 00:55:51 +0100	[thread overview]
Message-ID: <20061220235551.GA2974@hermes.lan.home.vilz.de> (raw)

hello guys,

it has been a while, i tried git in conjunction with svn... i got a nice
history, when working with it. This Work is now a year old.

Now I wanted to get on working and got following error message while
fetching from one specific svn tracking branch:

$ git-svn fetch -i svn_master
perl: subversion/libsvn_subr/path.c:343: svn_path_remove_component: 
Assertion `is_canonical(path->data, path->len)' failed.
Aborted

I checked the svn working copy, it is uptodate now (although i had to
search for it, i havent been using this repository for one year...)

the output of gitk --all looks good, too. So i wonder if that error
message above is only an alternative to say "more work? i ask because i
am finished and have nothing else todo.."

It is only happening to this old repository...

Any help is appreciated. If possible, i would like to keep my development
history for this repository.

I almost forgot, i use git version 1.4.4.3.g545b 

Sincerly
Nicolas

             reply	other threads:[~2006-12-21  0:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 23:55 Nicolas Vilz [this message]
2006-12-21  1:05 ` git-svn throwing assertion on old svn tracking branch Eric Wong
2006-12-22  1:35   ` Nicolas Vilz
2006-12-22  2:16     ` Nicolas Vilz
2006-12-22  8:38       ` Eric Wong
2006-12-22  9:43         ` Nicolas Vilz
2006-12-23  6:45           ` Eric Wong
2007-01-01  2:27   ` Eric Wong
2007-01-05  9:18     ` Nicolas Vilz

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=20061220235551.GA2974@hermes.lan.home.vilz.de \
    --to=niv@iaglans.de \
    --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;
as well as URLs for NNTP newsgroup(s).