This update reverts the attempt to fix bug #1394862 / bug #1397087 from
libdb-5.3.28-21. Multiple reports indicate the attempted fix can still cause RPM database corruption in some cases, so we are backing out the fix to try and prevent any more people hitting that problem.
If you have already encountered RPM database issues after updating to -21, please run:
rm -f /var/lib/rpm/__db* rpm --rebuilddb
as root. We apologize for the inconvenience.
Please login to add feedback.
This update has been submitted for testing by adamwill.
This update has been pushed to testing.
updated from -14 (or something like that), tested dnf and gnome-software operations, seems to work without issues
Well, was not on (-21), but no problems with (-22) here.
works fine for me in a VM
So, reports indicate that updating from -21 to -22 will almost inevitably cause (recoverable) db corruption. Based on that, we're going to go with unpushing the -22 updates and writing a common bugs entry and maybe a blog post to tell people to rebuild the database for any problems. Sorry about all this to-ing and fro-ing, everyone. If you're on -22, I'd suggest downgrading to -21, but there shouldn't be any awful consequences to staying on -21. For clarity, here's what's actually in every version of the package:
We will send out a -23 with the fixes re-applied and another fix for a somewhat related issue included shortly. Updating to that may possibly cause corruption again, we are sorry about this. Recovery will work just the same.
This update has been unpushed.