As described in this F40 Change proposal: https://fedoraproject.org/wiki/Changes/F40_MariaDB_MySQL_repackaging I want to stop producing i686 build of the packages 'mariadb' and 'community-mysql'. i686 packages that relies on the i686 MariaDB client library are expected to build against the 'mariadb-connector-c-devel' package instead, which will retain i686 variant. This BZ serve as a tracker of the progress of package 'mariadb' becoming "leaf" package (package no other package relies on) on i686 architecture. --- Several steps has to be done: 1. Packages that require the MariaDB client library should use mariadb-connector-c I already have a tracker BZ for this specific part, which progresses very well: https://bugzilla.redhat.com/show_bug.cgi?id=2241091 2. Packages that require MariaDB client, server or other sub-packages should either stop doing that or drop i686 builds I already created a tracker BZ for this specific part: https://bugzilla.redhat.com/show_bug.cgi?id=2245189 Reproducible: Always
I've noticed, that some name(s) provided by the 'mariadb' package is required for run-time by the following packages: mysqltuner https://src.fedoraproject.org/rpms/mysqltuner/blob/rawhide/f/mysqltuner.spec#_20 ncid-mysql https://src.fedoraproject.org/rpms/ncid/blob/rawhide/f/ncid.spec#_70 perl-DBD-MariaDB https://src.fedoraproject.org/rpms/perl-DBD-MariaDB/blob/rawhide/f/perl-DBD-MariaDB.spec#_45 The packages 'mysqltuner' and 'ncid-mysql' are "noarch", which IMO means that I don't need any action on their side. I, however, need to test that they will behave correctly after the 'mariadb' i686 builds are removed. The package 'perl-DBD-MariaDB' require 'mariadb' only for running the package test-suite during the package build-time. However since the sole purpose of this package is to be "Perl5 Database Interface driver for MariaDB and MySQL databases", there shouldn't be a problem in dropping the i686 arch for this package. The package 'perl-DBD-MariaDB' is required by package: perl-Rose-DB https://src.fedoraproject.org/rpms/perl-Rose-DB/blob/rawhide/f/perl-Rose-DB.spec#_26 which is required by package perl-Rose-DB-Object https://src.fedoraproject.org/rpms/perl-Rose-DB-Object/blob/rawhide/f/perl-Rose-DB-Object.spec#_34 However both packages 'perl-Rose-DB' and 'perl-Rose-DB-Object' are "noarch", so they should be the same case as above.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle. Changing version to 40.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.