It seems to fix a bug we encountered in fedmsg: https://github.com/fedora-infra/fedmsg/pull/389
Looking at 0.26 setup.py, m2crypto 0.26.0 seems to simply refuses to build with any OpenSSL > 1.0.1. Matěj, should I just take the openssl-1.1.0 branch and carry it in the RPM? Do you think it is ready enough?
(In reply to Miloslav Trmač from comment #1) > Looking at 0.26 setup.py, m2crypto 0.26.0 seems to simply refuses to build > with any OpenSSL > 1.0.1. > > Matěj, should I just take the openssl-1.1.0 branch and carry it in the RPM? > Do you think it is ready enough? No, it is not, I don’t think you can merge it at all. OK, I take as a TODO task to move that branch to the highest priority.
(In reply to Miloslav Trmač from comment #1) > Looking at 0.26 setup.py, m2crypto 0.26.0 seems to simply refuses to build > with any OpenSSL > 1.0.1. > > Matěj, should I just take the openssl-1.1.0 branch and carry it in the RPM? > Do you think it is ready enough? See https://gitlab.com/m2crypto/m2crypto/merge_requests/98#note_26993076 and disastrous results of https://gitlab.com/mcepl/m2crypto/pipelines/7490115
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
M2Crypto 0.26.2 was released today which adds port to OpenSSL 1.1.0 (while still maintaining compatibility all the way down to RHEL-6). Available at normal places (https://pypi.python.org/pypi/M2Crypto/).
m2crypto-0.26.2-1.fc28 built in rawhide (only). Thanks, Matěj!