Hi there, this is half a question and half a remark. python-PyMuPDF started to FTBFS recently with a weird error message: https://koschei.fedoraproject.org/build/21026539 python-PyMuPDF uses swig generated python bindings from the package mupdf. After staring at the error and koschei's list of changes for a while, knowing that my regular rebuilds in copr showed no such issue, I did the following in mock locally: rebuild and install mupdf (unchanged) rebuild python-PyMuPDF This worked. My current assumption is that that the patch in swig-4.3.1-4.fc43 introduced a change which made a rebuild necessary - i.e. the mupdf bindings built with swig-4.3.1-3 do not work when I use them to build python-PyMuPDF with swig-4.3.1-4. The rebuilt bindings do work. Since my mock changeroot does not want to downgrade swig I cannot test for sure, just wanted to throw it out there in case someone experiences strange effects with call signatures of overloaded functions using swig. Michael -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
