On Thu, 23 Jun 2005, Ben Collins-Sussman wrote:
>
> On Jun 23, 2005, at 12:46 AM, Eric Wong wrote:
>
> > The svn:executable property isn't (always) handled in the correct
> > order
> > for symlinks.
> >
> > I had a bunch of scripts and also symlinks to those scripts in one
> > directory that I needed to make executable. Naturally, the fastest way
> > was to just run this:
> >
> > svn propset svn:executable ON *
> >
> > and set svn:executable on everything in the directory, even the
> > symlinks
> > there. That was the only change I made when I committed the changes.
> >
> > Then another user tried to do a fresh checkout of the directory I was
> > working on. Unfortunately, `svn co' created some of the symlinks
> > before
> > the original file it linked to was created and tried to set
> > svn:executable on it. This caused the checkout to fail.
> >
> > I've made a small repo and was able to reproduce the bug (after the
> > second try, if you look closely :); you may download the test
> > repository
> > here:
> >
> > http://yhbt.net/svn_executable_symlink_bug_repo.tar.gz
> >
> > A quick workaround for this was to check out the previous revision
> > of the
> > directory, and then `svn up' to the latest.
> >
>
> Aha, can you please file this as a new issue?
>
>
Wait a moment, I think the real bug is that you can set svn:executable on
a versioned symlink. then subversion set the executable bit on the
symlink, which actually affects the link target. That's wrong. I think we
have (had?) the same bug for the read-only state when svn:needs-lock is
set.
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 23 14:13:36 2005