Bug#953437: Flint problem reported upstream

Julien Puydt julien.puydt at gmail.com
Sat May 9 14:49:34 BST 2020


Le samedi 09 mai 2020 à 09:19 -0300, David Bremner a écrit :
> Julien Puydt <julien.puydt at gmail.com> writes:
> 
> > Well, that will be something to check when we'll have a fixed
> > package
> > (be it with a patch or a new upstream version).
> > 
> > And if it doesn't fix everything, that will be something to
> > investigate.
> 
> Sure, I don't want to discourage people from fixing bugs. On the
> other
> hand, it's only fair to note that the set of people that actually 
> run polymake on mipsel is probably pretty small. So from my point of
> view a small performance / feature loss on an architecture nobody
> uses
> (for this task) is acceptable.
> 

My point of view is that code running well on some architectures and
not on others has a hidden defect ready to rear its ugly head at the
worst possible moment, everywhere at once.

But I'm a mathematician, so my expectations of perfection might
sometimes be hard to reach :-P

Cheers,

JP



More information about the debian-science-maintainers mailing list