I'm hitting bug 1394862 with a libdb.x86_64 5.3.28-21.fc26 to libdb.x86_64 5.3.28-22.fc26 update. Why? It has a +4 karma and I'm hitting it the instant the dnf update completes. Should I negative karma the -22 package? Seems obviously broken to me.
[chris@f26h Documents]$ sudo dnf clean all error: db5 error(5) from dbenv->open: Input/output error error: cannot open Packages index using db5 - Input/output error (5) error: cannot open Packages database in /var/lib/rpm Error: Error: rpmdb open failed [chris@f26h Documents]$ rpm -q libdb libdb-5.3.28-22.fc26.x86_64 [chris@f26h Documents]$ sudo dnf update [sudo] password for chris: error: db5 error(5) from dbenv->open: Input/output error error: cannot open Packages index using db5 - Input/output error (5) error: cannot open Packages database in /var/lib/rpm Error: Error: rpmdb open failed [chris@f26h Documents]$ sudo dnf search iotop error: db5 error(5) from dbenv->open: Input/output error error: cannot open Packages index using db5 - Input/output error (5) error: cannot open Packages database in /var/lib/rpm Error: Error: rpmdb open failed [chris@f26h Documents]$
On Mon, 12 Jun 2017 21:45:03 -0600 Chris Murphy lists@colorremedies.com wrote:
I'm hitting bug 1394862 with a libdb.x86_64 5.3.28-21.fc26 to libdb.x86_64 5.3.28-22.fc26 update. Why? It has a +4 karma and I'm hitting it the instant the dnf update completes. Should I negative karma the -22 package? Seems obviously broken to me.
Did you try removing the temp files in /var/lib/rpm, __db.00?, and then rebuilding the rpm database with rpm --rebuilddb? That worked for me when the update had a problem, and for the poster of the comment you reference in your comment (c100), and you don't mention doing it.
Whether this should be considered broken, I'll leave to more knowledgeable folks.