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

Re: repost: "No such file or directory" on checkout leaves locks....

From: <kfogel_at_collab.net>
Date: 2004-12-02 21:54:07 CET

Wade Hampton <wade.hampton@nsc1.net> writes:
> Problem duplicated. See attached tar file and scripts.

I got a tar file containing a working copy (crash1.tgz, unpacking into
crash1/, which has subdirs trunk/, tags/, and branches/, etc).

I didn't see any attachment with scripts, though?

> I think the problem came about because we added the script, then removed it,
> then turned it into a link all before checking in (I seem to remember
> having
> to do a --foce at least one time when dealing with this script). The
> problem seems
> to be on the initial creation of the symlink and the executable part
> seems to be a
> leftover attribute from when I initially was adding a file.

When you removed it, the properties were removed as well as the
contents, so I (tentatively) didn't buy that explanation... but
looking below, I see that there was no commit after the add. It was
added, then removed immediatey, then re-added as a symlink.

> touch new_file
> chmod +x new_file
> svn add new_file
> svn rm --force new_file
> ln -s some_old_file new_file
> svn add --force new_file
> svn commit -m "added new_file as symlink"

So if I try the above in a working copy, then try to check out HEAD, I
should get the error? See below...

> See attached. You might want to copy my scripts and make a "test
> framework"
> for duplicating problems and reporting them to you. I have a config
> file, make
> a repo, test a repo, and create a dump file (all in 6 scripts).

6 scripts to reproduce this problem?? :-) (I mean, I didn't see them
attached anyway, but I'm surprised there would need to be more than
one brief shell script.)

I wrote a script to try to reproduce based on the information in your
mail (which I realize may have been incomplete). The bug didn't
reproduce, at least over file:// access, with the latest development
Subversion (12130), on a Debian GNU/Linux box.

Here's the script, tell me if I'm missing something important:

#!/bin/sh

SVN=${HOME}/src/subversion/subversion/clients/cmdline/svn
SVNADMIN=${HOME}/src/subversion/subversion/svnadmin/svnadmin

# URL=http://localhost/SOMETHING/repos
# URL=svn://localhost/SOMETHING/repos
URL=file:///`pwd`/repos

rm -rf repos wc other_wc

${SVNADMIN} create repos

${SVN} co ${URL}/ wc

cd wc

touch orig_file
${SVN} add orig_file
${SVN} ci -m "add orig_file"
${SVN} up

##### Now to Wade's part of the repro recipe. #####
touch new_file
chmod +x new_file
${SVN} add new_file
${SVN} rm --force new_file
ln -s orig_file new_file
# The '--force' below is not actually necessary.
${SVN} add --force new_file
${SVN} commit -m "added new_file as symlink"

cd ..

${SVN} co ${URL}/ other_wc

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 2 21:59:46 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.