severity 577439 important thanks On Sun, Apr 11, 2010 at 06:02:46PM +0200, Jakub Wilk wrote: > Package: python-avogadro > Version: 1.0.0-3 > Severity: grave > Justification: renders package unusable (on mips)
Well, it's not unusable on mips, it's just unusable on architectures with unclean buildd chroots. > 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. Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
