Hi there! You might want some more data regarding the transition risk involved here.
Unless something actually changed in the archive since last time, there's always a small transition involved with libc6: there's a handful of packages that always need rebuilds on version bumps as they hook into internal APIs. I don't have the list here, but it's in the README.Ubuntu doc in the repo, and IIRC those packages aren't seeded (could be wrong). The rebuilds are quick and painless, especially compared to the regression hunting that happens in parallel. However, addition of things like openat2 or mseal sometimes triggers hard-to-detect "transitions": it's the kind of symbol that is ifdef'd into a custom implementation if not provided by the libc. That means any rebuild of affected packages would pick up a libc6 (>= 2.43) dependency. However, contrary to normal transitions, we don't *need* to rebuild affected packages, as it doesn't block the glibc migration. Since we're in FF, chances of that happening while 2.43 is in -proposed are fairly low. IMHO, this FFe should be granted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2143767 Title: [FFE] merge glibc 2.43 in ubuntu resolute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2143767/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
