ports/153506: ports/net-im/papyon (py26-papyon-0.5.4) gets Signal 11

[David E. Cross]

The following reply was made to PR ports/153506; it has been noted by GNATS.

From: "David E. Cross" <crossd at cs.rpi.edu>
To: Maho NAKATA <chat95 at mac.com>
Cc: bug-followup at FreeBSD.org
Subject: Re: ports/153506: ports/net-im/papyon (py26-papyon-0.5.4) gets Signal
 11
Date: Fri, 28 Jan 2011 19:18:53 -0500 (EST)

 To be fair, it really isn't papyon's fault, its just tickling it when 
 installed (and likely other things will as well, depending on what 
 features they use).
 
 The real issue seems to be openssl in base and openssl in ports with 
 python compiled when just the version in base exists, and even then only 
 later when other python modules are installed after the openssl port is 
 installed.
 
 -- 
 David E. Cross
 
 On Sat, 29 Jan 2011, Maho NAKATA wrote:
 
 > Hi gnome team and David,
 > Is it possible to add CONFLICT to papyon port
 > when openssl port is installed?
 >
 > thanks
 > Nakata Maho
 >
 > From: "David E. Cross" <crossd at cs.rpi.edu>
 > Subject: Re: ports/153506: ports/net-im/papyon (py26-papyon-0.5.4) gets Signal 11
 > Date: Fri, 28 Jan 2011 13:49:59 -0500 (EST)
 >
 >> I just stumbled across this on 8.2-RC2, and was able to reproduce
 >> it.. I know the cause (and a fix.. but I don't think the "right" fix).
 >>
 >> The cause is having openssl from ports intsalled *after* pyton is
 >> built, such that python's ssl library is linked against base openssl,
 >> and the py-OpenSSL package (which is a prereq for this one) is linked
 >> against the ports version.
 >>
 >> The fix I did was to recompile python now that openssl was installed
 >> and viola..
 >>
 >> This should be re-opened.. but I am unsure if it belongs to papyon,
 >> python, or py-OpenSSL.
 >>
 >> --
 >> David E. Cross
 >>
 >