[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion M4 issue #528 resolved, half of #530 resolved

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2001-10-17 05:05:41 CEST

Ben Collins-Sussman <sussman@collab.net> writes:
> So I suspect that this Hudson Scenario has always failed over DAV,
> ever since M2 last April. We just never noticed it, because we didn't
> get the python tests working over DAV until last month. :-(

While we're on this subject, I realized this is also probably the
reason test #11 is failing, too.

Test #11 does this:

   * deletes a file, commits.

   * tries to commit a propchange on the (out-of-date) parent dir

Now, we have a rule in the fs_merge() routine that should *prevent*
this commit from working; the test actually expects failure.

In the ra_local case, the merge() routine is able to notice that the
directory is out-of-date. But because ra_dav always commits against
HEAD, the directory will *never* be out-of-date, and thus the commit
always succeeds!


The "new" planned commit-system isn't going to be able to just ignore
revision numbers coming into the editor (the way ra_dav currently
does). It needs them to check out-of-dateness on dir-props. This is
OK, I think, because our planned system is going to use the revision
numbers for other reasons.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:44 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.