[MDEV-18345] Installation of galera-4 RPM fails when older galera is present Created: 2019-01-23 Updated: 2019-01-27 Resolved: 2019-01-27 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera, Packaging |
| Affects Version/s: | 10.4 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
galera-4 should either replace galera-25.3.x or co-exist with it. Now it does neither. |
| Comments |
| Comment by Elena Stepanova [ 2019-01-23 ] | |||||||||||||||||||||||||||||||||||||
|
Strangely, it didn't fail on Fedora28/29. I don't know what's the difference is. | |||||||||||||||||||||||||||||||||||||
| Comment by Sergei Golubchik [ 2019-01-27 ] | |||||||||||||||||||||||||||||||||||||
|
Both systems do
with a similar result
and both do
But on fedora28 it's
While on CentOS 7.3 it's
As you can see, CentOS does not remove dependent packages, so galera stays installed and conflicts with the galera-4, when MariaDB 10.4 tries to pull it in. This behavior is configured in yum.conf (or dnf.conf), with clean_requirements_on_remove setting. Which is True on fedora28 and unset on CentOS 73. As a fix we could either use yum autoremove, which removes a package and all dependencies. Or set clean_requirements_on_remove in CentOS 7.3 images. I'll try the first fix now. | |||||||||||||||||||||||||||||||||||||
| Comment by Sergei Golubchik [ 2019-01-27 ] | |||||||||||||||||||||||||||||||||||||
|
autoremove worked |