Hello, Am Samstag, 2. November 2019, 16:20:10 CET schrieb intrig...@debian.org: > As discovered on #942663, src:apparmor fails to build for python 3.8. ... > - upstream Git: libraries/libapparmor/m4/ac_python_devel.m4 > > - upstream tarball: libraries/libapparmor/configure
This is part of the libapparmor bindings which are generated with swig, which I'm not really familiar with. However, there's an interesting detail on http://www.swig.org/Release/RELEASENOTES for swig 4.0.1 (which is the latest release): - Add Python 3.8 support. Which swig version gets used in the failing builds? If it's older than 4.0.1, then updating swig is probably the first thing to do/test ;-) Note that this is just a wild guess ;-) Regards, Christian Boltz -- seccheck runs here on a host that contains 3 daily backups of 10+ SAP hosts, and the "Local Monthly Security" Mail size is 562 MB. This mail size causes an unfriednly, suspicious grin on the face of my mail admin... [Werner Flamme in opensuse-security]
signature.asc
Description: This is a digitally signed message part.