Weird need for "svn update"

Hi all,

I've got this script attached which doesn't run smoothly when a specific
update is missing (see comment in the script).

This is the same for 1.5.6, 1.6.2 and trunk.

Can anyone explain to me *why* that update in there is necessary?

Thanks,
~Neels

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2360921

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].

#!/bin/bash

## UNCOMMENT AND CONFIGURE THIS:
#alias svn /path/to/bin/svn
#alias svnadmin /path/to/bin/svnadmin

echo "I'm gonna ERASE ./repos and ./wc (enter to proceed)"
read
svn --version
set -x
rm -rf repos wc
svnadmin create repos
svn co file://`pwd`/repos wc
cd wc

mkdir dir
echo fool > dir/foo
svn add dir
svn ci -m log1

## The problem disappears when removing this edit:
echo once > dir/foo
svn ci -m log2

## And uncommenting this following line also fixes the problem;
## why is this update necessary?
#svn up

# The following commit says it's out of date.
svn rm dir
svn ci -m log3
echo "what, out of date?"

# The following update creates a tree-conflict with >=1.6,
# succeeds without problems with <=1.5.6
svn up
svn ci -m log3