[Bug 216257] security/py-m2crypt: swig is not used and py-typing seems needed

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216257

            Bug ID: 216257
           Summary: security/py-m2crypt: swig is not used and py-typing
                    seems needed
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: luca.pizzamiglio at gmail.com
 Attachment #179068 maintainer-approval?
             Flags:
             Flags: maintainer-feedback?

Created attachment 179068
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179068&action=edit
The proposed patch

I discovered the problem using openssl without SSLv3 support.

If swig is not used, the wrapper's C code is not recreated, but the provided
one (generated by the developer) is used to build the _m2crypto.so, that
includes the SSLv3_method() function.
At compile time, only a couple of warning about automatic function definition
(the SSLv3_method()) are shown; the error is fatal at run-time, python is not
able to solve the symbol and crash loading the m2crypto module.

the setup.py has an extra function (swig_version, outside build_ext) that spawn
a "swig -version" to check if swig is new enough, but it should spawn swig3.0,
on FreeBSD.

Moreover, it looks like that to use M2Crypto with python >= 2.7, the py-typing
module is need.
As example, the util.py imports the typing module.

The attached patch fix both problems:
- patch the setup.py to call swig3.0 instead of swig
- add py-typing as run-time dependency

portlint is still happy ad poudriere as well.

-- 
You are receiving this mail because:
You are the assignee for the bug.