Sorry missed this for a day or two or three ...
On 1 November 2025 at 16:07, Santiago Vila wrote: | On Sat, Nov 01, 2025 at 09:36:23AM -0500, Dirk Eddelbuettel wrote: | | > This is apparently caused by SWIG 4.4.0 which is newer than the one used to | > generated these bindings here, but upstream (CC'ed) kindly gave me a | > (trivial) two-line (net) patch rolling the minimum version format which I | > folded the usual way via a file in debian/patches/ | > | > New version coming up shortly closing this too. | | I infer, then, that any package with a similar mode of failure is | suitable to be fixed in the package itself. | | (I'm often in doubt if some bugs are bugs in the packages that need to | be fixed, or a bug in one of the build-depends, and reassigns are | required, so I rely on the good will of maintainers to tell me). I would concur. [ But I am really not much of a Python programmer. ] The error your (autogenerated ?) bug report showed was suggestive of an API evolution and the spot-on-yet-very-simple patch that Luigi helped us with does nothing more than ... rolling the minimum Python forward to a version already way too ancient for Debian testing/unstable. So methinks you can automate this with suitable Python defaults. | Thanks a lot. Anytime. Cheers, Dirk -- dirk.eddelbuettel.com | @eddelbuettel | [email protected]
