Re: Log command for directory is mislocated

On Tue, Mar 18, 2008 at 08:47:18AM -0700, Robert Denton wrote:
> Any suggestions on this before we blow away our changes and
> re-checkout the project?

Well, no, not yet, but please keep the broken working copy
around for analysis :)

I'll try to help.
 
> A user was renaming files via TSVN and ended up not being able
> to commit or update (a cleanup was required/asked for) and the
> clean up fails with:
>
> Log command for directory file.gif is mislocated.

Skimming the code, if I understand it correctly, it seems that this
condition can only be triggered if:

1. file.gif used to be a file

2. A commit of this file to the repository was successful, but svn was
   interrupted while modifying working copy meta data that reflects
   the state of this file. Files marked "locally modified" and similar
   need to be flagged as "up to date" after a successful commit.
   Subversion keeps a log of working copy operations before actually
   carrying them out, in order to be able to replay interrupted or
   aborted operations. Because of the interrupted commit operation
   there is still an operation on this file scheduled in the log.
   This operation is what svn cleanup tries to carry out.

3. file.gif is now a directory, not a file anymore. So the log cannot
   be replayed as it assumes that file.gif is a file.

Does that match what the user has done?

If so, could you try to find out what happened between 2. and 3. ?
Did someone deliberately or by accident replace file.gif with
a directory of the same name?

-- 
Stefan Sperling <stsp_at_elego.de>                 Software Developer
elego Software Solutions GmbH                            HRB 77719
Gustav-Meyer-Allee 25, Gebaeude 12        Tel:  +49 30 23 45 86 96 
13355 Berlin                              Fax:  +49 30 23 45 86 95
http://www.elego.de                 Geschaeftsfuehrer: Olaf Wagner