Description of problem: https://koji.fedoraproject.org/koji/rpminfo?rpmID=11585409 mariadb-common-3:10.2.9-2.fc28.x86_64.rpm has the following obsoletes: mariadb-common(x86-64) < 3:10.2.9-2.fc28 mariadb-galera-common < 5.5.36-10 mariadb-libs(x86-64) <= 3:10.2.9-2.fc28 Obsoletes only applies to package names, not provides. The obsoletes with the %{_isa} does not match any package names, only provides from other packages - and are therefore ignored. Updating from previous versions relies on the obsoletes on mariadb-libs to update cleanly. As it is now this obsoletes is ignored and the update fails. mariadb-common explicitly obsoleting earlier versions of itself does not make sense, that is implicit and does not need to be stated. The proper obsoletes should be: mariadb-galera-common < 5.5.36-10 mariadb-libs < 3:10.2.9-2.fc28 Version-Release number of selected component (if applicable): mariadb-common-3:10.2.9-2.fc28.x86_64.rpm How reproducible: Always Steps to Reproduce: 1. dnf update in rawhide with mariadb-devel installed Actual results: File conflict due to mariadb-libs Expected results: Old mariadb-libs removed due to obsoletes in new mariadeb-common
Hello, I understand your request only partially. I think, the following patch should be applied, however I think the "mariadb-galera-common" has right obsolete (in SPECfile) diff --git a/mariadb.spec b/mariadb.spec index 19d1845..53d7666 100644 --- a/mariadb.spec +++ b/mariadb.spec @@ -354,8 +354,7 @@ Provides: mariadb-galera-common = %{sameevr} Obsoletes: mariadb-galera-common < %{obsoleted_mariadb_galera_common_evr} %if %{without clibrary} -Obsoletes: %{name}-libs%{?_isa} <= %{sameevr} -Obsoletes: %{name}-common%{?_isa} < %{sameevr} +Obsoletes: %{name}-libs <= %{sameevr} %endif
Btw workarounf for you, till it's fixed: use "--allowerasing" dnf option
Tested, pushed, building
mariadb-10.2.9-3.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-dff1218bfa
mariadb-10.2.9-3.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-dff1218bfa
mariadb-10.2.9-3.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
mariadb-10.2.10-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-7b83201239
mariadb-10.2.10-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-7b83201239
mariadb-10.2.10-2.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
mariadb-10.2.12-5.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-66833616aa
mariadb-10.2.12-5.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-66833616aa
mariadb-10.2.12-5.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.