Re: Ghostscript/GhostPDL 9.25 Release Candidate 1
Jonas Smedegaard <[email protected]> Fri, 14 Sep 2018 11:48:01 +0200
| Newsgroups | gmane.comp.printing.ghostscript.devel |
|---|---|
| Message-ID | <[email protected]> |
Quoting Johannes Meixner (2018-09-14 10:41:07) > On Sep 13 15:51 Chris Liddell wrote (excerpt): > > On 13/09/18 15:43, Johannes Meixner wrote: > >> The call > >> -------------------------------------------------------------------- > >> gs -q -r50 -dNOPAUSE -dBATCH -dSAFER \ > >> -sOutputFile=/dev/null -sDEVICE=nullpage \ > >> /usr/share/ghostscript/9.25/examples/transparency_example.ps > >> -------------------------------------------------------------------- > >> fails with this gs stdout and stderr output: > >> ------------------------------------------------------------------------------ > >> > >> Error: /undefined in .pushpdf14devicefilter > ... > >> GPL Ghostscript RELEASE CANDIDATE 1 9.25: Unrecoverable error, exit code 1 > >> ------------------------------------------------------------------------------ > >> > >> I don't know if '.pushpdf14devicefilter' is also used in general > >> by other PostScript files or tools that output PostScript. > > <SNIP> > > > > It's a custom operator, specific to Ghostscript, and no, it should not > > be used anywhere else. I'm not sure if it only fails in SAFER, but, > > frankly, don't use it. > > I fully agree: Don't use it. > ;-) > > /usr/share/ghostscript/9.25/examples/transparency_example.ps > that uses .pushpdf14devicefilter is the Ghostscript > source file examples/transparency_example.ps > > Because it is a Ghostscript upstream example others may > assume .pushpdf14devicefilter could be regularly used. > At least a comment in transparency_example.ps should explain > that .pushpdf14devicefilter cannot be regularly used. > > I excluded your transparency_example.ps in my ghostscript-testing > package and now the remaining Ghostscript examples succeed, see > https://build.opensuse.org/package/show/Printing/ghostscript-testing > > Perhaps you at Ghostscript upstream could add such kind of test > to your test suite as I run in my ghostscript-testing package > so that you at Ghostscript upstream could notice such issues? > > For the source of my simple test (bash script code) > see the '%build' section in > https://build.opensuse.org/package/view_file/Printing/ghostscript-testing/ghostscript-testing.spec?expand=1 You might also consider adding a "make test" build target to Ghostscript source so that us consumers had a consistent (limited) testsuite to optionally run when building the code. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlubg9EACgkQLHwxRsGg ASF2iBAApUnyXO8+YY8uU7vdWOZ0dvnzj19hZOxcza4WiXE0a7Xb6UdWdoxEwVVs AUrZzsV2cIU4ynsdG7kguQu9Rzwz5GFW/wT3CcFSzf0UgIWwM8ElOyzs3sg9eceU O9kM4oOUGAN2boG+FlLElw692IjHgwVjxMXdm+xfLsQl5T6CAvHbiFZUjQx6vA9m 4ToUtA2HdwL7Da8+0y1qMAhCmNsoRZtoiLJuDRB7u2tSRIwQb7jcStR+cCA3smcM bxG20daWGjozyqdr7dcqV7bj/78vCijzDk3YArIvf2oS0SDDPHJeTCDh7BwwbENg AeN4XiYBEOJBND/lIat3g/ye9KTeEhjZbzF6qTinXksflGaY+LzK083x2aqDJxa+ ukBO2hl+1W6c8Ip3LM7O6eSry81yoAOoK4c4yEUarESgvQNqvvJUQ8xIz5wDKklx TM6jgzGjRgXVsgV7fd/FnHsDix5g+RcEDCBg+xoGJW+PrE3ld4Lwi19D4z37CxdG mdsVVPEoE38C90RwSYIXtLUX/8Ozj8dJYNekpg7dVIalt+bb3NZoH+rMs8pzH64p efDvU105l4Ebk9Frsjfg8n+nf3HdC4AIeEp5J9W0/3hBa669t8XRvU0pM01LRMvg YJBNSOrbsTCc3Yeup/gQLKX8HrlwV6+aSsi+si/1rWwilao3/lM= =OXet -----END PGP SIGNATURE-----