dnf error conflicting packages between i686 and x86_64RPMDB broke after a yum update in fedora 19?What is the difference between i686 and x86_64 packages?How can I install 32-bit dependencies on a 64-bit machine using dnf builddep?How to engage with Fedora 23 error message in dnf install error of dnspython?identify all broken / conflicting rpm's and fix them *correctly* Fedora 23, persistent usbLinux: dnf error: Aborted (core dumped) after packages upgraded from .fc22.x86_64 to .fc22.i686 in fedora 22'obsoleting packages' in package manager output? [DNF]Error while upgrading to Fedora 26 from 25How to differentiate between repo and built packages with dnf?Reverse dependencies to determining the Cause of DNF conflicting packages

Why do phishing e-mails use faked e-mail addresses instead of the real one?

How to educate team mate to take screenshots for bugs with out unwanted stuff

Why aren't there more Gauls like Obelix?

School performs periodic password audits. Is my password compromised?

Interpretation of linear regression interaction term plot

Having the player face themselves after the mid-game

What exactly is the meaning of "fine wine"?

Can I negotiate a patent idea for a raise, under French law?

Too soon for a plot twist?

Should I apply for my boss's promotion?

Does the US political system, in principle, allow for a no-party system?

A running toilet that stops itself

How does a sound wave propagate?

Paper published similar to PhD thesis

How do you make a gun that shoots melee weapons and/or swords?

How to distinguish easily different soldier of ww2?

The (Easy) Road to Code

Will the concrete slab in a partially heated shed conduct a lot of heat to the unconditioned area?

Why is there an extra space when I type "ls" on the Desktop?

Are small insurances worth it?

Where is the License file location for Identity Server in Sitecore 9.1?

Issue with units for a rocket nozzle throat area problem

How would an energy-based "projectile" blow up a spaceship?

Limpar string com Regex



dnf error conflicting packages between i686 and x86_64


RPMDB broke after a yum update in fedora 19?What is the difference between i686 and x86_64 packages?How can I install 32-bit dependencies on a 64-bit machine using dnf builddep?How to engage with Fedora 23 error message in dnf install error of dnspython?identify all broken / conflicting rpm's and fix them *correctly* Fedora 23, persistent usbLinux: dnf error: Aborted (core dumped) after packages upgraded from .fc22.x86_64 to .fc22.i686 in fedora 22'obsoleting packages' in package manager output? [DNF]Error while upgrading to Fedora 26 from 25How to differentiate between repo and built packages with dnf?Reverse dependencies to determining the Cause of DNF conflicting packages













2















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





fedora dnf cpu-architecture







share|improve this question




























    2















    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





    fedora dnf cpu-architecture







    share|improve this question


























      2












      2








      2








      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





      fedora dnf cpu-architecture







      share|improve this question
















      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





      fedora dnf cpu-architecture




      fedora dnf cpu-architecture






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Sep 5 '17 at 1:41









      Jeff Schaller

      43.1k1159138




      43.1k1159138










      asked Sep 5 '17 at 1:23









      lvclvc

      20628




      20628




















          3 Answers
          3






          active

          oldest

          votes


















          4














          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:



          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


          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.






          share|improve this answer

























          • dnf repoquery --duplicates does come out with a long list of mostly x86_64 packages (and some i686 ones), including multiple versions of some packages - but doesn't seem to actually remove any of them. But if I'm understanding you correctly, when it lists two x86_64 versions of a package that would mean I have three of it installed, and it should be safe for me to do something like dnf repoquery --duplicates | xargs dnf remove?

            – lvc
            Sep 6 '17 at 9:26






          • 1





            Sorry, dnf remove --duplicates to remove. I'll add that.

            – mattdm
            Sep 6 '17 at 15:55











          • dnf remove --duplicates tells me, twice, that it "would result in removing the following protected packages: dnf, sudo". I found a fedora bugzilla thread discussing removing protected packages, and tried dnf remove --duplicates --disableplugin=protected_packages for the same error, and dnf remove --disableplugin=protected_packges libdnf-0:0.9.2-1.fc26.x86_64 for the same Python traceback as trying to dnf install anything.

            – lvc
            Sep 7 '17 at 2:42











          • Hmmm. Given the db errors, can you try sudo rpm --rebuilddb? Should run with no errors and may fix the problem.

            – mattdm
            Sep 7 '17 at 5:44











          • rpm --rebuilddb did indeed run without errors, but doesn't seem to have fixed the problems. The Python traceback makes me wonder if my dnf is finding the wrong version of a module, although it seems strange that the only relevant duplicates are libdnf.x86_64 (ie, native code) but the traceback only mentions pure Python files. Should I perhaps be trying to remove the libdnf dups at the rpm level, and/or reinstall dnf itself? In which case, I would need to find the rpms - would they still be cached on my system somewhere?

            – lvc
            Sep 7 '17 at 13:39


















          0














          I got past the Python exception by booting from a live USB, and using dnf --installroot=/mnt/fedora; the package conflicts kept coming, including errors when I tried to dnf remove --duplicates or even trying to remove packages one-by-one. So I ended up deciding the system was not fixable, and reinstalling Fedora - along with finally getting around to setting up snapper so there's an easy fix next time something like this happens.






          share|improve this answer






























            -1














            after every package(uptodate) ready,



            vi /etc/dnf/dnf.conf



            [main]
            gpgcheck=1
            installonly_limit=3
            clean_requirements_on_remove=True
            exactarch=1 ##<--add line this


            after save to $(prompt)



            dnf clean all



            dnf update






            share|improve this answer








            New contributor




            Jungsuep Yoon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.




















            • would be pleased, paste[solved]; thanks

              – Jungsuep Yoon
              1 hour ago










            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f390367%2fdnf-error-conflicting-packages-between-i686-and-x86-64%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            3 Answers
            3






            active

            oldest

            votes








            3 Answers
            3






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            4














            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:



            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


            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.






            share|improve this answer

























            • dnf repoquery --duplicates does come out with a long list of mostly x86_64 packages (and some i686 ones), including multiple versions of some packages - but doesn't seem to actually remove any of them. But if I'm understanding you correctly, when it lists two x86_64 versions of a package that would mean I have three of it installed, and it should be safe for me to do something like dnf repoquery --duplicates | xargs dnf remove?

              – lvc
              Sep 6 '17 at 9:26






            • 1





              Sorry, dnf remove --duplicates to remove. I'll add that.

              – mattdm
              Sep 6 '17 at 15:55











            • dnf remove --duplicates tells me, twice, that it "would result in removing the following protected packages: dnf, sudo". I found a fedora bugzilla thread discussing removing protected packages, and tried dnf remove --duplicates --disableplugin=protected_packages for the same error, and dnf remove --disableplugin=protected_packges libdnf-0:0.9.2-1.fc26.x86_64 for the same Python traceback as trying to dnf install anything.

              – lvc
              Sep 7 '17 at 2:42











            • Hmmm. Given the db errors, can you try sudo rpm --rebuilddb? Should run with no errors and may fix the problem.

              – mattdm
              Sep 7 '17 at 5:44











            • rpm --rebuilddb did indeed run without errors, but doesn't seem to have fixed the problems. The Python traceback makes me wonder if my dnf is finding the wrong version of a module, although it seems strange that the only relevant duplicates are libdnf.x86_64 (ie, native code) but the traceback only mentions pure Python files. Should I perhaps be trying to remove the libdnf dups at the rpm level, and/or reinstall dnf itself? In which case, I would need to find the rpms - would they still be cached on my system somewhere?

              – lvc
              Sep 7 '17 at 13:39















            4














            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:



            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


            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.






            share|improve this answer

























            • dnf repoquery --duplicates does come out with a long list of mostly x86_64 packages (and some i686 ones), including multiple versions of some packages - but doesn't seem to actually remove any of them. But if I'm understanding you correctly, when it lists two x86_64 versions of a package that would mean I have three of it installed, and it should be safe for me to do something like dnf repoquery --duplicates | xargs dnf remove?

              – lvc
              Sep 6 '17 at 9:26






            • 1





              Sorry, dnf remove --duplicates to remove. I'll add that.

              – mattdm
              Sep 6 '17 at 15:55











            • dnf remove --duplicates tells me, twice, that it "would result in removing the following protected packages: dnf, sudo". I found a fedora bugzilla thread discussing removing protected packages, and tried dnf remove --duplicates --disableplugin=protected_packages for the same error, and dnf remove --disableplugin=protected_packges libdnf-0:0.9.2-1.fc26.x86_64 for the same Python traceback as trying to dnf install anything.

              – lvc
              Sep 7 '17 at 2:42











            • Hmmm. Given the db errors, can you try sudo rpm --rebuilddb? Should run with no errors and may fix the problem.

              – mattdm
              Sep 7 '17 at 5:44











            • rpm --rebuilddb did indeed run without errors, but doesn't seem to have fixed the problems. The Python traceback makes me wonder if my dnf is finding the wrong version of a module, although it seems strange that the only relevant duplicates are libdnf.x86_64 (ie, native code) but the traceback only mentions pure Python files. Should I perhaps be trying to remove the libdnf dups at the rpm level, and/or reinstall dnf itself? In which case, I would need to find the rpms - would they still be cached on my system somewhere?

              – lvc
              Sep 7 '17 at 13:39













            4












            4








            4







            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:



            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


            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.






            share|improve this answer















            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:



            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


            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.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Sep 6 '17 at 15:58

























            answered Sep 5 '17 at 12:19









            mattdmmattdm

            28.8k1372116




            28.8k1372116












            • dnf repoquery --duplicates does come out with a long list of mostly x86_64 packages (and some i686 ones), including multiple versions of some packages - but doesn't seem to actually remove any of them. But if I'm understanding you correctly, when it lists two x86_64 versions of a package that would mean I have three of it installed, and it should be safe for me to do something like dnf repoquery --duplicates | xargs dnf remove?

              – lvc
              Sep 6 '17 at 9:26






            • 1





              Sorry, dnf remove --duplicates to remove. I'll add that.

              – mattdm
              Sep 6 '17 at 15:55











            • dnf remove --duplicates tells me, twice, that it "would result in removing the following protected packages: dnf, sudo". I found a fedora bugzilla thread discussing removing protected packages, and tried dnf remove --duplicates --disableplugin=protected_packages for the same error, and dnf remove --disableplugin=protected_packges libdnf-0:0.9.2-1.fc26.x86_64 for the same Python traceback as trying to dnf install anything.

              – lvc
              Sep 7 '17 at 2:42











            • Hmmm. Given the db errors, can you try sudo rpm --rebuilddb? Should run with no errors and may fix the problem.

              – mattdm
              Sep 7 '17 at 5:44











            • rpm --rebuilddb did indeed run without errors, but doesn't seem to have fixed the problems. The Python traceback makes me wonder if my dnf is finding the wrong version of a module, although it seems strange that the only relevant duplicates are libdnf.x86_64 (ie, native code) but the traceback only mentions pure Python files. Should I perhaps be trying to remove the libdnf dups at the rpm level, and/or reinstall dnf itself? In which case, I would need to find the rpms - would they still be cached on my system somewhere?

              – lvc
              Sep 7 '17 at 13:39

















            • dnf repoquery --duplicates does come out with a long list of mostly x86_64 packages (and some i686 ones), including multiple versions of some packages - but doesn't seem to actually remove any of them. But if I'm understanding you correctly, when it lists two x86_64 versions of a package that would mean I have three of it installed, and it should be safe for me to do something like dnf repoquery --duplicates | xargs dnf remove?

              – lvc
              Sep 6 '17 at 9:26






            • 1





              Sorry, dnf remove --duplicates to remove. I'll add that.

              – mattdm
              Sep 6 '17 at 15:55











            • dnf remove --duplicates tells me, twice, that it "would result in removing the following protected packages: dnf, sudo". I found a fedora bugzilla thread discussing removing protected packages, and tried dnf remove --duplicates --disableplugin=protected_packages for the same error, and dnf remove --disableplugin=protected_packges libdnf-0:0.9.2-1.fc26.x86_64 for the same Python traceback as trying to dnf install anything.

              – lvc
              Sep 7 '17 at 2:42











            • Hmmm. Given the db errors, can you try sudo rpm --rebuilddb? Should run with no errors and may fix the problem.

              – mattdm
              Sep 7 '17 at 5:44











            • rpm --rebuilddb did indeed run without errors, but doesn't seem to have fixed the problems. The Python traceback makes me wonder if my dnf is finding the wrong version of a module, although it seems strange that the only relevant duplicates are libdnf.x86_64 (ie, native code) but the traceback only mentions pure Python files. Should I perhaps be trying to remove the libdnf dups at the rpm level, and/or reinstall dnf itself? In which case, I would need to find the rpms - would they still be cached on my system somewhere?

              – lvc
              Sep 7 '17 at 13:39
















            dnf repoquery --duplicates does come out with a long list of mostly x86_64 packages (and some i686 ones), including multiple versions of some packages - but doesn't seem to actually remove any of them. But if I'm understanding you correctly, when it lists two x86_64 versions of a package that would mean I have three of it installed, and it should be safe for me to do something like dnf repoquery --duplicates | xargs dnf remove?

            – lvc
            Sep 6 '17 at 9:26





            dnf repoquery --duplicates does come out with a long list of mostly x86_64 packages (and some i686 ones), including multiple versions of some packages - but doesn't seem to actually remove any of them. But if I'm understanding you correctly, when it lists two x86_64 versions of a package that would mean I have three of it installed, and it should be safe for me to do something like dnf repoquery --duplicates | xargs dnf remove?

            – lvc
            Sep 6 '17 at 9:26




            1




            1





            Sorry, dnf remove --duplicates to remove. I'll add that.

            – mattdm
            Sep 6 '17 at 15:55





            Sorry, dnf remove --duplicates to remove. I'll add that.

            – mattdm
            Sep 6 '17 at 15:55













            dnf remove --duplicates tells me, twice, that it "would result in removing the following protected packages: dnf, sudo". I found a fedora bugzilla thread discussing removing protected packages, and tried dnf remove --duplicates --disableplugin=protected_packages for the same error, and dnf remove --disableplugin=protected_packges libdnf-0:0.9.2-1.fc26.x86_64 for the same Python traceback as trying to dnf install anything.

            – lvc
            Sep 7 '17 at 2:42





            dnf remove --duplicates tells me, twice, that it "would result in removing the following protected packages: dnf, sudo". I found a fedora bugzilla thread discussing removing protected packages, and tried dnf remove --duplicates --disableplugin=protected_packages for the same error, and dnf remove --disableplugin=protected_packges libdnf-0:0.9.2-1.fc26.x86_64 for the same Python traceback as trying to dnf install anything.

            – lvc
            Sep 7 '17 at 2:42













            Hmmm. Given the db errors, can you try sudo rpm --rebuilddb? Should run with no errors and may fix the problem.

            – mattdm
            Sep 7 '17 at 5:44





            Hmmm. Given the db errors, can you try sudo rpm --rebuilddb? Should run with no errors and may fix the problem.

            – mattdm
            Sep 7 '17 at 5:44













            rpm --rebuilddb did indeed run without errors, but doesn't seem to have fixed the problems. The Python traceback makes me wonder if my dnf is finding the wrong version of a module, although it seems strange that the only relevant duplicates are libdnf.x86_64 (ie, native code) but the traceback only mentions pure Python files. Should I perhaps be trying to remove the libdnf dups at the rpm level, and/or reinstall dnf itself? In which case, I would need to find the rpms - would they still be cached on my system somewhere?

            – lvc
            Sep 7 '17 at 13:39





            rpm --rebuilddb did indeed run without errors, but doesn't seem to have fixed the problems. The Python traceback makes me wonder if my dnf is finding the wrong version of a module, although it seems strange that the only relevant duplicates are libdnf.x86_64 (ie, native code) but the traceback only mentions pure Python files. Should I perhaps be trying to remove the libdnf dups at the rpm level, and/or reinstall dnf itself? In which case, I would need to find the rpms - would they still be cached on my system somewhere?

            – lvc
            Sep 7 '17 at 13:39













            0














            I got past the Python exception by booting from a live USB, and using dnf --installroot=/mnt/fedora; the package conflicts kept coming, including errors when I tried to dnf remove --duplicates or even trying to remove packages one-by-one. So I ended up deciding the system was not fixable, and reinstalling Fedora - along with finally getting around to setting up snapper so there's an easy fix next time something like this happens.






            share|improve this answer



























              0














              I got past the Python exception by booting from a live USB, and using dnf --installroot=/mnt/fedora; the package conflicts kept coming, including errors when I tried to dnf remove --duplicates or even trying to remove packages one-by-one. So I ended up deciding the system was not fixable, and reinstalling Fedora - along with finally getting around to setting up snapper so there's an easy fix next time something like this happens.






              share|improve this answer

























                0












                0








                0







                I got past the Python exception by booting from a live USB, and using dnf --installroot=/mnt/fedora; the package conflicts kept coming, including errors when I tried to dnf remove --duplicates or even trying to remove packages one-by-one. So I ended up deciding the system was not fixable, and reinstalling Fedora - along with finally getting around to setting up snapper so there's an easy fix next time something like this happens.






                share|improve this answer













                I got past the Python exception by booting from a live USB, and using dnf --installroot=/mnt/fedora; the package conflicts kept coming, including errors when I tried to dnf remove --duplicates or even trying to remove packages one-by-one. So I ended up deciding the system was not fixable, and reinstalling Fedora - along with finally getting around to setting up snapper so there's an easy fix next time something like this happens.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Sep 12 '17 at 10:11









                lvclvc

                20628




                20628





















                    -1














                    after every package(uptodate) ready,



                    vi /etc/dnf/dnf.conf



                    [main]
                    gpgcheck=1
                    installonly_limit=3
                    clean_requirements_on_remove=True
                    exactarch=1 ##<--add line this


                    after save to $(prompt)



                    dnf clean all



                    dnf update






                    share|improve this answer








                    New contributor




                    Jungsuep Yoon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                    Check out our Code of Conduct.




















                    • would be pleased, paste[solved]; thanks

                      – Jungsuep Yoon
                      1 hour ago















                    -1














                    after every package(uptodate) ready,



                    vi /etc/dnf/dnf.conf



                    [main]
                    gpgcheck=1
                    installonly_limit=3
                    clean_requirements_on_remove=True
                    exactarch=1 ##<--add line this


                    after save to $(prompt)



                    dnf clean all



                    dnf update






                    share|improve this answer








                    New contributor




                    Jungsuep Yoon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                    Check out our Code of Conduct.




















                    • would be pleased, paste[solved]; thanks

                      – Jungsuep Yoon
                      1 hour ago













                    -1












                    -1








                    -1







                    after every package(uptodate) ready,



                    vi /etc/dnf/dnf.conf



                    [main]
                    gpgcheck=1
                    installonly_limit=3
                    clean_requirements_on_remove=True
                    exactarch=1 ##<--add line this


                    after save to $(prompt)



                    dnf clean all



                    dnf update






                    share|improve this answer








                    New contributor




                    Jungsuep Yoon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                    Check out our Code of Conduct.










                    after every package(uptodate) ready,



                    vi /etc/dnf/dnf.conf



                    [main]
                    gpgcheck=1
                    installonly_limit=3
                    clean_requirements_on_remove=True
                    exactarch=1 ##<--add line this


                    after save to $(prompt)



                    dnf clean all



                    dnf update







                    share|improve this answer








                    New contributor




                    Jungsuep Yoon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                    Check out our Code of Conduct.









                    share|improve this answer



                    share|improve this answer






                    New contributor




                    Jungsuep Yoon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                    Check out our Code of Conduct.









                    answered 1 hour ago









                    Jungsuep YoonJungsuep Yoon

                    11




                    11




                    New contributor




                    Jungsuep Yoon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                    Check out our Code of Conduct.





                    New contributor





                    Jungsuep Yoon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                    Check out our Code of Conduct.






                    Jungsuep Yoon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                    Check out our Code of Conduct.












                    • would be pleased, paste[solved]; thanks

                      – Jungsuep Yoon
                      1 hour ago

















                    • would be pleased, paste[solved]; thanks

                      – Jungsuep Yoon
                      1 hour ago
















                    would be pleased, paste[solved]; thanks

                    – Jungsuep Yoon
                    1 hour ago





                    would be pleased, paste[solved]; thanks

                    – Jungsuep Yoon
                    1 hour ago

















                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid …


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f390367%2fdnf-error-conflicting-packages-between-i686-and-x86-64%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    -

                    Popular posts from this blog

                    Frič See also Navigation menuinternal link

                    Image
                    SurnamesCzech-language surnames ‹ The template Infobox surname is being considered for merging. › Frič Origin Language(s) Czechized German (eastern Middle German dialects and Alemannic German) - Thuringian, Upper Saxon, Low Lusatian, Silesian Meaning derived from German: Friedrich Other names Variant(s) Fritsch, Fritzsch, Frycz, Fricz, Fryczyński, Frietsch, Fritsche, Fritzsche; Fritschi (Alemannic), Fritz, Fritze, Fritzel, Fritzl, Fritzke, Fritzen Frič is a Czechized German surname. Notable people with the surname include: Alberto Vojtěch Frič, Czech botanist Antonín Jan Frič (Fritsch) , Czech paleontologist Jaroslav Erik Frič, Czech poet Martin Frič, Czech film director, screenwriter and actor See also Fričovce (Hungarian: Frics ) .mw-parser-output table.dmboxclear:both;margin:0.9em 1em;border-top:1px solid #ccc;border-bottom:1px solid #ccc;background-color:transparent Surname list This page lists people with the surname Frič . If an internal link intending to refer to a specifi
                    Read more

                    Identify plant with long narrow paired leaves and reddish stems Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is this plant with long sharp leaves? Is it a weed?What is this 3ft high, stalky plant, with mid sized narrow leaves?What is this young shrub with opposite ovate, crenate leaves and reddish stems?What is this plant with large broad serrated leaves?Identify this upright branching weed with long leaves and reddish stemsPlease help me identify this bulbous plant with long, broad leaves and white flowersWhat is this small annual with narrow gray/green leaves and rust colored daisy-type flowers?What is this chilli plant?Does anyone know what type of chilli plant this is?Help identify this plant

                    Image
                    Apollo command module space walk? prime numbers and expressing non-prime numbers Can a non-EU citizen traveling with me come with me through the EU passport line? Extract all GPU name, model and GPU ram How to deal with a team lead who never gives me credit? Why was the term "discrete" used in discrete logarithm? Why do we bend a book to keep it straight? When do you get frequent flier miles - when you buy, or when you fly? How come Sam didn't become Lord of Horn Hill? At the end of Thor: Ragnarok why don't the Asgardians turn and head for the Bifrost as per their original plan? Is it true that "carbohydrates are of no use for the basal metabolic need"? Using et al. for a last / senior author rather than for a first author How to tell that you are a giant? How to react to hostile behavior from a senior developer? String `!23` is replaced with `docker` in command line How to find out what spells would be useless to a blind NPC sp
                    Read more

                    fontconfig warning: “/etc/fonts/fonts.conf”, line 100: unknown “element blank” The 2019 Stack Overflow Developer Survey Results Are In“tar: unrecognized option --warning” during 'apt-get install'How to fix Fontconfig errorHow do I figure out which font file is chosen for a system generic font alias?Why are some apt-get-installed fonts being ignored by fc-list, xfontsel, etc?Reload settings in /etc/fonts/conf.dTaking 30 seconds longer to boot after upgrade from jessie to stretchHow to match multiple font names with a single <match> element?Adding a custom font to fontconfigRemoving fonts from fontconfig <match> resultsBroken fonts after upgrading Firefox ESR to latest Firefox

                    Image
                    How to type this arrow in math mode? Multiply Two Integer Polynomials What do hard-Brexiteers want with respect to the Irish border? Why isn't the circumferential light around the M87 black hole's event horizon symmetric? For what reasons would an animal species NOT cross a *horizontal* land bridge? Can one be advised by a professor who is very far away? Identify boardgame from Big movie slides for 30min~1hr skype tenure track application interview Why do we hear so much about the Trump administration deciding to impose and then remove tariffs? If I score a critical hit on an 18 or higher, what are my chances of getting a critical hit if I roll 3d20? Can we generate random numbers using irrational numbers like π and e? Worn-tile Scrabble Output the Arecibo Message What is the meaning of Triage in Cybersec world? How are circuits which use complex ICs normally simulated? Shouldn't "much" here be used instead of "more"? Dele
                    Read more