Comment 39 for bug 1674532

@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.