threads / discuss / 6070

Re: git-svn throwing assertion on old svn tracking branch

Subject: Re: git-svn throwing assertion on old svn tracking branch

## tl;dr

9 messages between Dec 20, 2006 and Jan 5, 2007.

replies: 8people: 2as markdown or json

Nicolas Vilz· Dec 20, 2006, 23:55 UTC · lore

git-svn throwing assertion on old svn tracking branch

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

Eric Wong· Dec 21, 2006, 01:05 UTC · re: Nicolas Vilz · lore
Nicolas Vilz <niv@iaglans.de> wrote:
Show 12 quoted lines
> 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 don't recall seeing that error before.

Are you using the command-line client or the perl SVN libraries? If you're using the command-line client, you may want to try: rm -rf .git/svn/svn_master/tree && git-svn rebuild -i svn_master

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

Does the directory you're tracking the the repository still exist? If it disappeared, git-svn could have some issues with it (regardless of command-line or SVN libraries).

Nicolas Vilz· Dec 22, 2006, 01:35 UTC · re: Eric Wong · lore
On Wed, Dec 20, 2006 at 05:05:20PM -0800, Eric Wong wrote:
Show 26 quoted lines
> Nicolas Vilz <niv@iaglans.de> wrote:
> > 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 don't recall seeing that error before.
> 
> Are you using the command-line client or the perl SVN libraries?  If
> you're using the command-line client, you may want to try:
> rm -rf .git/svn/svn_master/tree && git-svn rebuild -i svn_master
> 
> > 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...)
> 
> Does the directory you're tracking the the repository still
> exist?  If it disappeared, git-svn could have some issues with it
> (regardless of command-line or SVN libraries).

The repository i am tracking does still exist. both, the tree and the repository are on the same revision-number, so i am a bit clueless.

I tried a fresh fetch of this repository, it worked. so it shouldn't be a client-server version mismatch..

I also tried 
rm -rf .git/svn/svn_master/tree && git-svn rebuild -i svn_master

this had no effect to git-svn fetch -i svn_master... i get the very same error message...

I didn't alter there anything, so i think, fetching works, but if nothing is there to fetch, there is the initial error message...

beneath there is svn, version 1.4.2 (r22196) ... on that repository is Subversion version 1.1.4 (r13838).

Nicolas Vilz
Nicolas Vilz· Dec 22, 2006, 02:16 UTC · re: Nicolas Vilz · lore
On Fri, Dec 22, 2006 at 02:35:10AM +0100, Nicolas Vilz wrote:
> On Wed, Dec 20, 2006 at 05:05:20PM -0800, Eric Wong wrote:
> > Nicolas Vilz <niv@iaglans.de> wrote:
[...]
Show 19 quoted lines
> 
> The repository i am tracking does still exist. both, the tree and the
> repository are on the same revision-number, so i am a bit clueless.
> 
> I tried a fresh fetch of this repository, it worked. so it shouldn't be
> a client-server version mismatch..
> 
> I also tried 
> 
> rm -rf .git/svn/svn_master/tree && git-svn rebuild -i svn_master
> 
> this had no effect to git-svn fetch -i svn_master... i get the very same
> error message...
> 
> I didn't alter there anything, so i think, fetching works, but if
> nothing is there to fetch, there is the initial error message...
> 
> beneath there is svn, version 1.4.2 (r22196) ... on that repository is
> Subversion version 1.1.4 (r13838).

i should ammend, that the same error message comes, when i want to dcommit something in this repository...

Eric Wong· Dec 22, 2006, 08:38 UTC · re: Nicolas Vilz · lore
Nicolas Vilz <niv@iaglans.de> wrote:
Show 9 quoted lines
> On Fri, Dec 22, 2006 at 02:35:10AM +0100, Nicolas Vilz wrote:
> > On Wed, Dec 20, 2006 at 05:05:20PM -0800, Eric Wong wrote:
> > > Nicolas Vilz <niv@iaglans.de> wrote:
> [...]
> > beneath there is svn, version 1.4.2 (r22196) ... on that repository is
> > Subversion version 1.1.4 (r13838).
> 
> i should ammend, that the same error message comes, when i want to
> dcommit something in this repository...

Weird, so you have the SVN:: libraries installed? (dcommit requires it). Is the repository you're tracking public? If so, I'd like to have a look...

-- 
Eric Wong
Nicolas Vilz· Dec 22, 2006, 09:43 UTC · re: Eric Wong · lore
On Fri, Dec 22, 2006 at 12:38:03AM -0800, Eric Wong wrote:
Show 14 quoted lines
> Nicolas Vilz <niv@iaglans.de> wrote:
> > On Fri, Dec 22, 2006 at 02:35:10AM +0100, Nicolas Vilz wrote:
> > > On Wed, Dec 20, 2006 at 05:05:20PM -0800, Eric Wong wrote:
> > > > Nicolas Vilz <niv@iaglans.de> wrote:
> > [...]
> > > beneath there is svn, version 1.4.2 (r22196) ... on that repository is
> > > Subversion version 1.1.4 (r13838).
> > 
> > i should ammend, that the same error message comes, when i want to
> > dcommit something in this repository...
> 
> Weird, so you have the SVN:: libraries installed? (dcommit requires it).
> Is the repository you're tracking public?  If so, I'd like to have a
> look...
unfortunatelly, its not public...

I noticed, it is not the step of committing anything, but the step to fetch the revisions in the svn tree. I had a workaround last night... I used the documentation on Advanced Example: Tracking a Reorganized Repository to reorganize my tree from broken old repository to reorganized fresh tree that is working... that all because time was running out this night and i had to work something.

I keep the old one as a souvenier... The problem lies somewhere there in the old branch. The history is not lost here in any case.

I backuped my repository and pruned my tree as you suggested it... I connected to that remote repository... and then the assertion came down on me. Personally i can live with that reorganized repository. If you are really keen on digging the error down to ground, i could try to setup something.

Perhaps back were i worked on that repository, git-svn accessed a little different from now....

If you are still interested in digging, I think about a private solution for that.

Sincerly Nicolas Vilz

Eric Wong· Dec 23, 2006, 06:45 UTC · re: Nicolas Vilz · lore
Nicolas Vilz <niv@iaglans.de> wrote:
Show 23 quoted lines
> On Fri, Dec 22, 2006 at 12:38:03AM -0800, Eric Wong wrote:
> > Nicolas Vilz <niv@iaglans.de> wrote:
> > > On Fri, Dec 22, 2006 at 02:35:10AM +0100, Nicolas Vilz wrote:
> > > > On Wed, Dec 20, 2006 at 05:05:20PM -0800, Eric Wong wrote:
> > > > > Nicolas Vilz <niv@iaglans.de> wrote:
> > > [...]
> > > > beneath there is svn, version 1.4.2 (r22196) ... on that repository is
> > > > Subversion version 1.1.4 (r13838).
> > > 
> > > i should ammend, that the same error message comes, when i want to
> > > dcommit something in this repository...
> > 
> > Weird, so you have the SVN:: libraries installed? (dcommit requires it).
> > Is the repository you're tracking public?  If so, I'd like to have a
> > look...
> unfortunatelly, its not public...
> 
> I noticed, it is not the step of committing anything, but the step to
> fetch the revisions in the svn tree. I had a workaround last night... I
> used the documentation on Advanced Example: Tracking a Reorganized
> Repository to reorganize my tree from broken old repository to
> reorganized fresh tree that is working... that all because time was
> running out this night and i had to work something.
So the repository was reorganized?  That could be it...
> I keep the old one as a souvenier... The problem lies somewhere there in
> the old branch. The history is not lost here in any case.
Good to know :)
Show 8 quoted lines
> I backuped my repository and pruned my tree as you suggested it... I
> connected to that remote repository... and then the assertion came down
> on me. Personally i can live with that reorganized repository. If you
> are really keen on digging the error down to ground, i could try to
> setup something.
> 
> Perhaps back were i worked on that repository, git-svn accessed a little
> different from now....
 
Some things have changed such as allowing access to repositories with
limited read permissions.  I'm not sure how/if that affects you.  If you
have time, can you try going back to revision
30d055aa1e45b4740edc3bfbff77fa5d65e106ff?  Or try bisecting...
-- 
Eric Wong
Eric Wong· Jan 1, 2007, 02:27 UTC · re: Eric Wong · lore
Eric Wong <normalperson@yhbt.net> wrote:
Show 13 quoted lines
> Nicolas Vilz <niv@iaglans.de> wrote:
> > 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

Actually, I just hit upon a weird bug in svm (SVN::Mirror) that was similar to this (line 114 of the same file, 1.4.2dfsg1-2 in Debian). Can you try taking the trailing slash out of the URL? (.git/svn/svn_master/info/url).

Thanks.
-- 
Eric Wong
Nicolas Vilz· Jan 5, 2007, 09:18 UTC · re: Eric Wong · lore
On Sun, Dec 31, 2006 at 06:27:34PM -0800, Eric Wong wrote:
Show 21 quoted lines
> Eric Wong <normalperson@yhbt.net> wrote:
> > Nicolas Vilz <niv@iaglans.de> wrote:
> > > 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
> 
> Actually, I just hit upon a weird bug in svm (SVN::Mirror) that was
> similar to this (line 114 of the same file, 1.4.2dfsg1-2 in Debian).
> Can you try taking the trailing slash out of the URL?
> (.git/svn/svn_master/info/url).
> 
> Thanks.

Actually I can fetch the revisions now again. Maybe that that little trailing slash did it.

Nicolas Vilz

← back to recent threads