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

[Subclipse-users] Re: Files are executable at checkout

From: Hendrik Maryns <qwizv9b02_at_sneakemail.com>
Date: Wed, 17 Sep 2008 14:01:32 +0200

Konstantin Kolinko schreef:
> 2008/9/17 Hendrik Maryns <qwizv9b02_at_sneakemail.com>:
>> Mark Phippard schreef:
>>> On Wed, Sep 17, 2008 at 5:11 AM, Hendrik Maryns
>>> <qwizv9b02_at_sneakemail.com> wrote:
>>>> I am bothered by a problem I have been having for a while now. I have
>>>> some TeX projects containing .tex, .pdf and other image files. They
>>>> have been checked in with Subclipse from a Linux desktop. Somehow, the
>>>> files are now marked as executable, since when I check them out on
>>>> another Linux, they are. They are not in the original project, however.
>>>> I have no idea how this change cam into being and cannot really
>>>> reproduce it, since e.g. my latest project doesn't suffer from this.
>>>> Anyway, I'd like to make the files in the projects that have this
>>>> problem non-executable again. Changing the permissions does not give
>>>> any change in the Synchronizing perspective. Is there a way to get this
>>>> done? If not in Subclipse, then maybe from the command line?
>>> Look at the SVN Properties on one of these items and see if the
>>> svn:executable property it set. If it is, then SVN will set the
>>> executable property on the file.
>> Some of them had svn:executable set to *, indeed. But how could this
>> be, since I have never set it myself explicitly? Others have the
>> property svn:special, could this have the same effect?
> See
> http://svnbook.red-bean.com/en/1.5/svn.advanced.props.html#svn.advanced.props.auto
> "Subversion will automatically set the svn:executable property on newly
> added or imported files whose execute bit is enabled."

I suppose this must have come because they were changed on Windows or
something. Or maybe I made them executable once as a mistake. Anyway,
I know how to remedy now, thanks.

And oh yes: svn:special is because the file is a symbolic link.

Cheers, H.

Hendrik Maryns
Ask smart questions, get good answers:

Received on 2008-09-17 14:05:17 CEST

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

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