m2crypto: testsuite fails with openssl 3.4
Bug #2091358 reported by
Adrien Nader
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| m2crypto (Ubuntu) |
Fix Released
|
High
|
Adrien Nader | ||
Bug Description
Openssl 3.4 has started returning an error for when calling X509_REQ_
Related branches
~adrien/ubuntu/+source/m2crypto:plucky-erroneous-x509-version-test
- git-ubuntu import: Pending requested
-
Diff: 174 lines (+129/-1)6 files modifieddebian/changelog (+11/-0)
debian/control (+2/-1)
debian/patches/openssl-3.4-ftbfs.patch (+31/-0)
debian/patches/series (+6/-0)
debian/patches/testsuite-compatibility-with-openssl-3.4-1.patch (+38/-0)
debian/patches/testsuite-compatibility-with-openssl-3.4-2.patch (+41/-0)
| description: | updated |
| summary: |
- Testsuite fails with openssl 3.4 + m2crypto: testsuite fails with openssl 3.4 |
| tags: | added: update-excuse |
To post a comment you must log in.

This bug was fixed in the package m2crypto - 0.42.0-2ubuntu2
---------------
m2crypto (0.42.0-2ubuntu2) plucky; urgency=medium
* d/p/openssl- 3.4-ftbfs. patch: swig-4. 3-changed- exception. patch:
Remove as this was leading to a whack-a-mole game trying to have
SWIG parse properly all system headers
* d/p/ftbfs-
Adapt to SWIG 4.3 changing exception raised in some situations
(LP: #2092223)
-- Adrien Nader <email address hidden> Thu, 19 Dec 2024 18:47:30 +0100