Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Description of problem: to crosscheck compilation with -m32 flag I need both libmaxminddb-devel arch packages installed Version-Release number of selected component (if applicable): 1.2.0-7.fc30.i686 How reproducible: always Steps to Reproduce: 1. install libmaxminddb-1.2.0-7.fc30.i686 libmaxminddb-1.2.0-7.fc30.x86_64 libmaxminddb-devel-1.2.0-7.fc30.x86_64 2. try to install libmaxminddb-devel.i686 Actual results: Error: Transaction check error: file /usr/include/maxminddb_config.h from install of libmaxminddb-devel-1.2.0-7.fc30.i686 conflicts with file from package libmaxminddb-devel-1.2.0-7.fc30.x86_64 Expected results: working well like it does on libdb, here I can install i686 and x86_64 devel in parallel: libdb-devel-5.3.28-37.fc30.i686 libdb-devel-5.3.28-37.fc30.x86_64 libdb-5.3.28-37.fc30.x86_64 libdb-5.3.28-37.fc30.i686
Hmm the mentioned config files are not equal in the RPM, that is strange...potentially this can be solved more elegant: /* include/maxminddb_config.h. Generated from maxminddb_config.h.in by configure. */ # diff -u /usr/include/maxminddb_config.h /usr/include/maxminddb_config.h.x86_64 --- /usr/include/maxminddb_config.h 2019-02-01 17:47:35.000000000 +0100 +++ /usr/include/maxminddb_config.h.x86_64 2019-02-01 17:47:26.000000000 +0100 @@ -9,7 +9,7 @@ #ifndef MMDB_UINT128_IS_BYTE_ARRAY /* Define as 1 if we don't have an unsigned __int128 type */ -#define MMDB_UINT128_IS_BYTE_ARRAY 1 +#define MMDB_UINT128_IS_BYTE_ARRAY 0 #endif #endif /* MAXMINDDB_CONFIG_H */
I am tagging this so the new package owner Igor can know this is outstanding.
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
FEDORA-2020-1fb1785fa1 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-1fb1785fa1
FEDORA-2020-8a8f8b244f has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8a8f8b244f
FEDORA-2020-1fb1785fa1 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-1fb1785fa1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-1fb1785fa1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-8a8f8b244f has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8a8f8b244f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8a8f8b244f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-1fb1785fa1 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-8a8f8b244f has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.