Re: Bug in commiting changes to an fsfs repository?
Unfortunately I even can't reproduce it with my subversion 1.2.1...
The repository I used yesterday is now in a state where I don't get this
problem although I think that I do just the same as yesterday.
Can you tell me in which situation I will get the error again? Sorry for
(If I can reproduce it again I will test with today's trunk version which
I have already built)
> Mathias.Weinert@gfa-net.de writes:
> > I sometimes get errors while commiting changes to subversion (1.2.1
> > cygwin, repository uses fsfs):
> > $ svn ci -m "A.txt moved from dir1 to dir2"
> > Deleting test/dir1/A.txt
> > Adding test/dir2/A.txt
> > svn: Commit failed (details follow):
> > svn: Can't open file
> > '/d/Subversion/repos/db/transactions/149-13.txn/node.15.w ♫§ ': No
> > file or directory
> > (The characters after 'node.15.w' are in this case hex '0F 0E 15 0F')
> > This happens sometimes but not always and I haven't found out when it
> > happen and when it will not.
> > After looking at the subversion sources, it seems to be a problem to
> > a copy_id of NULL to svn_fs_fs__dag_clone_child in make_path_mutable
> > libsvn_fs_fs/tree.c.
> > When I changed line 816 in libsvn_fs_fs/tree.c. from copy_id = NULL;
> > copy_id = "0"; the problem didn't occur any more.
> > So for me it seems as if there is a bug in subversion. Perhaps you
> > investigate this and in case you agree that there is a bug you surely
> > find a better fix for this problem as did.
> Thanks for the report! Can you reproduce this problem with today's
> trunk code?
Received on Thu Aug 18 16:42:17 2005
This is an archived mail posted to the Subversion Dev