Bug#950608: gmp 6.2.0 crashes postgresql-pgmp (& others)

John Scott jscott at posteo.net
Sun Feb 23 20:32:49 GMT 2020


On February 23, 2020 3:11:46 PM EST, Marco Bodrato <bodrato at mail.dm.unipi.it> wrote:
>Ciao,
>
>Il Dom, 9 Febbraio 2020 9:34 pm, Steven Robbins ha scritto:
>> On Sunday, February 9, 2020 9:54:02 A.M. CST Marco Bodrato wrote:
>>> So, if the new release of the library is able to answer that the number
>>> 3878888047 is prime, and not only "probably" prime... This should not be
>>> marked as a regression...
>>
>> Indeed!  Thanks for investigating.  An improvement could be simply that
>
>> Is there a bug for libmath-gmp-perl for this test suite issue?
>
>It seems to me that all packages incorrectly using the internal
>representation and not the documented interface of GMP where patched.
>
>What else stops migration of GMP to testing? Maybe a release of GMP
>explicitly saying that it breaks:
> libmath-gmp-perl < 2.20
> libmath-prime-util-gmp-perl < 0.51-2
> postgresql-pgmp < 1.0.4
>is needed? So that nobody will update the library without updating also
>the other possibly failing packages?
>
>Ĝis,
>m
>

GMP is not migrating because this bug was marked as done by uploading postgresql-pgmp. However, this bug is filed against GMP, so the bug metadata still suggests that GMP 6.2.0 introduces this serious issue.



More information about the debian-science-maintainers mailing list