Created attachment 166971 [details]
Fix conflict print/foomatic-filters and print/cups-filters.
Rename /usr/local/libexec/cups/backend/beh into foomatic-beh.
Created attachment 166972 [details]
Created attachment 166973 [details]
Created attachment 166974 [details]
Created attachment 166975 [details]
The release manager for cups (Mike Sweet from apple, see
said in private mail that foomatic-filters is replaced by cups-filters.
So maybe it's time to DEPRECATE the foomatic stuff ?
Yes, I agree to deprecating foomatic-filters. If that is done, then patching foomatic-filters would be unnecessary.
I think, in the first time need update this port.
Then need will testing replace foomatic-filters on foomatic-cups,
especially need testing port /print/foo2js, which depend from foomatic-filters.
Testbuilds are fine.
A commit references this bug:
Date: Mon Feb 15 16:51:06 UTC 2016
New revision: 408946
print/foomatic-filters: remove CONFLICT with cups-filters
Submitted by: Vladimir Omelchuk <firstname.lastname@example.org>
Approved by: email@example.com (maintainer)
(In reply to Vladimir Omelchuk from comment #7)
I've tried to use foomatic-rip, built and installed from the modified print/cups-filters port, with foo2zjs (built from source), and it seems to be working.
The NEWS file from the cups-filters contains following:
"Moved foomatic-rip's upstream home from the
foomatic-filters package to cups-filters, to make it easier
for distributions to ship and maintain a complete printing
stack and also to make upstream maintenance and development
So, to deprecate print/foomatic-filters in favor of print/cups-filters looks reasonable
(In reply to Alexander Zagrebin from comment #11)
If you tested and port print/foo2zjs correctly work with print/cups-filters,
modify ports and add PR into bugzilla.