FEDORA-2017-816792354b created by adamwill 4 years ago for Fedora 26
unpushed

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.

This update has been submitted for testing by adamwill.

4 years ago

This update has been pushed to testing.

4 years ago
User Icon cserpentis commented & provided feedback 4 years ago
karma

works for me

User Icon besser82 commented & provided feedback 4 years ago
karma

Works great! LGTM! =)

User Icon alciregi commented & provided feedback 4 years ago
karma

After installing this update

dnf search easy-karma
error: db5 error(2) from dbenv->open: No such file or directory
error: cannot open Packages index using db5 - No such file or directory (2)
error: cannot open Packages database in /var/lib/rpm
Error: Error: rpmdb open failed

But after issuing

rm -f /var/lib/rpm/__db*
rpm --rebuilddb

all seems to work as expected.

Please note that pushing this update will force everyone already on -21 to rebuild their libdb environments regardless of whether they did or did not encounter the segfault when applying the fixes as opposed to forcing only those people that are affected by the bug to rebuild...

User Icon g6avk commented & provided feedback 4 years ago
karma

I was on the -21 build and had no issues. However as mentioned I also had to rebuild the db after this update. Then all works as it should.

Man, this is a pickle. But I think we'll have 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:

  • -17 and lower: no fix for upgrade issue
  • -18 and -19: original version of the upgrade fix which caused lots of people to see RPM db corruption
  • -20 (Rawhide only): fix reverted, same as -17
  • -21: improved version of the upgrade fix which caused some people to see RPM db corruption
  • -22: fix reverted again, same as -17

We may send out a -23 with the fixes re-applied (so effectively the same as -21) to Rawhide and F26.

This update has been unpushed.


Please login to add feedback.

Metadata
Type
bugfix
Severity
high
Karma
4
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
4 years ago
in testing
4 years ago

Automated Test Results