mailman 1:2.1.15-1 FTBFS on amd64 in raring

[Robie Basak]

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

[Robie Basak (racb)]

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?

[Robie Basak (racb)]

@Mark Sapiro

This also affects the upstream Mailman project, since the pristine upstream tarball also will also fail to build on Ubuntu after the next release. What's the reason you removed the bug task?

[Mark Sapiro (msapiro)]

I looked too quickly the first time and thought it was strictly a Debian/Ubuntu packaging issue and didn't look closely at your comment #1

[Robie Basak (racb)]

No problem. Thanks for the quick fix!

[Launchpad Janitor (janitor)]

This bug was fixed in the package mailman - 1:2.1.15-1ubuntu1

---------------
mailman (1:2.1.15-1ubuntu1) raring; urgency=low

  * Fix FTBFS: correct expected Python.h location in configure script
    (LP: #1098162).
    - d/control: add build dependency on dh-autoreconf
    - d/rules: use dh_autoreconf and dh_autoreconf_clean
    - d/patches/80_python_h_location.patch: patch configure.in
 -- Robie Basak <email address hidden> Thu, 10 Jan 2013 12:10:20 +0000