* debian/patches/25_fix-driver-in-printer-xml-without-driver-xml.patch:
If a printer XML entry has a driver in its driver list but for which
there is no driver XML entry, this printer/driver combo was considered
as producing a PPD because the driver is not in the list of drivers
without command line prototype. This leads for example to non-working
"Foomatic/Gutenprint" driver entries in the printer setup tools
(LP: #373371).
* debian/patches/20_fix-jcl-options-as-members-of-composite-options.patch:
Upstream fix in the PPD generator: In Foomatic PPDs JCL options were
broken when they where member options of a composite options. In addition
to these options not being correctly applied this made them also be
interpreted as a PostScript options which in turn made foomatic-rip
converting PDF jobs to PostScript. This made some printers suffering
LP: #361772 which usually is worked around by the PDF printing workflow.
-- Till Kamppeter <email address hidden> Fri, 8 May 2009 12:57:49 +0200
This bug was fixed in the package foomatic-db-engine - 4.0.0-0ubuntu6.1
---------------
foomatic-db-engine (4.0.0-0ubuntu6.1) jaunty-proposed; urgency=low
* debian/ patches/ 25_fix- driver- in-printer- xml-without- driver- xml.patch: Gutenprint" driver entries in the printer setup tools
If a printer XML entry has a driver in its driver list but for which
there is no driver XML entry, this printer/driver combo was considered
as producing a PPD because the driver is not in the list of drivers
without command line prototype. This leads for example to non-working
"Foomatic/
(LP: #373371).
* debian/ patches/ 20_fix- jcl-options- as-members- of-composite- options. patch:
Upstream fix in the PPD generator: In Foomatic PPDs JCL options were
broken when they where member options of a composite options. In addition
to these options not being correctly applied this made them also be
interpreted as a PostScript options which in turn made foomatic-rip
converting PDF jobs to PostScript. This made some printers suffering
LP: #361772 which usually is worked around by the PDF printing workflow.
-- Till Kamppeter <email address hidden> Fri, 8 May 2009 12:57:49 +0200