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,
* Michael Banck mba...@debian.org, 2010-05-06, 22:58:
The attached patch should do the trick.
Ah, great! I'll wait for the buildd results to trickle in and will then
upload -2.
Thanks.
I could not test the resulting binary package, however, as it depended
on python2.5-sip4 (which does not
On Thu, May 06, 2010 at 11:10:04PM +0200, Jakub Wilk wrote:
* Michael Banck mba...@debian.org, 2010-05-06, 22:58:
The attached patch should do the trick.
Ah, great! I'll wait for the buildd results to trickle in and will then
upload -2.
Thanks.
I could not test the resulting binary
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
tags 577439 + patch
thanks
* 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.
Package: python-avogadro
Version: 1.0.0-3
Severity: grave
Justification: renders package unusable (on mips)
Hello,
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
6 matches
Mail list logo
