multiple propset before commit

[Eric Malafeew <em...@rcn.com>]

I'm new to this list and subversion, but a long time CVS user and admin.
I've been evaluating subversion 1.0.5 for a couple weeks and noticed this
bug, which I didn't find in the issue tracker:

If you propset multiple times before a commit, the commit fails rather than
accept the latest propset.

>svn propset svn:ignore foo .
>svn propset svn:ignore bar .
>svn commit
Sending        run
svn: Commit failed (details follow):
svn: Out of date: '/test/trunk/run' in transaction '77'

The second propset is in effect locally, as evidences by a svn status, seems
like it's unambiguous to commit.

BTW my company was using CVS with a couple modifications and GUI that I
wrote (preceding but eerily similar to RapidSVN), before switching to
Perforce this year.  Most of the reasons were addressed by Subversion but
binary-file locking was a show stopper.  Also during my evaluation I've come
across some of the win32 bugs mentioned in the issue tracker, which could
scare our average user.  Perforce doesn't satisfy my need to branch and
switch frequently, among other reasons, so I hope we'll come back to
Subversion.

--
Eric Malafeew
Senior Programmer, Harmonix Music Systems


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: multiple propset before commit

[Ben Collins-Sussman <su...@collab.net>]

On Mon, 2004-07-19 at 00:13, Eric Malafeew wrote:

> >svn propset svn:ignore foo .
> >svn propset svn:ignore bar .
> >svn commit
> Sending        run
> svn: Commit failed (details follow):
> svn: Out of date: '/test/trunk/run' in transaction '77'

You're misdiagnosing the problem.  I can tell you exactly what's going
on, and it has nothing to do with 'propset' or 'svn st -u'.  :-)

There are two limitations to mixed-revision working copies, as described
at the end of chapter 2 in the book:

1. you can't delete a file or dir which isn't the latest version.

2. you can't commit a change to a directory (i.e. a propchange) unless
the working rev of the directory == HEAD.

That's why you're seeing the out-of-date error.  Just 'svn up' so that
your directory's working-rev == HEAD first, and the commit will succeed.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org