Re: Strange svn move behaviour

On 5/20/06, Ryan Schmidt <subversion-2006q2@ryandesign.com> wrote:

> I can't imagine why you
> wouldn't in real use replace the above three commands with "svn mv
> test_file test_file_rn".

Doing an add and replace should be exactly the same as doing a move.
In fact, the same problem still appears when doing a pure move operation.

> To avoid the problem below, you will want to do an "svn update" at
> this point.

This seems to solve the problem!
The update seems to have no effect, but then the problem doesn't
appear ... why do we need to make an update?

However, I've already "manually" solved the problem, editing the
.svn/entries file and deleting the corresponding wrong entry with the
attribute schedule="delete". I know this is not the standard way, but
it works ... there could be some problem?

Thank you very much,
Regards,

Sergio B.

-- 
Sergio Bossa
Developer, software designer, blogger and Open Source believer.
Blogging on: http://sbtourist.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org