On Fri, Apr 05, 2013 at 15:02:54 -0000, Barry Warsaw wrote:
> To be honest, I don't really have much more time to spend investigating this.
> The workaround fixes the problem and while a bit wasteful, seems harmless
> enough. Since Doko agrees, I think I'll just apply this for now, and maybe we
> can re-investigate this later after Raring is released.
I certainly agree that further investigation can wait until after Raring
is released.
My longer-term concern with masking this at the pycurl level is that if
some library is leaving the floating-point registers in a confused
state, then it seems possible that other applications could be affected
-- perhaps in a way that's a lot more subtle than apt-add-repository's
explicit "cannot convert float NaN to integer" message...
Nathan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063350
Title:
curl corrupts floating point context
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1063350/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
