svn has lost a change to a property

On 9/17/07, David Glasser <glasser@davidglasser.net> wrote:
> On 9/17/07, Dave Rodgman <dave_rodgman@fastmail.co.uk> wrote:
> > Hi,
> >
> > I've observed a concerning problem with subversion (1.4.3 server with
> > FSFS backend). Details (log, diff, propgets) are below. The gist is that
> > a property was modified in revision X+1, then a file was modified in
> > revision X+2; but the value of the property in X+2 is reverted to its
> > value in revision X.
> >
> > It seems highly likely in this case that the user making the second
> > commit in fact didn't change the property (it usually only gets changed
> > by a merging tool which wraps svn, which he wasn't using); so it seems
> > that the property has been corrupted.
>
> The directory in question is the root of the repository, right? I
> think this is issue #2608, fixed a year ago tomorrow in r21540 but
> never backported. Should we backport it?

Nominated for backport in r26848. (In addition to being a minor data
loss bug, it's getting in the way of my run-new-tests-vs-old-servers
work :) )

--dave

-- 
David Glasser | glasser_at_davidglasser.net | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org