@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 Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1674532 Title: glibc update caused NSS ABI break Status in eglibc package in Ubuntu: Invalid Status in glibc package in Ubuntu: Fix Committed Status in eglibc source package in Precise: Fix Released Status in glibc source package in Precise: Invalid Status in eglibc source package in Trusty: Fix Released Status in glibc source package in Trusty: Invalid Status in eglibc source package in Xenial: Invalid Status in glibc source package in Xenial: Fix Released Status in eglibc source package in Yakkety: Invalid Status in glibc source package in Yakkety: Invalid Bug description: After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during the automated install of ubuntu 14.04.5, the system was suddenly unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved the issue. Reinstalling -ubuntu6.10 broke the system again. I note that -ubuntu6.10 was recently added to the archive. I am currently unable to install Ubuntu 14.04.5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
