I am reviewing this upload in noble unapproved, and I am skeptical that
the impact here is severe enough to justify an SRU of glibc, especially
in an LTS.
1. It does not appear this is affecting any packages in Ubuntu
2. i386 is a partial architecture on Ubuntu. Where *exactly* is this happening?
A CI/CD system was mentioned in comment #8, but I see no further reference
3. Static linking against libma.a on i386 sounds like a very specific or niche
thing to do
Hence, the impact here does not seem severe or widespread enough to
justify this SRU. Am I missing something? If so, please elaborate on the
impact and why an SRU is necessary.
Beyond that (in case this *does* move forward), the test plan does not
actually test any static compilation. While checking for these symbols
does make sense as a test, if the *impact* here is about static
compilation, that should also be exercised in the test plan.
** Changed in: glibc (Ubuntu Noble)
Status: In Progress => Incomplete
--
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
