On 23.03.2010 21:21, Jonathan Wiltshire wrote:
Hi, Do you have any indication of when this bug will be closed? It's currently holding up the (proper) fixes for several bugs key to the Python 2.6 transition, that we want to get over and done as soon as possible. We can make ugly patches, but fixing this bug would reduce the work needed to merely binNMUing the affected packages, if I have understood it correctly.
it is fixed upstream in automake 1.11 (and in Debian), so you could use this version; I doubt that it will allow more binNMUs, as autoconf isn't called during the build for many packages.
Matthias