Hi, On Wed, May 05, 2010 at 08:36:41PM +0200, Jakub Wilk wrote: > * Michael Banck <mba...@debian.org>, 2010-05-05, 19:16: > >>On mips python-avogadro does not ship modules for Python 2.5 > >>(which is still the default Python version). Apparently, if > >>python2.6-dev happens to be installed in the chroot, only modules for > >>2.6 will be built. Here's an excerpt from the build log: > >> > >>| Package versions: [...] libpython2.6_2.6.4-6 [...] python2.6_2.6.4-6 > >>python2.6-dev_2.6.4-6 python2.6-minimal_2.6.4-6 [...] > >>[...] > >>| -- [2/5] Python Libraries > >>| -- Found PythonLibs: /usr/lib/libpython2.6.so > >>| -- [3/5] Python Interpreter > >>| -- Found PythonInterp: /usr/bin/python2.6 > > > >What do you propose we should do? Hardcoding to look for 2.5 first? > >That would make it break the same way once the default changes and 2.5 > >packages happen to be installed as well. > > The attached patch should do the trick.
Ah, great! I'll wait for the buildd results to trickle in and will then upload -2. > I could not test the resulting binary package, however, as it depended > on python2.5-sip4 (which does not exist). AFAICT, it's a virtual package provided by python-sip4. If you can't install it (I can on i386), it might be an architecture specific bug or package-relation issue. Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org