Has the issue with the last ghostscript update been resolved? I temporarily added ghostcript to the excludes line in my yum.conf to prevent problems and haven't seen any more mention of it here.
On 01/10/2017 11:28 AM, Frank Cox wrote:
Has the issue with the last ghostscript update been resolved? I temporarily added ghostcript to the excludes line in my yum.conf to prevent problems and haven't seen any more mention of it here.
Nothing yet. You can add yourself to the CC list at https://bugzilla.redhat.com/show_bug.cgi?id=1410260 to monitor progress.
If you exclude only the specific version, you will get subsequent package updates as they become available. exclude=ghostscript-8.70-21.el6_8.1
Hello Frank,
On Tue, 2017-01-10 at 11:28 -0600, Frank Cox wrote:
Has the issue with the last ghostscript update been resolved? I temporarily added ghostcript to the excludes line in my yum.conf to prevent problems and haven't seen any more mention of it here.
Yamaban recently pointed out it's a simple fix. Let me summarize:
$ diff -up /usr/share/ghostscript/8.70/Resource/Init/gs_init.ps.new.bad /usr/share/ghostscript/8.70/Resource/Init/gs_init.ps --- /usr/share/ghostscript/8.70/Resource/Init/gs_init.ps.new.bad 2017-01-04 11:20:37.000000000 +0100 +++ /usr/share/ghostscript/8.70/Resource/Init/gs_init.ps 2015-07-24 00:00:19.000000000 +0200 @@ -2025,7 +2025,6 @@ readonly def /LockFilePermissions true >> setuserparams } - systemdict /getenv {pop //false} put if % setpagedevice has the side effect of clearing the page, but % we will just document that. Using setpagedevice keeps the device
Regards, Leonard.
-
Frank Cox -
Leonard den Ottolander -
Robert Nichols