Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Customer description:
We are see a regression bug between sip6-6.5.1 and sip6-6.6.2. Basically code like this no longer works and results in a compilation error while doing the sip-build.
31 │ %Exception mylib::Exception(SIP_Exception) /PyName=mylibException/ {
32 │ %TypeHeaderCode
33 │ #include <Exception.h>
34 │ %End
35 │ %RaiseCode
36 │ const char *detail = sipExceptionRef.what();
37 │ if (mylib::TimeoutException *te = dynamic_cast<mylib::TimeoutException *>(&sipExceptionRef)) {
38 │ SIP_BLOCK_THREADS
39 │ PyErr_SetString(sipException_mylib_TimeoutException, detail);
40 │ SIP_UNBLOCK_THREADS
41 │ }
42 │ else if (mylib::MetadataException *me = dynamic_cast<mylib::MetadataException *>(&sipExceptionRef)) {
43 │ SIP_BLOCK_THREADS
44 │ PyErr_SetString(sipException_mylib_MetadataException, detail);
45 │ SIP_UNBLOCK_THREADS
46 │ }
47 │ else {
48 │ SIP_BLOCK_THREADS
49 │ PyErr_SetString(sipException_mylib_Exception, detail);
50 │ SIP_UNBLOCK_THREADS
51 │ }
52 │ %End
53 │
54 │ }; // Exception
55 │
56 │ %Exception mylib::TimeoutException(mylib::Exception) /PyName=mylibTimeoutException/ {
57 │ %TypeHeaderCode
58 │ #include <Exception.h>
59 │ %End
60 │ %RaiseCode
61 │ const char *detail = sipExceptionRef.what();
62 │ SIP_BLOCK_THREADS
63 │ PyErr_SetString(sipException_mylib_TimeoutException, detail);
64 │ SIP_UNBLOCK_THREADS
65 │ %End
66 │ }; // TimeoutException
The bug has already been fixed by the upstream project in the 6.6 branch with this commit.
https://www.riverbankcomputing.com/hg/sip/rev/1430b279a3c9
Define the value or impact to you or the business
This bug was impeding our progress towards moving to el9 since it was breaking builds of internal software. As a short term stop gap we can downgrade to sip6-6.5.1 on our build machine. But that is not a tenable long term solution.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (sip6 bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:6521
Customer description: We are see a regression bug between sip6-6.5.1 and sip6-6.6.2. Basically code like this no longer works and results in a compilation error while doing the sip-build. 31 │ %Exception mylib::Exception(SIP_Exception) /PyName=mylibException/ { 32 │ %TypeHeaderCode 33 │ #include <Exception.h> 34 │ %End 35 │ %RaiseCode 36 │ const char *detail = sipExceptionRef.what(); 37 │ if (mylib::TimeoutException *te = dynamic_cast<mylib::TimeoutException *>(&sipExceptionRef)) { 38 │ SIP_BLOCK_THREADS 39 │ PyErr_SetString(sipException_mylib_TimeoutException, detail); 40 │ SIP_UNBLOCK_THREADS 41 │ } 42 │ else if (mylib::MetadataException *me = dynamic_cast<mylib::MetadataException *>(&sipExceptionRef)) { 43 │ SIP_BLOCK_THREADS 44 │ PyErr_SetString(sipException_mylib_MetadataException, detail); 45 │ SIP_UNBLOCK_THREADS 46 │ } 47 │ else { 48 │ SIP_BLOCK_THREADS 49 │ PyErr_SetString(sipException_mylib_Exception, detail); 50 │ SIP_UNBLOCK_THREADS 51 │ } 52 │ %End 53 │ 54 │ }; // Exception 55 │ 56 │ %Exception mylib::TimeoutException(mylib::Exception) /PyName=mylibTimeoutException/ { 57 │ %TypeHeaderCode 58 │ #include <Exception.h> 59 │ %End 60 │ %RaiseCode 61 │ const char *detail = sipExceptionRef.what(); 62 │ SIP_BLOCK_THREADS 63 │ PyErr_SetString(sipException_mylib_TimeoutException, detail); 64 │ SIP_UNBLOCK_THREADS 65 │ %End 66 │ }; // TimeoutException The bug has already been fixed by the upstream project in the 6.6 branch with this commit. https://www.riverbankcomputing.com/hg/sip/rev/1430b279a3c9 Define the value or impact to you or the business This bug was impeding our progress towards moving to el9 since it was breaking builds of internal software. As a short term stop gap we can downgrade to sip6-6.5.1 on our build machine. But that is not a tenable long term solution.