On Mon, Jul 11, 2011 at 11:33:57AM +0100, Philip Martin wrote:
> This issue is about rejecting commits that attempt to introduce invalid,
> i.e. fails to parse, svn:mergeinfo. This has been fixed on trunk and
> was backported to 1.6.17. It turns out that the fix was incomplete: it
> didn't fix commits through mod_dav_svn, see issue 3953.
> I voted for the 3895 backport but I've now realised it causes problems
> for repositories that already include invalid mergeinfo: they can no
> longer be copied by dump/load or svnsync. There is no easy way for
> users to correct the problem.
> Do we need to provide a way for users to handle such repositories?
> Force the commit? Delete the mergeinfo? Attempt to correct the
Your concerns are related to this issue:
"mergeinfo syntax errors should be treated gracefully"
We should allow invalid mergeinfo to exit the repository, e.g. in a dump
file. But input paths, such as svnadmin load, should refuse invalid mergeinfo.
Maybe we should provide a way to fix invalid mergeinfo in dump files.
One existing but no officially supported method is svndumptool
Received on 2011-07-11 14:12:02 CEST