[MacPorts] #26264: gv: pdf display not operational: error /undefined in copy_trailer_attrs

MacPorts noreply at macports.org
Wed Jan 25 15:56:06 PST 2012


#26264: gv: pdf display not operational: error /undefined in copy_trailer_attrs
---------------------------------------+------------------------------------
 Reporter:  veedeehjay@…               |       Owner:  takanori@…           
     Type:  defect                     |      Status:  new                  
 Priority:  Normal                     |   Milestone:                       
Component:  ports                      |     Version:  1.9.1                
 Keywords:                             |        Port:  ghostscript, gv      
---------------------------------------+------------------------------------

Comment(by ryandesign@…):

 I found a response the reporter sent by email in August 2010:

 >> The file /opt/local/share/ghostscript/8.71/lib/pdf2dsc.ps  is part of
 the
 >> port ghostscript, not part of the port gv.
 >
 > right. I did not not recall my old mails. of course this is actually a
 ghostscript issue.
 > sorry for that.
 >
 >> What do you mean "the bug is principally known"? Known by whom? Is
 there
 >> an upstream bug report? If so where? Where did this patch come from? Is
 >
 > at the time I found the solution in red hat's bugzilla: [[br]]
 > https://bugzilla.redhat.com/attachment.cgi?id=395186&action=edit [[br]]
 > [[br]]
 > and here is another reference to the problem: [[br]]
 > http://savannah.gnu.org/bugs/?29023 [[br]]
 > [[br]]
 > here, too: [[br]]
 >
 http://groups.google.de/group/comp.lang.postscript/browse_thread/thread/24ade6df75ea896a/5f30f3545e657584?lnk=raot
 [[br]]
 > [[br]]
 > if I recall correctly back in May I also found some remarks that it
 indeed had been reported upstream.
 > right now I cannot locate these remarks again.
 >
 >> this an upstream fix? If you invented this patch yourself, have you
 >> already reported it to the developers of ghostscript?
 >
 > no since I presumed that had already happened (it seemed that the
 problem had already been noted
 > month ago in several linux distros). but maybe this is not correct...

-- 
Ticket URL: <https://trac.macports.org/ticket/26264#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list