Hi Ioana and Ioanna,

This was discussed during the SRU Team meeting today.

The current evaluation of this bug still matches Nick's opinions from back in 
August, which is, the user story or impact statement simply does not match our
expectations for what would be acceptable for a glibc SRU.

glibc is special as it underpins nearly every other package in the Ubuntu
archive, and in this case, the risk of regression to our users and to the
archive itself is just too high, compared to the benefits of making the change.

You can read more about how we evaluate risk and benefits in the SRU Team
documentation:

https://documentation.ubuntu.com/project/SRU/explanation/principles/
https://documentation.ubuntu.com/project/SRU/explanation/requirements/

This only affects static compilation on i386, which is not widely used, it
doesn't directly affect any package in the Ubuntu archive, and there would be
very few users who will ever experience this problem.

There is an upgrade path available, as this is fixed in questing and resolute,
and easily worked around, as you could simply patch what you are building with
your own implementation of fmod().

I am going to mark this as "Won't fix" for noble.

This also isn't a hard "no". If you can explain a user story or a proper
impact statement that shows us how this is used, why this could be of benefit to
a wide variety of users, and why the current behaviour is bad, then we are open
to re-evaluating in the future.

Additional comments:
- In the testcase, it would be good to check the result of fmod() to make sure
it actually computes the correct result on i386, and not just that the symbol
is available.

Thanks,
Matthew

** Changed in: glibc (Ubuntu Noble)
       Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2036283

Title:
  i386 glibc is missing fmod in libm.a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2036283/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to