Based on the distutils documentation, I think that calling distutils.sysconfig.get_python_inc() is a more appropriate way of determining the location of Python.h. It seems to work both after and before the transition that broke Raring. Is this appropriate for upstream as well?
** Patch added: "mailman.debdiff" https://bugs.launchpad.net/mailman/+bug/1098162/+attachment/3479074/+files/mailman.debdiff ** Description changed: mailman's configure script assumes that Python.h is present in distutils.sysconfig.get_config_var('CONFINCLUDEPY') which is arch- specific and not where it is in raring. + + https://launchpadlibrarian.net/126517790/buildlog_ubuntu-raring- + amd64.mailman_1%3A2.1.15-1_FAILEDTOBUILD.txt.gz -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman in Ubuntu. https://bugs.launchpad.net/bugs/1098162 Title: mailman 1:2.1.15-1 FTBFS on amd64 in raring To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1098162/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
