Bug#1035420: pdfjam: Produces error "sed ...: not found"
Package: texlive-extra-utils
Version: 2022.20230122-3
Severity: normal
Tags: upstream
When running pdfjam to work with PDF files, it produces the following
error:
/usr/bin/pdfjam: 1141: sed s/^Title:\\\s\*//: not found
Inspecting the pdfjam script reveals that this is due to an improper
quote on line 1141 on my machine (line 1140 in the upstream source).
The line in question currently reads:
grep -e '^Title:'| 'sed s/^Title:\\\s\*//' | \
But should read:
grep -e '^Title:'| sed 's/^Title:\\\s\*//' | \
That is, the single quote should be moved ahead to after "sed".
In the upstream tarball, this is in the file:
texmf-dist/scripts/pdfjam/pdfjam
Note: I found this issue on my Ubuntu machine, but the system
information below is from one of my Debian machines. The issue
still exists in Debian as of the latest version in sid.
-- System Information:
Debian Release: 11.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-20-amd64 (SMP w/2 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages texlive-extra-utils depends on:
pn libunicode-linebreak-perl <none>
ii python3 3.9.2-3
pn tex-common <none>
pn texlive-base <none>
pn texlive-binaries <none>
pn texlive-latex-base <none>
pn texlive-luatex <none>
pn texlive-plain-generic <none>
Versions of packages texlive-extra-utils recommends:
ii ghostscript 9.53.3~dfsg-7+deb11u4
pn libfile-homedir-perl <none>
pn liblog-log4perl-perl <none>
pn libyaml-tiny-perl <none>
pn ruby | ruby-interpreter <none>
pn texlive-latex-recommended <none>
Versions of packages texlive-extra-utils suggests:
pn chktex <none>
pn default-jre-headless <none>
pn dvidvi <none>
pn dvipng <none>
pn fragmaster <none>
pn lacheck <none>
pn latexdiff <none>
pn latexmk <none>
pn purifyeps <none>
pn xindy <none>
Reply to: