Bug 51327

Summary: fop.bat, fop.cmd, ... should have svn:executable property in SVN ?
Product: Fop - Now in Jira Reporter: Bill Meier <wmeier>
Component: generalAssignee: fop-dev
Status: CLOSED INVALID    
Severity: minor    
Priority: P3    
Version: 1.0   
Target Milestone: ---   
Hardware: PC   
OS: All   

Description Bill Meier 2011-06-06 17:06:03 UTC
After installing fop-1.0 (to upgrade from fop-0.95) and then running Visual C nmake which then invokes fop.bat, I got the following message:

   c:\...\fop-1.0\fop.bat ... ...
NMAKE : fatal error U1045: spawn failed : No error


Windows 7; MSVC 9 (2008); 
fop-1.0 installed from fop-1.0-bin.zip using:
UnZip 6.00 of 20 April 2009, by Cygwin. Original by Info-ZIP.

A bit of poking around on the web suggested a permissions problem.

I don't really understand how to use Windows7 tools to view/change file permissions so I just used cygwin 'ls' and found that fop.bat wasn't marked as executable (according to cygwin 'ls').

So: I tried a different unzip (Winzip) to install fop-1.0 again (after removing the first install) and found that that fop.bat was then magically marked as executable; invoking fop.bat via nmake worked AOK.

I don't understand all that goes on behind the scenes but I'm guessing that setting the svn:executable property for the Windows .bat & .cmd files in the SVN repository might be the right way to go.

================
Contents of /xmlgraphics/fop/trunk/fop.bat

Revision 697152 - (show annotations) (download)
Fri Sep 19 17:01:03 2008 UTC (2 years, 8 months ago) by adelmelle
File MIME type: text/plain
File size: 3915 byte(s) 

...

Properties
Name 	Value
svn:eol-style 	CRLF
svn:keywords 	Author Date Id Revision
Comment 1 Bill Meier 2011-06-06 17:16:43 UTC
(For some reason trying to set the 'Platform' in this bug repprt to Windows 7 results in 'All')
Comment 2 Simon Pepping 2011-06-08 07:34:48 UTC
Windows does not have an executable permission. Did Windows7 change that?

fop.bat never had an executable permission, not even in fop0.95. I fail to see why you come to the conclusion that the absence of an executable permission causes your problem.
Comment 3 Glenn Adams 2012-04-07 01:41:36 UTC
resetting P2 open bugs to P3 pending further review
Comment 4 Glenn Adams 2012-04-09 18:56:58 UTC
insufficient information to reproduce
Comment 5 Glenn Adams 2012-04-30 00:11:27 UTC
batch transition resolved+invalid to closed+invalid