On 11 July 2013 09:19, Lorenzo <l.fraccaro_at_autecsafety.com> wrote:
> Hello
>
> We're running Tortoise SVN on 3 machines with a single repository on a Windows 2000 server with Apache Subversion 1.5.4.
> I find no previous complaint about following problem in the mailing list.
>
> This is the sequence that caused the problem:
>
> 1) updated TortoiseSVN to revision 1.8
> 2) TSVN requested updating working copies
> 3) confirmed update of working copies to 1.8
> 4) changed some source files
> 5) built executable (Windows 32 bit application)
> 6) committed changes, including executable file
> 7) launched executable
> 8) Windows complains that "file is not excecutable"
>
> All committed files have one or more svn:keywords active at the project level, therefore also executable files.
> Comparing executable file with latest revision, all '$' characters have been replaced by the sequence "$: ".
> This disrupted the executable file.
> I remembered that svn:keywords substitution should not affect binary files, and I can confirm that the executable file is seen by Tortoise as such.
>
> Is this a bug of Tortoise 1.8 or am I missing something ?
Why do you set svn:keywords on an executable file if you don't want
keyword substitution?
Why do you even version an executable file?
Simon
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3060234
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-07-11 10:33:02 CEST