Summary: | psutils-1.17: psnup, pstops, psresize created postscript files don't print duplex | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Horst Prote <prote> |
Component: | Current packages | Assignee: | Text-Markup Team (OBSOLETE) <text-markup+disabled> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | matteo-ml |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
psutils duplex printing patch
psutils ebuild file that installs the above patch psutils ebuild file that installs the above patch |
Description
Horst Prote
2005-03-30 05:17:28 UTC
Googling a bit I finally found this post in the fptex mailing list: http://www.tug.org/pipermail/fptex/2004-March/001551.html where the poster suggests to remove the lines "/setpagedevice {pop}bind 1 index where{dup wcheck{3 1 roll put}", " {pop def}ifelse}{def}ifelse", from psspec.c and rebuild the psutils. I just succesfully tried this myself. I'll attach the patch and my new ebuild file. Created attachment 54832 [details, diff]
psutils duplex printing patch
Created attachment 54833 [details]
psutils ebuild file that installs the above patch
Created attachment 54834 [details]
psutils ebuild file that installs the above patch
For me the bug is fixed. But since I don't realy know what the two deleted lines of postscript code do/mean I can't assure that the patch doesn't implement another bug. Maybe some postscript expert can check this or should we ask/inform the auhtor of the psutils package? Forgot to change resolution to WORKSFORME. Reason see my previous comment. Is it okay this bug is closed WORKSFORME? If the patch hasn't been committed to portage, I think it should have been left open... You're right. I should have read the explanation for the "Resolution" Field. I'm now quite convinced that this is no bug. At least not a bug of psutils. I can't say if a new cups or something else made the problem disappear, but it's gone. So I closed this bug as INVALID. |