Bug 1545433
| Summary: | [mariadb-server] dependency resolves to community-mysql and fails to install | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Carl George <carl> |
| Component: | mariadb | Assignee: | Michal Schorm <mschorm> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 28 | CC: | ben.harper, dciabrin, hhorak, jmracek, jstanek, mbayer, mkocka, mmuzila, mschorm, praiskup, terje.rosten |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-05 13:59:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
my_print_defaults should moved to community-mysql-server I think. Other thing is that server should not require mysql(x86-64) at all, there is no need for client for server to start. (in pre systemd days mysqladmin was used in initscript to check server was up, however there is no such need any longer). Two separate issues: 1) I try to make mariadb and mysql installable together in a matrix of ways. I'll move the files to the correct location, so they won't confict 2) Why the docker DNF like coomunity-mysql client more, I can't tell for now. Yeah it would be nice if dnf had additional flags to show more insight into resolution logic. See also: https://bugzilla.redhat.com/show_bug.cgi?id=1148627 This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'. The first issue was solved by an update I made for community-mysql package, fixing confilcting files. The second issue is still a mystery, however it is not a severe issue anymore. Leaving this bugzilla open to find out. In the fresh docker container, if you run first this update: dnf update -y --nogpgcheck gdbm openssl-libs Then mariadb-server will resolve correctly dnf install --assumeno mariadb-server I think that the file conflict should be solved on packaging level. If there are two packages that provides same file, but checksum of those files is different (always if they are from different srpm), there should be a conflict in spec. Like: "Conflicts: community-mysql" (in mariadb-server). I believe that solution in Comment 6 is based on new weak deps in updated packages, but this is an only guess. Should be fixed now. Can you confirm it for me please? Yes, it works now. Thanks! No problem, enjoy :) -- Unfortunatelly it took so long. Sorry for that. The issue - i believe - was hidden in the exact version of OpenSSL both databases was built with. DNF then prefered a combination, that required less changes in the system (e.g. not updating OpenSSL package). With combination of weak dependencies it resolved in such a way. That's why update of the system solved the issue (the OpenSSL package was updated too) And that's why it wasn't reproducible in base Fedora, where the OpenSSL package was already updated. The container image holds an old version. |
Description of problem: Installing mariadb-server in a Rawhide container resolves some dependencies to community-mysql, which has conflicting files with mariadb-server. Version-Release number of selected component (if applicable): mariadb-server-3:10.2.12-5.fc28 community-mysql-5.7.21-1.fc28 Steps to Reproduce: 1. docker run -it --rm registry.fedoraproject.org/fedora:28 2. dnf install mariadb-server Actual results: Fedora - Rawhide - Developmental packages for 899 kB/s | 60 MB 01:08 Last metadata expiration check: 0:01:04 ago on Wed Feb 14 21:53:26 2018. Dependencies resolved. =============================================================================== Package Arch Version Repository Size =============================================================================== Installing: mariadb-server x86_64 3:10.2.12-5.fc28 rawhide 18 M Upgrading: glibc x86_64 2.26.9000-51.fc28 rawhide 3.6 M glibc-common x86_64 2.26.9000-51.fc28 rawhide 770 k glibc-langpack-en x86_64 2.26.9000-51.fc28 rawhide 296 k Installing dependencies: bison x86_64 3.0.4-8.fc27 rawhide 684 k community-mysql x86_64 5.7.21-1.fc28 rawhide 8.4 M community-mysql-common x86_64 5.7.21-1.fc28 rawhide 94 k iproute x86_64 4.14.1-4.fc28 rawhide 531 k libaio x86_64 0.3.110-10.fc28 rawhide 29 k libedit x86_64 3.1-21.20170329cvs.fc28 rawhide 100 k libmnl x86_64 1.0.4-4.fc27 rawhide 28 k libnsl x86_64 2.26.9000-51.fc28 rawhide 82 k libxcrypt x86_64 4.0.0-3.fc28 rawhide 77 k replacing libcrypt-nss.x86_64 2.26.9000-26.fc28 linux-atm-libs x86_64 2.5.1-19.fc27 rawhide 40 k m4 x86_64 1.4.18-5.fc27 rawhide 219 k mariadb-common x86_64 3:10.2.12-5.fc28 rawhide 57 k mariadb-config x86_64 3:10.2.12-5.fc28 rawhide 38 k mariadb-errmsg x86_64 3:10.2.12-5.fc28 rawhide 226 k psmisc x86_64 23.1-2.fc27 rawhide 148 k Installing weak dependencies: iproute-tc x86_64 4.14.1-4.fc28 rawhide 382 k mariadb-backup x86_64 3:10.2.12-5.fc28 rawhide 5.9 M mariadb-gssapi-server x86_64 3:10.2.12-5.fc28 rawhide 44 k mariadb-rocksdb-engine x86_64 3:10.2.12-5.fc28 rawhide 4.3 M mariadb-tokudb-engine x86_64 3:10.2.12-5.fc28 rawhide 837 k Transaction Summary =============================================================================== Install 21 Packages Upgrade 3 Packages Total download size: 44 M Is this ok [y/N]: y Downloading Packages: (1/24): iproute-4.14.1-4.fc28.x86_64.rpm 889 kB/s | 531 kB 00:00 (2/24): libaio-0.3.110-10.fc28.x86_64.rpm 290 kB/s | 29 kB 00:00 (3/24): bison-3.0.4-8.fc27.x86_64.rpm 911 kB/s | 684 kB 00:00 (4/24): libxcrypt-4.0.0-3.fc28.x86_64.rpm 533 kB/s | 77 kB 00:00 (5/24): mariadb-common-10.2.12-5.fc28.x86_64.r 487 kB/s | 57 kB 00:00 (6/24): mariadb-config-10.2.12-5.fc28.x86_64.r 365 kB/s | 38 kB 00:00 (7/24): mariadb-errmsg-10.2.12-5.fc28.x86_64.r 955 kB/s | 226 kB 00:00 (8/24): psmisc-23.1-2.fc27.x86_64.rpm 713 kB/s | 148 kB 00:00 (9/24): libmnl-1.0.4-4.fc27.x86_64.rpm 253 kB/s | 28 kB 00:00 (10/24): m4-1.4.18-5.fc27.x86_64.rpm 911 kB/s | 219 kB 00:00 (11/24): libnsl-2.26.9000-51.fc28.x86_64.rpm 591 kB/s | 82 kB 00:00 (12/24): community-mysql-common-5.7.21-1.fc28. 719 kB/s | 94 kB 00:00 (13/24): libedit-3.1-21.20170329cvs.fc28.x86_6 487 kB/s | 100 kB 00:00 (14/24): mariadb-backup-10.2.12-5.fc28.x86_64. 1.3 MB/s | 5.9 MB 00:04 (15/24): mariadb-gssapi-server-10.2.12-5.fc28. 237 kB/s | 44 kB 00:00 (16/24): community-mysql-5.7.21-1.fc28.x86_64. 1.2 MB/s | 8.4 MB 00:07 (17/24): mariadb-tokudb-engine-10.2.12-5.fc28. 1.0 MB/s | 837 kB 00:00 (18/24): iproute-tc-4.14.1-4.fc28.x86_64.rpm 954 kB/s | 382 kB 00:00 (19/24): mariadb-rocksdb-engine-10.2.12-5.fc28 1.2 MB/s | 4.3 MB 00:03 (20/24): linux-atm-libs-2.5.1-19.fc27.x86_64.r 256 kB/s | 40 kB 00:00 (21/24): glibc-common-2.26.9000-51.fc28.x86_64 1.0 MB/s | 770 kB 00:00 (22/24): glibc-langpack-en-2.26.9000-51.fc28.x 803 kB/s | 296 kB 00:00 (23/24): glibc-2.26.9000-51.fc28.x86_64.rpm 1.1 MB/s | 3.6 MB 00:03 (24/24): mariadb-server-10.2.12-5.fc28.x86_64. 1.2 MB/s | 18 MB 00:14 ------------------------------------------------------------------------------- Total 2.9 MB/s | 44 MB 00:15 Running transaction check Transaction check succeeded. Running transaction test The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Transaction check error: file /usr/bin/my_print_defaults conflicts between attempted installs of mariadb-server-3:10.2.12-5.fc28.x86_64 and community-mysql-5.7.21-1.fc28.x86_64 Error Summary ------------- Expected results: successful installation Additional info: Installing mariadb at the same time as mariadb-server is enough to complete the transaction successfully. That makes me think the root issue is related to mariadb-server requiring mysql(x86-64) instead of mariadb directly.