Re: entry and wcprops stored in repository(!) (was: bug? "Delta source ended unexpectedly")

Ben Collins-Sussman wrote:
>
> Ben Collins-Sussman <sussman@collab.net> writes:
>
> > > How did you do the 'merge' for that revision?
> >
> > Bam! Issue 1012 is the culprit!
> >
> > It's already fixed, but I'll bet a huge sum that this is the exact bug
> > that caused blair's bogus wc. He didn't realize that he got extra
> > props, and then committed them.
>
> So here's what we need to do from here:
>
> 1. Make sure everyone is running a post r4023 client, so nobody gets
> bitten by issue 1012, accidentally creating bad props.

I have a public Subversion repository that is used by people that
don't have the time or the inclination to rebuild Subversion when
something like this happens, and I'm concerned about a client doing
something similar to my repository.

Is there anyway for the me to have my Subversion server validate
the Subversion client version number?

This would be a good thing to have, and would be another reason to
have the Subversion revision number compiled into the client in
addition to the 0.XX.Y style revision number.

The version check would occur all but the GET, OPTIONS, PROPFIND,
REPORT methods, because you'd still like to have people check out
the repository with an older client.

I think this would have to be something the server does and not
something you'd check in Apache, because if you did this in Apache,
svnserve would not be protected.

When the client accesses a server with svn://, does it send it's
version along?

Best,
Blair

-- 
Blair Zajac <blair@orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org