a newer version of net-print/xerox-drivers than the current 0_p20080123 is available, see, e.g., http://www.support.xerox.com/support/workcentre-5225/file-download/enus.html?operatingSystem=linux&fileLanguage=en&contentId=68540&from=downloads&viewArchived=false
workaround: install the ppd manually (but perhaps some other support files are needed, I've seen *.so files in the driver pqckqge lib directory? our workcentre 5230 is detected/configured, but I haven't actually managed to print anything yet)
To get the printer to work, I downloaded the generic PPD (for Win7, but I guess that doesn't matter) from http://www.support.xerox.com/support/workcentre-5225/file-download/enus.html?operatingSystem=win7&fileLanguage=en&contentId=114774&from=downloads&viewArchived=false and modified it by removing any lines referring to files not present on my system, i.e., those containing the string "/Library/" and use that ppd while installing the printer through CUPS.
I guess this removes my need for action on this Bug. Perhaps close as resolved wontfix?
I'll see if I can submit my ppd to openprinting/cups-filters. But I see I'll have to create yet-another-account for that... sigh.
I'm a bit confused about this package. It looks like there is no "xerox-drivers" upstream and the Linux drivers of various versions are scattered amongst product-specific pages?
(In reply to Michael Palimaka (kensington) from comment #2)
> I'm a bit confused about this package. It looks like there is no
> "xerox-drivers" upstream and the Linux drivers of various versions are
> scattered amongst product-specific pages?
I think so too. Also, since the original report, I've moved to a different job and a different printer (make), so given the fact that there is only one other person in Cc… (who can react) I personally suggest marking this RESOLVED WONTFIX. People should just download the ppd for their specific model themselves.
Thanks for the info. Do you have any opinion whether it makes sense to keep this package in the tree the way it is or not?
(In reply to Michael Palimaka (kensington) from comment #4)
> Do you have any opinion whether it makes sense to keep
> this package in the tree the way it is or not?
No, I don't use it. Barring usage data, one can't know whether others do, I guess.
Created attachment 512718 [details]
Did you guys bother to untar the tarball at the download location? I am the original author of this package and I will proxy maintain it. The reason for the "xerox-drivers" name is because the 2008 version untarred as something that wasn't descriptive enough to know that it was associated to xerox printers. So I chose the xerox-drivers name for the ebuild. It covers multiple printers (probably all of the xerox printers that have PPD support).
I can verify that the updated ebuild I am attaching actually works because I still have a xerox laser printer I use on a regular basis at home.
I am volunteering to proxy maintain this package so it can remain in the tree.
The newest version of the package has a slightly more sane name of "XeroxPrinterPkgXPXX" although I think there's probably no need to change the name at this point.
In addition, Xerox is not well organized in how they package their files. It appears the reason why the 2008 package broke is that they renamed the original tarball they were providing for all the printers and provide a slightly newer 2008 version. It's not necessary as the 2011 version provides everything the newer 2008 version had plus more printer support. In fact, I looked at the Workcenter 5225 link that Eric provided and it still points to that 2008 version despite having a newer 2011 tarball available that also supports that printer (has the same files as the 2008 version plus more which ostensibly supports newer printers)
I digress. The newest version(s) (XeroxPrinterPkgXPXX_2011_09_30.tgz and PrinterPkgXPXX_2008_03_13.tgz) appear to drop support that existed in the oldest version (LinuxCupsPrinterPkg.tar.gz). I suggest we keep the oldest version in the tree and add the 2011 version which appears to be a superset of the 2008_03_13 version.
I also suggest that the fetch restriction be removed on the 2008 version in the tree. The package I originally built did not have that restriction and I see no reason why it has to be there.
The .so files provided in the 2011 version are only necessary if you want to use Xerox's Centerware software to manage the printer. It's unclear to me why you would even need that software when the PPD files should suffice. Perhaps it might be used for things like checking ink/toner level on printers which don't have built-in print servers that already provide the same functionality. The support could be added if necessary in a future ebuild.
Created attachment 512720 [details]
Addressed some minor QA issues.
Created attachment 512722 [details]
I updated the license. Just to note, the license does not mention that the package cannot be downloaded by the ebuild. It just says you have to accept the license to download it and no restrictions are placed on their server to download either (like cookies) and it doesn't say you can't mirror it either so I have not included the RESTRICT variable as a result in this ebuild.
Created attachment 512724 [details]
I missed the part about distribute in the license, so I've added a mirror restriction. I still don't see a reason why a fetch restriction should be in place since the ACCEPT_LICENSE="*" should suffice.
CCing proxy maintainers then
It seems Xerox has a separate set of drivers:
These are dated Jan 1, 2018, so they're current. The same download can be found for a bunch of other newer printers, but with different dates.
These ones match the printers I'm trying to use, but they aren't at all the same. The ppds define a cupsFilter that sends everything to XeroxQScript, so you have to install /usr/libexec/cups/filters/XeroxQScript, which then calls a bunch of stuff in /opt/Xerox/... All of this is in the new package. Unfortunately, when I try to install and use it, everything appears to work, but nothing prints. What works fine is to remove the cupsFilter lines from the supplied ppd files and ignore the rest of their print driver mess.
I think the new drivers are for new printers, and the old drivers are for old printers, so it probably makes sense to look at this as two separate driver ebuilds. This also explains why Xerox hasn't updated the old drivers since 2011, but doesn't invalidate them.
Removed from the tree