This is a bug fix release which fixes several bugs leading foomatic-rip to crash. This happened especially with PJL commands and if the incoming job comes from a Windows client.
In addition, foomatic-rip builds now on Mac OS X and this enables the new Foomatic generation also for this operating system.
My special thanks go to Lars Uebernickel who made the Mac OS X build working. He also fixed some bugs in the handling of the renderer command line.
In foomatic-db-engine some small bugs in PPD file generation, especially for CUPS custom options, were fixed and the PPDs enable the integration of foomatic-rip in the PDF printing workflow of Mac OS X.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
foomatic-4.0.2-1.fc11 has been submitted as an update for Fedora 11.
Does anyone know when we might get this update? I think I need it to fix segfaults I'm getting in foomatic-rip. I don't see it at the link in Comment #2, nor have I seen it in updates-testing.
The foomatic-rip segfault is bug #496521.
The updates-testing queue hasn't been working for me for the last couple of weeks. I've pushed the foomatic update for the 'updates' channel (i.e. stable updates) now -- hopefully it will actually get pushed this time.
foomatic-4.0.2-3.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
Despite of FEDORA-2009-7448 notification from 2009-07-11 it does not look that foomatic-4.0.2-3.fc11 really ever made to mirrors (while various later packages did; at least to some mirrors) so closing that may be a tad premature.
The same goes for "companion" system-config-printer-1.1.8-5.fc11 packages (FEDORA-2009-6777 from the same day).
Reported to Fedora admin:
foomatic-4.0.2-4.fc11 has been submitted as an update for Fedora 11.
foomatic-4.0.2-4.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.