https://bugzilla.suse.com/show_bug.cgi?id=1219600 https://bugzilla.suse.com/show_bug.cgi?id=1219600#c3 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to William Brown from comment #2)

Thanks for fixing those - however I think we should learn from this situation as a whole. We had a package (rpm) that was making a change that would break a list of packages that were identified by dimstar. However, the package was still released without all of those breakages being resolved.

Is there a way we could have done this better?

The guarantee is on TW not to break the ring packages. Non-ring have always been reactive (often fail with gcc/binutils updates too) There was communication ahead of time that RPM will have this requirement - and not a single maintainer felt the need to check their package (except all the ones in ring1, which were identified as part of the staging process) If it were not for glibc/pyton312 coming so close to RPM 4.19, there would likely not have been a full rebuild of TW - which would have made this even trickier as errors would have popped up at random times. So, from that PoV, I think it's even better the way it is. The bug in its form is of no help as 'multiple issues reported in one bug' is not workable (bug cannot be moved to the right assignee) -- You are receiving this mail because: You are on the CC list for the bug.