RE: File not found: transaction 'x', path /X/Y/Z

OK, Here is the transcript of my entire bash session. Note that it starts
with the repository created and the directory structure

/swimming/trunk
         /tags
         /branches

already created (exited that bash session so the transcript of those
commands and responses are unavailable).

But this starts out right from the initial checkout after the import, so
hopefully it will allow reproduction of the problem by others :-)

In the meantime, I'll see if I can create a script that will reproduce this
:-)

Thanks for the help,

Peter

-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Tuesday, May 04, 2004 7:58 AM
To: Peter Milliken
Cc: users@subversion.tigris.org
Subject: RE: File not found: transaction 'x', path /X/Y/Z

Peter, please keep this mail on the users@ list.

On Mon, 2004-05-03 at 16:51, Peter Milliken wrote:
> Ben,
>
> It would appear that I get the same error when using the svn command line
> after all. I received the following when I attempted to commit a directory
> (am I doing the right thing by this?????) after changing it's ignore
> properties (used "svn propedit svn:ignore data"):
>
>
> roebourne240#1(/c/tmp/swimming)$ svn status
> M .
> ? data\Records
> M S data
> ? data\meet_data\Conversion Constants
> M data\meet_data
> M data\child_data
> roebourne240#1(/c/tmp/swimming)$ svn commit data
> Sending data
> svn: Commit failed (details follow):
> svn: File not found: transaction 'd', path '/swimming/data'
> svn: Your commit message was left in a temporary file:
> svn: 'c:/tmp/swimming/data/svn-commit.tmp'
> [exited with 1]
> roebourne240#1(/c/tmp/swimming)$
>
>
> As you can see, the directory (data) was shown as modified by the status
> command, so I presume I should perform a 'commit'. But the commit failed
> with the same error message that I was getting through the Tortoise SVN
> interface.
>
> Please not that I cleaned the repository first and performed all the same
> steps as outline in my first email.

I still don't understand: can you show us an actual commandline
transcript, from start to finish, which shows us the entire problem? I
want to be able to reproduce the problem on my own machine. (Even
better would be a /bin/sh script that I can run which demonstrates the
bug!)

Warning: Copyright ResMed. Where the contents of this email and/or attachment includes materials prepared by ResMed, the use of those
materials is subject exclusively to the conditions of engagement between ResMed and the intended recipient.
 
This communication is confidential and may contain legally privileged information.
By the use of email over the Internet or other communication systems, ResMed is not waiving either confidentiality of, or legal
privilege in,the content of the email and of any attachments.
If the recipient of this message is not the intended addressee, please call ResMed immediately on +61 2 9886 5000 Sydney, Australia.

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