Package: fop
Version: 1:2.6-2
Severity: normal
Tags: newcomer
X-Debbugs-Cc: tstev...@gmail.com
Dear Maintainer,
* What led up to the situation?
HOME environmental variable has a space in it.
* What exactly did you do (or not do) that was effective (or
ineffective)?
The fix is to double quote line 46 of /usr/bin/fop.
$ diff /usr/bin/fop fop
46c46
< . $HOME/.foprc
---
> . "$HOME/.foprc
* What was the outcome of this action?
fop works as expected with the patch. Without the patch fop fails:
HOME="/home/tsteven4/work/doc link" fop -q -fo gpsbabel.fo -pdf gpsbabel.pdf
/usr/bin/fop: 46: .: cannot open /home/tsteven4/work/doc: No such file
* What outcome did you expect instead?
I expect fop to work normally even when HOME has an embedded space
character.
see https://bugs.launchpad.net/ubuntu/+source/fop/+bug/1993853
LP: #1993853
-- System Information:
Debian Release: bookworm/sid
APT prefers jammy-updates
APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'),
(100, 'jammy-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 5.15.68.1-microsoft-standard-WSL2 (SMP w/20 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages fop depends on:
ii default-jre-headless [java2-runtime-headless] 2:1.11-72build2
ii libfop-java 1:2.6-2
ii openjdk-11-jre-headless [java2-runtime-headless] 11.0.16+8-0ubuntu1~22.04
Versions of packages fop recommends:
ii libsaxon-java 1:6.5.5-12
Versions of packages fop suggests:
pn fop-doc <none>
-- no debconf information
