On 10/30/2014 03:02 PM, Sebastian Ramacher wrote:
> Source: python-gmpy2
> Version: 2.0.4-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> python-gmpy2 failed to build on i386, armel, armhf, mips, mipsel,
> kfreebsd-i386 and powerpc:
> | File "test/test_mpz_io.txt", line 71, in test_mpz_io.txt
> | Failed example:
> | mpz(D("1e10"))
> | Expected:
> | mpz(10000000000)
> | Got:
> | mpz(10000000000L)
> | **********************************************************************
> | 1 items had failures:
> | 1 of 68 in test_mpz_io.txt
> | ***Test Failed*** 1 failures.
> | Results for: test_mpz_io Attempted: 68 Failed: 1
> | Results for: test_mpz_pack_unpack Attempted: 16 Failed: 0
> | Results for: test_mpz_to_from_binary Attempted: 6 Failed: 0
> |
> | Summary - Attempted: 964 Failed: 3
> | make: *** [test-python2.7] Error 1
> | debian/rules:45: recipe for target 'test-python2.7' failed
>
> For a full build log, see
> https://buildd.debian.org/status/fetch.php?pkg=python-gmpy2&arch=i386&ver=2.0.4-1&stamp=1414367107.
>
> Cheers
>
Thanks; it looks like it failed in the exact same way for all the 32-bit
architectures. This is the first time that the build is contingent on
the unit tests passing, and it appears we found a bug that upstream
didn't know about! Looks like we just need to change int to uint64 or
something similar. I should be able to patch it soon; we can put the
patch into our builds and then send it upstream.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
