Re: Bug in commiting changes to an fsfs repository?

Mathias.Weinert@gfa-net.de writes:

> Guess what happened... Yes, I again had the problem which I mentioned two
> days ago.
> I have the problem with version 1.2.1 as well as with 1.1.4. But when I
> apply my stuporous
> little patch I can do the commit without any problem.

svn_fs_fs__dag_clone_child is documented as allowing a NULL copy_id.
It passes copy_id to svn_fs_fs__create_successor and that calls
svn_fs_fs__id_txn_create to get a copy_id if NULL is passed. Your
change will cause a different code path to get followed but it's far
from clear that it's correct.

> Next I stepped back to the problematic state of the repository / working
> copy and tried
> it with yesterday morning's trunk (release 15801) and had the same problem
> again.
>
> Please don't hesitate to ask me for any additional information you need to
> find a solution for the problem.

Ideally we would want to know how to reproduce the problem on our own
machines. I suppose one possibility is that your repository already
has some corruption that is causing the problem. Are you able to dump
or verify your repository?

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org