Bug 986959

This prevents installing the 64-bit server and the 32-bit devel package as well.

Created attachment 777823 [details]
Changes against current Fedora 19 mariadb.spec

Since the mysql_config and mysqlbug scripts/binaries moved to %{_libdir}/mysql/ the only thing to do is to not install a static symlink, use alternatives instead. It makes the mariadb packages co-installable.

Thanks for the report, I've reverted a solutions that uses wrapper binary instead of alternatives.

mariadb-5.5.32-6.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/mariadb-5.5.32-6.fc19

(In reply to Honza Horak from comment #3)
> Thanks for the report, I've reverted a solutions that uses wrapper binary
> instead of alternatives.

Sorry, but this solution wouldn't work in a satisfactory way.

Both the i686 and x86_64 packages contain the mysql_config (scriptstub) binary.
The 64-bit is preferred at installation time, so the 32-bit one is lost.
There is no way to say

   alternatives  --set mysql_config /usr/lib/mysql/mysql_config

and then build 32-bit software that happens to use the MySQL/MariaDB client library.

The scriptstub.c contains a statically compiled-in path to point to the real script and doesn't distinguish between e.g. setach i386 and native mode.

pkg-config at least parses PKG_CONFIG_PATH and make it preferred so there is a way to build 32-bit software using regular infrastructure and 32-bit *-devel packages.

"mock" just isn't applicable when you need to compile an ad-hoc in-house piece of software without an RPM spec file.

The way I modified mariadb.spec (for the 5.5.31-4 version) is almost the same what the LLVM spec file has. llvm-config is renamed in %install this way:

mv %{buildroot}%{_bindir}/llvm-config{,-%{__isa_bits}}

Since the original %{buildroot}%{_bindir}/mysql_config is moved to %{buildroot}%{_libdir} , only the call to "alternatives --install ..." is needed.

Now THIS would allow building both 32 and 64-bit software separately.

Package mariadb-5.5.32-6.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mariadb-5.5.32-6.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-14040/mariadb-5.5.32-6.fc19
then log in and leave karma (feedback).

I have tested mariadb-5.5.32-6.fc19 from updates-testing and it indeed solves the letter of the report but loses the spirit of multilib -devel packages.

After installing both the i686 and x86_64 mariadb-devel packages, the ability to compile for 32-bit is lost. My spec file modification attached to this bug report allowed that by using alternatives.

I've issued a new build that uses alternatives-way to handle multilib problems:
https://admin.fedoraproject.org/updates/FEDORA-2013-14040/mariadb-5.5.32-8.fc19

Feel free to test.

Package mariadb-5.5.32-8.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mariadb-5.5.32-8.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-14040/mariadb-5.5.32-8.fc19
then log in and leave karma (feedback).

(In reply to Honza Horak from comment #8)
> I've issued a new build that uses alternatives-way to handle multilib
> problems:
> https://admin.fedoraproject.org/updates/FEDORA-2013-14040/mariadb-5.5.32-8.
> fc19
> 
> Feel free to test.

I just tested it. Thanks very much, it works. This bug can be closed.

mariadb-5.5.32-8.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.