On Fri, 2017-06-09 at 16:14 -0500, Chris Caudle wrote: > Not sure which list is most appropriate, but starting with test to see if > this is something which would be expected to be caught while a package was > in updates-testing: This update was kind of a special case, as it was required to fix a blocker bug in F26 (under certain circumstances, an update to F24 / F25 can be required to clear a 'blocker' condition for F26). The update has been undergoing testing by folks on the relevant bug reports all week, but it seems like it never actually made it to updates-testing even though someone tried to push it early last week (possibly a Bodhi issue), so it more or less went straight to stable without really hitting u-t. Unfortunately it does seem to still have some issues with certain package updates causing RPM db issues :/ Fortunately rpm --rebuilddb does seem to clear it, so it's recoverable, but this is definitely turning into a real mess. Sorry about that. I've sent a -22 to u-t which reverts the offending changes (again), and posted a PSA to my blog and G+ about the potential DB corruption; if folks could help spread that around it'd be great. Relevant bugs are: https://bugzilla.redhat.com/show_bug.cgi?id=1394862 https://bugzilla.redhat.com/show_bug.cgi?id=1397087 https://bugzilla.redhat.com/show_bug.cgi?id=1460303 -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
