Public bug reported: While trying to rebuild src:subversion against Ruby 2.7 I figured out it actually FTBFS due to the swig update to version 4. This is a known upstream bug [1], and the fix was not released yet. This is part of the build log (focal-proposed needs to be enabled to reproduce it):
... Wrote subversion/bindings/swig/proxy/swig_python_external_runtime.swg /usr/bin/swig -I/<<PKGBUILDDIR>>/BUILD/subversion -I/<<PKGBUILDDIR>>/subversion/include -I/<<PKGBUILDDIR>>/subversion/bindings/swig -I/<<PKGBUILDDIR>>/subversion/bindings/swig/include -I/<<PKGBUILDDIR>>/subversion/bindings/swig/proxy -I/<<PKGBUILDDIR>>/BUILD/subversion/bindings/swig/proxy -I/usr/include/apr-1.0 -I/usr/include/apr-1.0 -I/usr/include -python -classic -o subversion/bindings/swig/python/core.c /<<PKGBUILDDIR>>/subversion/bindings/swig/core.i Deprecated command line option: -classic. This option is no longer supported. make[1]: *** [/<<PKGBUILDDIR>>/build-outputs.mk:290: subversion/bindings/swig/python/core.c] Error 1 make[1]: Leaving directory '/<<PKGBUILDDIR>>/BUILD' make: *** [debian/rules:228: debian/stamp-build-arch] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 After a discussion with doko on #ubuntu-devel we brought up with 2 options: 1) Drop the needed bindings. We'd need to take care with the reverse dependencies if we take this route. 2) Maintain a swig 3 source package to support those bindings. I'd go for the first option, IMO it'd make the future maintenance easier. [1] https://issues.apache.org/jira/browse/SVN-4818 ** Affects: subversion (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866208 Title: FTBFS against SWIG 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1866208/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
