On 9/23/07, Karl Fogel <kfogel@red-bean.com> wrote:
> "Joe Swatosh" <joe.swatosh@gmail.com> writes:
> > D:\SVN\r26758>svn propset pn pv wc -R
> > property 'pn' set (recursively) on 'wc'
> >
> > D:\SVN\r26758>svn commit wc -m ""
> > Sending wc
> > svn: Commit failed (details follow):
> > svn: Out of date: '/wc' in transaction '2-2'
> >
> > D:\SVN\r26758>svn up wc
> > At revision 2.
> >
> > D:\SVN\r26758>svn commit wc -m ""
> > Sending wc
> > Sending wc\t.txt
> >
> > Committed revision 3.
> >
> > I was suprised that I couldn't commit the propset until after an update. I
> > always thought after committing the add of the file that the working copy
> > would be in sync with the repository. The tests obviously already consider
> > this.
>
> I haven't looked at the Ruby failures in detail yet, but I think
> what's going on above is that the "-R" is causing property "pn" to be
> set to value "pv" down through the entire working copy -- on
> directories as well as files. Subversion requires directories to be
> completely up-to-date before you can commit property changes to them.
I think I knew that. What was surprising was that the 'svn commit wc' above
didn't make the 'wc' be at revision 2. If I had done 'svn commit
wc\t.txt' I would
have expected (at least not questioned) the behavior I got.
>
-----snipped additional explanation and recipe.
>
Thanks,
--
Joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 24 02:23:46 2007