@justin-demaris: Yes, sort of. What happened is that the first update caused a regression, and the second update reverted that. Any services that were restarted with the broken update would then have been "re- broken" with the update that backed out that change until they were again re-started. The good news is that people with less aggressive update schedules probably skipped the bug entirely (as upgrading from an older libc to the current one won't break), but that's scant comfort for those who came along for the ride.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674532 Title: glibc update caused NSS ABI break To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
