> On Mar 27, 2009, at 15:43, B Smith-Mannschott wrote:
>
> > I now have a 1.6 GB repository which I no longer able to back up
> using
> > svnsync. Correcting the problem would mean dumping, editing the
huge
> > dump file and reloading the repository. I have no way of preventing
> > this from occuring again since the server doesn't protect itself
> > against misbehaving clients.
>
> I have not tested to verify this problem. But I agree Subversion
> should prevent it. Until it does, you can prevent it by writing a pre-
> commit hook which tests the svn:ignore property (and possibly
> svn:externals and others). If you want to correct the problem in your
> existing revisions and can tolerate a dump and load cycle,
> svndumptool should be able to help you.
I don't think that's the right approach.
If Subversion starts to enforce a restriction that it didn't enforce in
an earlier version, it's the responsibility of Subversion -- not of the
admin -- to provide backwards compatibility. Preferably it should
accept the older, less restricted, data. Failing that, it should
provide a conversion process. Telling admins they have to construct
hook scripts to deal with something Subversion did to them is not a good
answer.
paul
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1456932
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-28 15:49:38 CET