[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: Wade Hampton <wade.hampton_at_nsc1.net>
Date: 2004-12-02 21:28:48 CET

kfogel@collab.net wrote:

>Wade Hampton <wade.hampton@nsc1.net> writes:
>>To fix, all I had to do was to remove the four lines starting at K 14
>>which made the symlink executable. Symlinks are mode 777
>>by default hence making it executable is not required (may fail?).
>>I think the problem was that VERSION.sh had been a file
>>reference (made executable), but was removed (svn rm)
>>and replaced with a symlink (svn add). The make executable
>>must be an artifact. However, it should not kill my checkouts
>>of the repo (at most should cause a warning). This seems to be
>>a bug in svn.
>I agree.
>Could you do us a favor? Based on what you know now, can you
>construct a minimal reproduction script (preferably one that involves
>only working copies and a repository -- it would be easy to make using
>a hand-constructed dumpfile, of course, but that's not a normal
>situation), and file a bug, including a pointer to this thread in the
>archives, and your script?
Problem duplicated. See attached tar file and scripts.

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
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.

    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"

I would recommend fixing in at least two places:
1) where the file gets created, if it is a symlink don't set executable....
2) when checking out, if trying to set a symlink executable, print a
warning (audit?) but don't die....

>This should be pretty easy for us to fix, I just want to get it down
>to a clean recipe first.
See attached. You might want to copy my scripts and make a "test
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).


Wade Hampton

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:31:25 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.