Description of problem: Attempting to upgrade this system gives error messages (see below). Version-Release number of selected component (if applicable): see below How reproducible: always Steps to Reproduce: 1.dnf -y --best upgrade 2. 3. Actual results: see error messages below Expected results: clean successful system upgrade Additional info: Why does DNF issue these suggestions that have NEVER worked for me? Running transaction check Error: transaction check vs depsolve: mariadb-server(x86-64) = 3:10.2.11-1.fc28 is needed by (installed) mariadb-tokudb-engine-3:10.2.11-1.fc28.x86_64 To diagnose the problem, try running: 'rpm -Va --nofiles --nodigest'. You probably have corrupted RPMDB, running 'rpm --rebuilddb' might fix the issue. f list mariadb-server Last metadata expiration check: 0:20:22 ago on Thu 25 Jan 2018 05:07:58 PM PST. Installed Packages mariadb-server.x86_64 3:10.2.12-2.fc28 @rawhide Available Packages mariadb-server.x86_64 3:10.2.12-3.fc28 rawhide bash 4.4 ~# rpm -qa | grep mariadb- mariadb-java-client-javadoc-2.2.1-1.fc28.noarch mariadb-embedded-10.2.12-2.fc28.x86_64 mariadb-rocksdb-engine-10.2.12-2.fc28.x86_64 mariadb-connector-c-devel-3.0.2-21.fc28.x86_64 mariadb-10.2.12-2.fc28.x86_64 mariadb-common-10.2.12-2.fc28.x86_64 mariadb-server-utils-10.2.12-2.fc28.x86_64 mariadb-devel-10.2.12-2.fc28.x86_64 mariadb-cracklib-password-check-10.2.12-2.fc28.x86_64 mariadb-embedded-devel-10.2.12-2.fc28.x86_64 mariadb-errmsg-10.2.12-2.fc28.x86_64 mariadb-bench-10.2.12-2.fc28.x86_64 mariadb-connect-engine-10.2.12-2.fc28.x86_64 mariadb-gssapi-server-10.2.12-2.fc28.x86_64 mariadb-server-10.2.12-2.fc28.x86_64 mariadb-connector-c-3.0.2-21.fc28.x86_64 mariadb-test-10.2.12-2.fc28.x86_64 mariadb-oqgraph-engine-10.2.12-2.fc28.x86_64 mariadb-connector-odbc-3.0.1-2.fc28.x86_64 mariadb-java-client-2.2.1-1.fc28.noarch mariadb-server-galera-10.2.12-2.fc28.x86_64 mariadb-config-10.2.12-2.fc28.x86_64 mariadb-tokudb-engine-10.2.11-1.fc28.x86_64 mariadb-sphinx-engine-10.2.12-2.fc28.x86_64 mariadb-backup-10.2.12-2.fc28.x86_64
Can you please test the 10.2.12-4 https://koji.fedoraproject.org/koji/taskinfo?taskID=24443141 update? It landed in Rawhide tonight, so it can take day or two to propagate to all mirrors.
Created attachment 1386629 [details] tar.gz of flat file of rpm activity Michal, I could add the --force option but am not sure that it's the right thing to do or whether it would work. George...
My interest is to solve this issue purely by fixing upgrade path - so no 'force' options should be required. After you download all the RPMs you want to a direcotry, you should be able to: # dnf install ./*rpm and end up with DNF telling you that there's no update issue and asking whether to continue. -- The "rpm -ivh" command can't handle updates, so it tells you correctly that all the files from already-installed and being-installed RPMs conflists. If you really want to do the update with 'rpm', instead of 'dnf', you need to specify different arguments, like "rpm -U": http://ftp.rpm.org/max-rpm/ch-rpm-upgrade.html
Michal, I'm happy to report that "dnf upgrade maria*.rpm" has succeeded. Good work and thanks for your hard work and help! George...