Rpm error cannot open packages index using db5 30969

Describe the bug

Run Yum update, or try to install a package using yum:

RPM: error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch
RPM: error: cannot open Packages index using db5 — (-30969)
RPM: error: cannot open Packages database in /var/lib/rpm
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘dnf clean packages’.
Error: Could not run transaction.

To Reproduce
Steps to reproduce the behavior:

1. Reboot
2. yum update
3. See error

Expected behavior
Updates completed succesfully

Additional context
I have deleted and started from scratch the whole WSL environment and yum works for one update cycle, then after an update and reboot I get the same error above.

Basic Troubleshooting Checklist

[x] I have searched Google for the error message.
[x] I have checked official WSL troubleshooting documentation: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#confirm-wsl-is-enabled.
[x] I have searched the official Microsoft WSL issues page: https://github.com/Microsoft/WSL/issues.
[x] I have searched the WLinux issues page: https://github.com/WhitewaterFoundry/WLinux/issues.
[x] I have reset WLinux: Settings->Apps->Apps & features->WLinux->Advanced Options->Reset.
[x] I have disabled and re-enabled WSL in Windows Features.
[x] I have run Windows 10 updates and restarted.

Windows Build

OS Version: 10.0.18362 N/A Build 18362

copy paste:

[root@SAMPC ~]# yum update
whitewaterfoundry_wslu 256 B/s | 833 B 00:03
Dependencies resolved.

Package Architecture Version Repository Size

Upgrading:
dnf noarch 4.2.8-2.fc30 updates 405 k
dnf-data noarch 4.2.8-2.fc30 updates 45 k
dnf-yum noarch 4.2.8-2.fc30 updates 42 k
fontconfig x86_64 2.13.1-9.fc30 updates 253 k
jbig2dec-libs x86_64 0.16-1.fc30 updates 69 k
libdnf x86_64 0.35.2-3.fc30 updates 589 k
libxcrypt x86_64 4.4.9-1.fc30 updates 123 k
libxcrypt-compat x86_64 4.4.9-1.fc30 updates 96 k
polkit-libs x86_64 0.116-2.fc30 updates 64 k
python3-dnf noarch 4.2.8-2.fc30 updates 413 k
python3-hawkey x86_64 0.35.2-3.fc30 updates 93 k
python3-libdnf x86_64 0.35.2-3.fc30 updates 708 k
vim-common x86_64 2:8.1.1991-2.fc30 updates 6.7 M
vim-enhanced x86_64 2:8.1.1991-2.fc30 updates 1.4 M
vim-filesystem noarch 2:8.1.1991-2.fc30 updates 28 k
vim-minimal x86_64 2:8.1.1991-2.fc30 updates 619 k

Transaction Summary

Upgrade 16 Packages

Total download size: 12 M
Is this ok [y/N]: y
Downloading Packages:
(1/16): dnf-yum-4.2.8-2.fc30.noarch.rpm 86 kB/s | 42 kB 00:00
(2/16): dnf-data-4.2.8-2.fc30.noarch.rpm 79 kB/s | 45 kB 00:00
(3/16): fontconfig-2.13.1-9.fc30.x86_64.rpm 288 kB/s | 253 kB 00:00
(4/16): jbig2dec-libs-0.16-1.fc30.x86_64.rpm 77 kB/s | 69 kB 00:00
(5/16): dnf-4.2.8-2.fc30.noarch.rpm 259 kB/s | 405 kB 00:01
(6/16): libxcrypt-compat-4.4.9-1.fc30.x86_64.rpm 265 kB/s | 96 kB 00:00
(7/16): polkit-libs-0.116-2.fc30.x86_64.rpm 269 kB/s | 64 kB 00:00
(8/16): libdnf-0.35.2-3.fc30.x86_64.rpm 609 kB/s | 589 kB 00:00
(9/16): libxcrypt-4.4.9-1.fc30.x86_64.rpm 130 kB/s | 123 kB 00:00
(10/16): python3-hawkey-0.35.2-3.fc30.x86_64.rpm 530 kB/s | 93 kB 00:00
(11/16): python3-dnf-4.2.8-2.fc30.noarch.rpm 232 kB/s | 413 kB 00:01
(12/16): python3-libdnf-0.35.2-3.fc30.x86_64.rpm 195 kB/s | 708 kB 00:03
(13/16): vim-filesystem-8.1.1991-2.fc30.noarch.rpm 272 kB/s | 28 kB 00:00
(14/16): vim-minimal-8.1.1991-2.fc30.x86_64.rpm 393 kB/s | 619 kB 00:01
(15/16): vim-enhanced-8.1.1991-2.fc30.x86_64.rpm 334 kB/s | 1.4 MB 00:04
(16/16): vim-common-8.1.1991-2.fc30.x86_64.rpm 612 kB/s | 6.7 MB 00:11

Total 809 kB/s | 12 MB 00:14
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
RPM: error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch
RPM: error: cannot open Packages index using db5 — (-30969)
RPM: error: cannot open Packages database in /var/lib/rpm
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘dnf clean packages’.
Error: Could not run transaction.
[root@SAMPC ~]#

dnf error conflicting packages between i686 and x86_64

I am getting a series of errors similar to this

when I try to dnf update , and a Python exception when I dnf install anything. These are a new errors that appeared at the same time, possibly related to a power failure I suffered yesterday in the middle of a dnf update , although the history log appears to suggest it had finished, with some errors, before the power went out.

Full errors for a current dnf update :

Error from dnf install [anything] :

Errors from the end of dnf history info 52 (the update before the power failure):

2 Answers 2

The most typical cause of this error is trying to install packages without having everything up to date. That sometimes causes new dependencies to be brought in which conflict with packages already on disk, and dnf doesn’t know that it should update those otherwise-unrelated packages.

In your case, it seems to be something else, since you are seeing the problem while running the update. Here, though, the error is definitely something out of sync between available and installed versions in the different architectures. For example:

Linebreaks added to make this obvious: It’s trying to install newer i686 packages and it doesn’t know to update older glibc.

The first thing I’d check is to see if you have multiple versions of the x86_64 glibc installed. If so, run sudo dnf repoquery —duplicates see the extra versions, and dnf remove —duplicates to clean up. (This will leave the files belonging to the latest package, so is safe even if it tries to remove things which seem important.)

If that’s not the case, it may simply be the mirror you are hitting now is not as up-to-date as the one you got earlier. In that case, try sudo dnf clean all and update again.

If that doesn’t work, you can often resolve this by temporarily removing all i686 packages. The system will function without them, and then you can do the update, and then put back what you need for compatibility with 32-bit apps.

If you are still getting db errors, you may have a different problem at the RPM level — but start with the above.

Источник

RPM DB_VERSION_MISMATCH #47

Describe the bug

Run Yum update, or try to install a package using yum:

RPM: error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch
RPM: error: cannot open Packages index using db5 — (-30969)
RPM: error: cannot open Packages database in /var/lib/rpm
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘dnf clean packages’.
Error: Could not run transaction.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
Updates completed succesfully

Additional context
I have deleted and started from scratch the whole WSL environment and yum works for one update cycle, then after an update and reboot I get the same error above.

Basic Troubleshooting Checklist

[x] I have searched Google for the error message.
[x] I have checked official WSL troubleshooting documentation: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#confirm-wsl-is-enabled.
[x] I have searched the official Microsoft WSL issues page: https://github.com/Microsoft/WSL/issues.
[x] I have searched the WLinux issues page: https://github.com/WhitewaterFoundry/WLinux/issues.
[x] I have reset WLinux: Settings->Apps->Apps & features->WLinux->Advanced Options->Reset.
[x] I have disabled and re-enabled WSL in Windows Features.
[x] I have run Windows 10 updates and restarted.

Windows Build

OS Version: 10.0.18362 N/A Build 18362

[root@SAMPC

]# yum update
whitewaterfoundry_wslu 256 B/s | 833 B 00:03
Dependencies resolved.

Package Architecture Version Repository Size

Upgrading:
dnf noarch 4.2.8-2.fc30 updates 405 k
dnf-data noarch 4.2.8-2.fc30 updates 45 k
dnf-yum noarch 4.2.8-2.fc30 updates 42 k
fontconfig x86_64 2.13.1-9.fc30 updates 253 k
jbig2dec-libs x86_64 0.16-1.fc30 updates 69 k
libdnf x86_64 0.35.2-3.fc30 updates 589 k
libxcrypt x86_64 4.4.9-1.fc30 updates 123 k
libxcrypt-compat x86_64 4.4.9-1.fc30 updates 96 k
polkit-libs x86_64 0.116-2.fc30 updates 64 k
python3-dnf noarch 4.2.8-2.fc30 updates 413 k
python3-hawkey x86_64 0.35.2-3.fc30 updates 93 k
python3-libdnf x86_64 0.35.2-3.fc30 updates 708 k
vim-common x86_64 2:8.1.1991-2.fc30 updates 6.7 M
vim-enhanced x86_64 2:8.1.1991-2.fc30 updates 1.4 M
vim-filesystem noarch 2:8.1.1991-2.fc30 updates 28 k
vim-minimal x86_64 2:8.1.1991-2.fc30 updates 619 k

Transaction Summary

Upgrade 16 Packages

Total download size: 12 M
Is this ok [y/N]: y
Downloading Packages:
(1/16): dnf-yum-4.2.8-2.fc30.noarch.rpm 86 kB/s | 42 kB 00:00
(2/16): dnf-data-4.2.8-2.fc30.noarch.rpm 79 kB/s | 45 kB 00:00
(3/16): fontconfig-2.13.1-9.fc30.x86_64.rpm 288 kB/s | 253 kB 00:00
(4/16): jbig2dec-libs-0.16-1.fc30.x86_64.rpm 77 kB/s | 69 kB 00:00
(5/16): dnf-4.2.8-2.fc30.noarch.rpm 259 kB/s | 405 kB 00:01
(6/16): libxcrypt-compat-4.4.9-1.fc30.x86_64.rpm 265 kB/s | 96 kB 00:00
(7/16): polkit-libs-0.116-2.fc30.x86_64.rpm 269 kB/s | 64 kB 00:00
(8/16): libdnf-0.35.2-3.fc30.x86_64.rpm 609 kB/s | 589 kB 00:00
(9/16): libxcrypt-4.4.9-1.fc30.x86_64.rpm 130 kB/s | 123 kB 00:00
(10/16): python3-hawkey-0.35.2-3.fc30.x86_64.rpm 530 kB/s | 93 kB 00:00
(11/16): python3-dnf-4.2.8-2.fc30.noarch.rpm 232 kB/s | 413 kB 00:01
(12/16): python3-libdnf-0.35.2-3.fc30.x86_64.rpm 195 kB/s | 708 kB 00:03
(13/16): vim-filesystem-8.1.1991-2.fc30.noarch.rpm 272 kB/s | 28 kB 00:00
(14/16): vim-minimal-8.1.1991-2.fc30.x86_64.rpm 393 kB/s | 619 kB 00:01
(15/16): vim-enhanced-8.1.1991-2.fc30.x86_64.rpm 334 kB/s | 1.4 MB 00:04
(16/16): vim-common-8.1.1991-2.fc30.x86_64.rpm 612 kB/s | 6.7 MB 00:11

Total 809 kB/s | 12 MB 00:14
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
RPM: error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch
RPM: error: cannot open Packages index using db5 — (-30969)
RPM: error: cannot open Packages database in /var/lib/rpm
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘dnf clean packages’.
Error: Could not run transaction.
[root@SAMPC

The text was updated successfully, but these errors were encountered:

Источник

How to install CentOS 8 on WSL 1 or 2 of Windows 10

CentOS 8 or any other of its version is not officially available on Windows 10 App store for WSL- Windows subsystem for Linux, however, you can still install and use it.

Microsoft has continuously shown its love towards Linux and that can be seen in WSL. With the latest Windows 10 May update, the WSL 2, an upgraded version of the previous WSL 1 will be available for regular users. The benefit of that is, now we will have a full-fledged Linux kernel to operate various Linux distros such as Ubuntu, Debian Kali, SUSE, and more… Recently, Ubuntu 20.04 LTS, the latest version of this Linux is available to download and install on Windows 10 for WSL but sorry to say, we don’t have popular CentOS server Linux there. Perhaps, it is because of CentOS’s less popularity among standard Desktop Linux users. However, if you are a developer or just a Linux enthusiast and want to use CentOS 8 on Windows 10 WSL, here is the tutorial on that.

requirements

• WSL on Windows 10
• Internet connection to download the required files.

Step 1: Enable WSL on your System

If you already have Windows subsystem for Linux enabled on your system then you can move to the next step. However, those yet need to Turn it ON, simply start the Powershell as Administrator and copy-paste the below command in it. Once the process gets completed, restart your system.

Step 2: Download CentOS 8 WSL files

Well, to get the CentOS WSL Linux app, we don’t need to visit Windows 10 store because it is not there, instead of that it is available on Github as an open-source project developed by some Japanese developer, named yuk7 (profile name). Therefore go to his Github project page and under the CentOS WSL release, you will get the latest 8.1 version. But remember to use this release you should be on the latest Windows 10 May update 2004 or later. Otherwise, you can run the CentOS 7 WSL app.

Step 3: Unzip CentOS8.zip

The downloaded file will be in zipped format, thus simply right-click and unzip it somewhere you won’t delete the file accidentally.

Extract zipped CentOS8 WSL

Step 3: Install CentOS 8 on WSL

Open the extracted folder and run the CentOS8.exe file. If Windows shows some suspicion on that, just select the option “Run Anyway”.

In a few minutes, it will register this new Linux app under the WSL feature of Windows 10.

CentOS 8 Windows 10 WSL installation complete

Step 4: Run the Linux app

Now, again run the same CentOS8 executable file present inside the extracted folder, but this time you will see the command line with the root user. Or Simply in the windows 10 search box type CentOS.

To test everything is working fine, we ran a system update command. You can do the same as well.

By default, the root user is without any password and if you want, you can set one.

Furthermore, those who want to run it under WSL 2, can see this tutorial: how to run a Linux app on WSL 2.

Run Centos Update command

Uninstall CentOS 8 from WSL (optional)

In the future, if you want to delete this Linux app then don’t just delete the CentOS 8 unzipped folder directly otherwise it will create a problem in reinstalling the same, thus properly deregister and then delete the files.

Open PowerShell Window here

• Open its folder and press & hold shift and right-click inside that folder.
• Select Open Powershell window here.
• Run command:

The output for the above command:

So, this was a simple tutorial on running CentOS 8 server on Windows 10 WSL.

Note: If you get this error in the future-

Then simply run-

Note: If you get an error:

Failed to download metadata for repo ‘AppStream’ [CentOS]

Источник

Невозможно установить Oracle SQL Developer 4.0.2 (4.0.2.15.21) из файла rpm.

Я недавно обновился до Ubuntu 14.04 (с помощью диспетчера обновлений), и он работает без проблем.

В котором я использую SQL Developer 3.2.20.09, и он отлично работает. Теперь новая версия была выпущена 5 мая 2014 года, и я хотел бы использовать ее, так как она отлично работает с JDK 1.7. Я следовал инструкциям по установке, предоставленным Oracle, но установить его не удалось.

Использовал Alien для установки пакета RPM:

что привело к этой ошибке:

Нужно ли обновлять какой-либо пакет вручную или я пропустил обновление при обновлении до Ubuntu 14.04?

4 ответа

Сначала вы должны преобразовать файл.rpm в.deb, который является форматом установочного файла в Ubuntu.

Затем установите этот файл.deb:

Мне не нравится использовать конвертированные RPM для установки в Ubuntu, если есть альтернатива.

Я предпочитаю использовать двоичный пакет вручную, особенно с приложениями Java, которые обычно не имеют конкретной зависимости (очевидно, JRE / JDK).

В этом случае я устанавливаю SQLDeveloper следующим образом:

• скачайте пакет «Другие платформы«: sqldeveloper-4.0.2.15.21-no-jre.zip
• распакуйте пакет в /opt/sqldeveloper (или другой каталог, если хотите, я поместил все установленные вручную пакеты в /opt)
• создайте файл sqldeveloper.desktop в / usr / share / Applications (для всех пользователей) или

/.local/share/ Applications (только для вашего пользователя)

Источник

singularity (git version) bootstrapping CentOS-7 container from debian jessie or ubuntu trusty #241

reported on #singularity irc channel and reproduced locally.

bootstrap fails during %post when yum install vim-minimal with:

imho /var/lib/rpm is not populated correctly, shell inside the container hosted on jessie/trusty verify that content of /var/lib/rpm is smaller than what I get from a centos-7 hosted host.

The text was updated successfully, but these errors were encountered:

@gmkurtzer can comment on building from scratch, but I’d recommend just bootstrapping a docker image. Here is what I started with, first for centos.def

and then the commands:

then for any post install you can just add that in the post section, so the entire file should look like:

Give that a go, let me know how it goes! If you need a different version of centos, then check out the different tags here: https://hub.docker.com/_/centos/

something is not right on my jessie build? «./configure —prefix=/»

could you show me the contents of your libexec/python folder?

2 things. We need to properly catch the python error and ABORT and I think the first issue referenced is due to incompatible RPM DBs based on the version of the DB installed by the rpmlib on the host versus the rpmlib inside the container. Aside from exporting and importing the database, I don’t think it is fixable.

centos7 container hosted on centos7:

my centos7 host:

jessie (host of failed container bootstrap from scratch):

/me shrugs. Maybe a different version of bdb that RPM got linked to?

Can you build a chroot from scratch using YUM and make it work? I’m still somewhat convinced this is not a Singularity issue as opposed to a RPM DB mismatch somehow. I’ve seen similar creating a C6 image from C7 host. When you shell into the image you can not run RPM commands within the host.

Have you tried running RPM commands from outside the container? Mount up the image and use the —root RPM command to see if that works.

I confirme your suspected rpm compatibility issues: bootstrapping (from scratch) a Centos6 container from a CentOS-7 host yields an non working one 🙁

After mounting the container:

Bottom line, imho, boostrap from scratch only works fine when RHEL’s clone versions are the same on host and container, or you can bootstrap from a docker image/tarball to work around the bootstrap from scratch issue cause by rpm, ymmv.

Oh! I’ve seen this error before.

It’s something to do with the fact that overlayfs is non-POSIX and RPM expects POSIX-like behavior.

(there are a few others). Seems that you can workaround this by doing the following:

@bbockelm: Yeah, this is an old RPM DB compatibility issue with bootstrapping. There are some shortcuts that sometimes work: touch /var/lib/rpm/* and rm /var/lib/rpm/_* , but if the BDB format itself is non-compatible (e.g. creating an RPM DB with a newer version of BDB then what is in the chroot/container) then it is a harder problem to solve. It usually involves exporting and re-importing the database.

@truatpasteurdotfr: I don’t think this can be fixed within Singularity unless we can come up with a method to reliably script the export/import of the BDB after bootstrap of the core OS. Thoughts?

followup: this recipe works on c7 host to bootstrap a c6 container:

but it fails to bootstrap a CentOS-5 container on the same CentOS-7 host:

We can include the removing of the DB lock files (/var/lib/rpm/__*), touch, and rebuilding of the DB in the redhat module, but the truly portable fix is to dump the DB’s and re-import.

trying the same trick on jessie host/c7 container yields:

as if /var/lib/rpm was not fully populated when the %post was run.

I was planning on making a new issue for this, but then @vsoch pointed me here! I’m also experiencing the same issue: If a Yum-based system is bootstrapped from a Debian-family OS (Debian, Ubuntu, etc.), then the RPM database doesn’t appear in the right place.

I’m working with a Singularity built from Git commit 17cad8a, but I’ve also seen this issue on Singularity 2.2.1. The only option I’m passing to ./configure is a custom —prefix .

Here’s an example bootstrap file that exposes this problem:

And here’s a asciinema that shows what happens when you bootstrap the above using Singularity commit 17cad8a on Ubuntu 16.10:

It took almost a day of hunting around, but I found the issue. The problem is that Debian (and therefore Ubuntu) have intentionally changed the _dbpath RPM setting, which tells RPM where the database files live.

Here’s what rpm —showrc | grep -E «:s_dbpaths» | cut -f2 returns on stock CentOS and Fedora:

• CentOS 6: %<_var>/lib/rpm (and % <_var>resolves to /var )
• CentOS 7: Same as CentOS 6
• Fedora 25: Same as CentOS 6

And if you first run apt-get -y install rpm , here’s what rpm —showrc | grep -E «:s_dbpaths» | cut -f2 returns on stock Debian and Ubuntu:

• Debian 7: %(echo $HOME/.rpmdb)
• Debian 8: %(bash -c ‘echo

/.rpmdb’)

(It’s worth noting that I checked for the _var RPM variable in Ubuntu 14.04 and 16.10; it is defined, and set to /var . On Ubuntu 16.04, _var is not defined.)

(props to dply.co for letting me spin up things quickly for testing!)

The above asciinema recording confirms, yum dumped the RPM database files into a sub-directory of my home directory, in the container. My actual home directory isn’t being touched, because Singularity is using the —installroot option for yum .

Источник

I am getting a series of errors similar to this

file /usr/share/doc/glibc/NEWS from install of glibc-2.25-10.fc26.i686 conflicts with file from package glibc-2.25-7.fc26.x86_64

when I try to dnf update, and a Python exception when I dnf install anything. These are a new errors that appeared at the same time, possibly related to a power failure I suffered yesterday in the middle of a dnf update, although the history log appears to suggest it had finished, with some errors, before the power went out.

Full errors for a current dnf update:

Error: Transaction check error:
  file /usr/share/doc/glibc/NEWS from install of glibc-2.25-10.fc26.i686 conflicts with file from package glibc-2.25-7.fc26.x86_64
  file /usr/share/man/man1/xmlwf.1.gz from install of expat-2.2.4-1.fc26.i686 conflicts with file from package expat-2.2.1-1.fc26.x86_64
  file /usr/share/doc/sqlite-libs/README.md from install of sqlite-libs-3.20.1-1.fc26.i686 conflicts with file from package sqlite-libs-3.19.3-1.fc26.x86_64
  file /usr/share/doc/gdk-pixbuf2/NEWS from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/cs/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/de/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/es/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/fr/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/fur/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/gl/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/hu/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/id/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/kk/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/lt/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/pl/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/pt_BR/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/sl/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/sr/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/sr@latin/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/sv/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/locale/tr/LC_MESSAGES/gdk-pixbuf.mo from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/man/man1/gdk-pixbuf-query-loaders.1.gz from install of gdk-pixbuf2-2.36.9-1.fc26.i686 conflicts with file from package gdk-pixbuf2-2.36.7-1.fc26.x86_64
  file /usr/share/doc/libidn2/README.md from install of libidn2-2.0.4-1.fc26.i686 conflicts with file from package libidn2-2.0.2-1.fc26.x86_64
  file /usr/share/doc/libidn2/NEWS from install of libidn2-2.0.4-1.fc26.i686 conflicts with file from package libidn2-2.0.2-1.fc26.x86_64
  file /usr/share/info/libidn2.info.gz from install of libidn2-2.0.4-1.fc26.i686 conflicts with file from package libidn2-2.0.2-1.fc26.x86_64
  file /usr/share/man/man1/idn2.1.gz from install of libidn2-2.0.4-1.fc26.i686 conflicts with file from package libidn2-2.0.2-1.fc26.x86_64
  file /usr/share/man/man5/cert8.db.5.gz from install of nss-3.32.0-1.1.fc26.i686 conflicts with file from package nss-3.30.2-1.1.fc26.x86_64
  file /usr/share/man/man5/cert9.db.5.gz from install of nss-3.32.0-1.1.fc26.i686 conflicts with file from package nss-3.30.2-1.1.fc26.x86_64
  file /usr/share/man/man5/key3.db.5.gz from install of nss-3.32.0-1.1.fc26.i686 conflicts with file from package nss-3.30.2-1.1.fc26.x86_64
  file /usr/share/man/man5/key4.db.5.gz from install of nss-3.32.0-1.1.fc26.i686 conflicts with file from package nss-3.30.2-1.1.fc26.x86_64
  file /usr/share/man/man5/pkcs11.txt.5.gz from install of nss-3.32.0-1.1.fc26.i686 conflicts with file from package nss-3.30.2-1.1.fc26.x86_64
  file /usr/share/man/man5/secmod.db.5.gz from install of nss-3.32.0-1.1.fc26.i686 conflicts with file from package nss-3.30.2-1.1.fc26.x86_64
  file /usr/share/man/man5/k5identity.5.gz from install of krb5-libs-1.15.1-25.fc26.i686 conflicts with file from package krb5-libs-1.15.1-17.fc26.x86_64
  file /usr/share/man/man5/k5login.5.gz from install of krb5-libs-1.15.1-25.fc26.i686 conflicts with file from package krb5-libs-1.15.1-17.fc26.x86_64
  file /usr/share/man/man5/krb5.conf.5.gz from install of krb5-libs-1.15.1-25.fc26.i686 conflicts with file from package krb5-libs-1.15.1-17.fc26.x86_64
  file /usr/share/doc/wine-core/AUTHORS from install of wine-core-2.15-1.fc26.i686 conflicts with file from package wine-core-2.12-1.fc26.x86_64
  file /usr/share/doc/wine-core/VERSION from install of wine-core-2.15-1.fc26.i686 conflicts with file from package wine-core-2.12-1.fc26.x86_64
  file /usr/share/doc/wine-core/ANNOUNCE from install of wine-core-2.15-1.fc26.i686 conflicts with file from package wine-core-2.12-1.fc26.x86_64
  file /usr/share/doc/pango/NEWS from install of pango-1.40.11-3.fc26.i686 conflicts with file from package pango-1.40.7-1.fc26.x86_64
  file /usr/share/man/man1/pango-view.1.gz from install of pango-1.40.11-3.fc26.i686 conflicts with file from package pango-1.40.7-1.fc26.x86_64
  file /usr/share/doc/gtk3/README from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/doc/gtk3/NEWS from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/cs/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/de/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/es/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/fi/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/fr/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/fur/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/gl/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/hr/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/id/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/kk/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/lt/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/ne/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/pl/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/pt_BR/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/sk/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/sl/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/sr/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/locale/sr@latin/LC_MESSAGES/gtk30.mo from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/man/man1/broadwayd.1.gz from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/man/man1/gtk-launch.1.gz from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/man/man1/gtk-query-immodules-3.0.1.gz from install of gtk3-3.22.19-1.fc26.i686 conflicts with file from package gtk3-3.22.17-2.fc26.x86_64
  file /usr/share/doc/libsoup/NEWS from install of libsoup-2.58.2-1.fc26.i686 conflicts with file from package libsoup-2.58.1-2.fc26.x86_64
  file /usr/share/doc/libgusb/NEWS from install of libgusb-0.2.11-1.fc26.i686 conflicts with file from package libgusb-0.2.10-1.fc26.x86_64
  file /usr/share/doc/p11-kit/NEWS from install of p11-kit-0.23.8-1.fc26.i686 conflicts with file from package p11-kit-0.23.5-3.fc26.x86_64
  file /usr/share/man/man1/trust.1.gz from install of p11-kit-0.23.8-1.fc26.i686 conflicts with file from package p11-kit-0.23.5-3.fc26.x86_64
  file /usr/share/man/man5/pkcs11.conf.5.gz from install of p11-kit-0.23.8-1.fc26.i686 conflicts with file from package p11-kit-0.23.5-3.fc26.x86_64
  file /usr/share/man/man8/p11-kit.8.gz from install of p11-kit-0.23.8-1.fc26.i686 conflicts with file from package p11-kit-0.23.5-3.fc26.x86_64

Error Summary
-------------

Error from dnf install [anything]:

Last metadata expiration check: 0:15:05 ago on Tue 05 Sep 2017 11:09:50 AEST.
Traceback (most recent call last):
  File "/bin/dnf", line 58, in <module>
    main.user_main(sys.argv[1:], exit_code=True)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 179, in user_main
    errcode = main(args)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 64, in main
    return _main(base, args, cli_class, option_parser_class)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 99, in _main
    return cli_run(cli, base)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 115, in cli_run
    cli.run()
  File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 962, in run
    return self.command.run()
  File "/usr/lib/python3.6/site-packages/dnf/cli/commands/install.py", line 120, in run
    self.base.install(pkg_spec, strict=strict, forms=forms)
  File "/usr/lib/python3.6/site-packages/dnf/base.py", line 1582, in install
    subj._is_arch_specified(self.sack):
  File "/usr/lib/python3.6/site-packages/dnf/subject.py", line 71, in _is_arch_specified
    q = self._nevra_to_filters(sack.query(), nevra)
  File "/usr/lib/python3.6/site-packages/dnf/subject.py", line 49, in _nevra_to_filters
    query._filterm(*flags, **{name + '__glob': attr})
  File "/usr/lib/python3.6/site-packages/dnf/query.py", line 93, in _filterm
    return super(Query, self)._filterm(*args, **nargs)
AttributeError: 'super' object has no attribute '_filterm'

Errors from the end of dnf history info 52 (the update before the power failure):

Scriptlet output:
   1 warning: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-5.b01.fc26.x86_64/jre/lib/security/java.security created as /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-5.b01.fc26.x86_64/jre/lib/security/java.security.rpmnew
   2 error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch
   3 error: cannot open Packages index using db5 -  (-30969)
   4 error: cannot open Packages database in /var/lib/rpm
   5 error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch
   6 error: cannot open Packages index using db5 -  (-30969)
   7 error: cannot open Packages database in /var/lib/rpm
   8 error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch
   9 error: cannot open Packages index using db5 -  (-30969)
  10 error: cannot open Packages database in /var/lib/rpm
  11 error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch
  12 error: cannot open Packages index using db5 -  (-30969)
  13 error: cannot open Packages database in /var/lib/rpm
  14 restored /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-5.b01.fc26.x86_64/jre/lib/security/java.security.rpmnew to /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-5.b01.fc26.x86_64/jre/lib/security/java.security