Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#68137 - openprinting support dropped from ghostscript package
Attached to Project:
Arch Linux
Opened by Drew DeVault (SirCmpwn) - Wednesday, 07 October 2020, 15:23 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 07 October 2020, 16:37 GMT
Opened by Drew DeVault (SirCmpwn) - Wednesday, 07 October 2020, 15:23 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 07 October 2020, 16:37 GMT
|
DetailsThe ghostscript package dropped openprinting support in version 9.52. This breaks some printer drivers. To correct this, add --with-openprinting to the configure arguments.
|
This task depends upon
Closed by Andreas Radke (AndyRTR)
Wednesday, 07 October 2020, 16:37 GMT
Reason for closing: Fixed
Additional comments about closing: 9.53.3-2
Wednesday, 07 October 2020, 16:37 GMT
Reason for closing: Fixed
Additional comments about closing: 9.53.3-2
From the commit message: https://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=66c2469c7d4543f32d6dc93edf1d649e809b8419
That option does not appear in the --help output because we want people to have to ask us about it, so we know if people actually use opvp/oprp, and still need them.
From the release notes:
IMPORTANT: In consultation with a representative of (OpenPrinting) it is our intention to deprecate and, in the not distant future, remove the OpenPrinting Vector/Raster Printer Drivers (that is, the opvp and oprp devices).
...
It does seem reasonable to provide still-in-use functionality for as long as it's still there.
Not sure if we should add it back if upstream disables the support by default and wants to drop it completely pretty soon.