[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Commit failure after a directory renaming

From: Yves Martin <yves.martin_at_elca.ch>
Date: 2005-09-02 13:32:55 CEST

Yves Martin <yves.martin@elca.ch> writes:

> I have proceeded this way:
> - svn mv buildsystem/j2ee/java/ch/elca/leaf/buildsystem buildsystem/j2ee/java/ch/elca/el4ant
> - svn rm buildsystem/j2ee/java/ch/elca/leaf
> - do changes on files inside the directory (change package declaration for instance)
>
> But when commiting:
> svn: Commit failed (details follow):
> svn: File not found: transaction '248-1', path '/trunk/buildsystem/core/java/ch/elca/el4ant/helper/ProjectLoader.java'

  Really strange. My working copy should have been in a bad state. Need a
  'cleanup' ??

  However, I have done a copy of it, a complete update, apply again my renaming
  'svn mv' and 'svn rm' and commit... and the error change !

[snip]
Adding buildsystem/j2ee/java/ch/elca/el4ant/j2ee
Deleting buildsystem/j2ee/java/ch/elca/el4ant/j2ee/InitTask.java
Sending buildsystem/j2ee/java/ch/elca/el4ant/j2ee/J2eeInitTask.java
[snip]
Sending project.xml
Transmitting file data ........svn: Commit failed (details follow):
svn: Delete failed--directory has no entry 'InitTask.java'

  Damned !

  Why on earth does 'svn' try to delete 'InitTask.java'... I have already
  committed the renaming of
  'buildsystem/j2ee/java/ch/elca/leaf/buildsystem/j2ee/InitTask.java' into
  'buildsystem/j2ee/java/ch/elca/leaf/buildsystem/j2ee/J2eeInitTask.java'
  before renaming the 'leaf/buildsystem' directory into 'el4ant' ???

  I do not understand why the
  'buildsystem/j2ee/java/ch/elca/el4ant/j2ee/.svn/entries' contains a reference
  to 'InitTask.java':
  <entry
   name="InitTask.java"
   copied="true"
   kind="file"
   schedule="delete"/>

  When doing a freash checkout of
  'buildsystem/j2ee/java/ch/elca/leaf/buildsystem/j2ee', the '.svn/entries'
  does not contain 'InitTask.java'.

  My svn client version is on Mandriva LE2005:
svn, version 1.2.0 (r14790) compiled May 31 2005, 14:45:54
  My svn server is on Debian Sarge:
svn, version 1.2.0 (r14790) compiled Jun 29 2005, 12:25:51
  My storage is FSFS and my protocol is 'svn://'...

  Is it really a bug ? I'm not able to reproduce it perfectly. I have 4 or 5
  files in that case but only one got into trouble after 'svn mv' on the
  directory...

  Thank you in advance for any help

-- 
Yves Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 2 13:35:15 2005

This is an archived mail posted to the Subversion Users mailing list.