Your message dated Wed, 17 Mar 2010 10:36:22 +0100
with message-id <[email protected]>
and subject line Re: Bug#574261: Bug in fop package
has caused the Debian Bug report #574261,
regarding Bug in fop package
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
574261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574261
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fop
Version: 0.95.dfsg-10
When I run "fop" from an ordinary shell prompt it prints:
$ fop -c /etc/fop.conf -xml 2.xml -xsl 1.xsl -pdf 3.pdf
/etc/fop.conf: line 1: syntax error near unexpected token `newline'
/etc/fop.conf: line 1: `<?xml version="1.0"?>'
/etc/fop.conf: line 1: warning: syntax errors in . or eval will cause future
versions of the shell to abort as Posix requires
...
I find patch for file /usr/bin/fop
I change line 22 in /usr/bin/fop to
fop_exec_args="-c /etc/fop.conf $fop_exec_args "
and after that it works fine.
I am using Debian GNU/Linux 5.0, kernel 2.6.32-trunk-686-bigmem.
Thx.
--- End Message ---
--- Begin Message ---
Hello,
On Wed, Mar 17, 2010 at 8:51 AM, Volodchenkov Dmitry
<[email protected]> wrote:
> When I run "fop" from an ordinary shell prompt it prints:
>
>
> $ fop -c /etc/fop.conf -xml 2.xml -xsl 1.xsl -pdf 3.pdf
> /etc/fop.conf: line 1: syntax error near unexpected token `newline'
> /etc/fop.conf: line 1: `<?xml version="1.0"?>'
> /etc/fop.conf: line 1: warning: syntax errors in . or eval will cause future
> versions of the shell to abort as Posix requires
From the manual page:
CONFIGURATION FILES
fop reads two configuration files on startup: /etc/fop.conf and
$HOME/.foprc. These are plain shell
script files where you can define for instance the
FOP_HYPHENATION_PATH variable.
If you want to define a system-wide fop XML configuration file, use
/etc/fop.xml, or whichever other file you may want. Not /etc/fop.conf,
which is expected to behave like a shell script file. This is also
upstream's use of the /etc/fop.conf.
Of course, if you dump XML there, it won't work at all.
Cheers,
Vincent
--- End Message ---
_______________________________________________
pkg-java-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
