On Wed, 9 Feb 2022 17:12:27 -0500 Michael Stone <mst...@debian.org> wrote: > On Wed, Feb 09, 2022 at 04:32:43PM -0500, Scott Kitterman wrote: > >On Sat, 5 Feb 2022 17:28:04 -0500 Michael Stone <mst...@debian.org> wrote: > >> It seems to be some kind of incompatibility in swig. Upstream .cc files > >> are built with swig 3, debian has swig 4. If the package is built with > >> the upstream .cc files (ditching the associated lines in debian/rules) > >> it seems to work fine. > > > >Thanks. I agree. The bad news is that would trade a DFSG issue for a > >technical issue, which might be considered progress (since the generated files > >can't be regenerated within Main anymore). > > I'd argue that's the least-bad option right now for a fix in bullseye. > It's IMO a DFSG-pedantic issue as the files can be regenerated with free > software, just not with anything currently packaged in debian (e.g., > with the buster version of swig). Would definitely be better than a > completely unusable package. (A change to the .i that makes everything > work would be even better obviously, but I have no idea how swig is > supposed to work.)
I have it figured out. I'll upload shortly for Unstable and then work on fixing the stable version. If you want to build a local copy that works, delete all the mv's in debian/rules and rebuild. The way that's structured is what caused the problem. Scott K
signature.asc
Description: This is a digitally signed message part.
