Build of libcap-ng failed with SWIG 4.2.0 about libcap-ng

[taladar]

Same issue in Gentoo unstable with the same versions of libcap-ng and swig. I have not really found the correct %exception based replacement syntax though.

@jplesnik What did you use to replace that block?

[stevegrubb]

This code was copied over from the audit project. The audit project was modified 5 months ago to pin point the exception to audit_open. Libcap-ng doesn't quite have a function like that. I suppose the except code can be deleted and let exceptions be thrown in the python code. I don't have a good sense of how many projects that might affect. Python is not normally used for daemons or setuid programs. So, maybe there's no risk in deleting the exception handler?

[lucabonnix]

If you want to keep the exception handler, you can simply change "%except(python)" with "%exception" and add a dedicated exception for void functions (otherwise "result" variable is not defined):

--- libcap-ng-0.8.4.old/bindings/src/capng_swig.i       2023-12-20 16:23:01.000000000 +0100
+++ libcap-ng-0.8.4/bindings/src/capng_swig.i   2024-01-04 12:53:12.131746399 +0100
@@ -30,7 +30,16 @@
 
 %varargs(16, signed capability = 0) capng_updatev;
 
-%except(python) {
+%exception capng_clear {
+  $action
+}
+%exception capng_fill {
+  $action
+}
+%exception capng_setpid {
+  $action
+}
+%exception {
   $action
   if (result < 0) {
     PyErr_SetFromErrno(PyExc_OSError);

But with the previous swig version the "%except(python)" was simply ignored, so maybe it is safe to remove it at all.

[stevegrubb]

I think I'll elect to just delete the exception handler. Less to go deprecated.

[stevegrubb]

And a new package pushed into rawhide. I'll go ahead and close this. If anything else comes up, feel free to re-open.