Fedora Account System
Red Hat Associate
Red Hat Customer
gpgme (or one of its subpacakges) has multiarch conflicts when installed for both i386 and x86_64 in the Fedora development tree. For help in resolving them, see http://fedoraproject.org/wiki/PackagingDrafts/MultilibTricks. file /usr/bin/gpgme-config from install of gpgme-devel-1.1.5-4.fc8 conflicts with file from package gpgme-devel-1.1.5-4.fc8 (Note that this is an automated bug filing.) It would be nice to have these bugs fixed by the beta of Fedora 9.
%changelog * Fri Jan 04 2008 Rex Dieter <rdieter[AT]fedoraproject.org> 1.1.6-1 - gpgme-1.1.6 - multiarch conflicts in gpgme (#341351)
As I see it, this issue has been reintroduced in gpgme at some point of time. Both gpgme-config and gpgme.h conflict in gpgme-devel.i686 and gpgme-devel.x86_64
I am afraid that this conflict - at least in gpgme-config - is unresolvable. There is no way how to tell the gpgme-config which arch should be used for the CFLAGS and LDFLAGS output. And due to the now resolved bug 621698 the output is really different on the 32bit and 64bit architectures.
Could it be ported to pkg-config, with files in %{_libdir}/pkgconfig, and have gpgme-config just call that?
Except that wouldn't solve the problem that gpgme-config output for the 32 bit arch on the 64bit would be incorrect. But yes, it would solve the file conflict.
or we could have gpgme-config.<arch> binaries and just call the right one with a wrapper if needed, one quick-n-dirty one: exec gpgme-config.$(arch) (but largely has the same problems as comment #5, though that case is not something handled very well in general on fedora anyway).
I would think either of the solutions from comment #5 or comment #6 could operate conditionally on uname output well enough that it should work as long as setarch is called.
gpgme-1.3.0-6.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/gpgme-1.3.0-6.fc17
Package gpgme-1.3.0-6.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gpgme-1.3.0-6.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-1726/gpgme-1.3.0-6.fc17 then log in and leave karma (feedback).
Further fixes are needed, so this is _the_ chance to include them: https://fedoraproject.org/wiki/Packaging:Guidelines#Requiring_Base_Package On x86_64: $ yum install gpgme-devel.i686 [...] ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: gpgme-devel i686 1.3.0-6.fc17 updates-testing 111 k Installing for dependencies: glibc i686 2.15-11.fc17 fedora 4.1 M gpgme i686 1.3.0-6.fc17 updates-testing 147 k libassuan i686 2.0.1-2.fc17 fedora 59 k libgpg-error i686 1.10-2.fc17 fedora 75 k libgpg-error-devel x86_64 1.10-2.fc17 fedora 15 k nss-softokn-freebl i686 3.13.1-20.fc17 fedora 123 k pth i686 2.0.7-15.fc17 fedora 86 k # rpm -e libgpg-error-devel.x86_64 error: Failed dependencies: libgpg-error-devel is needed by (installed) gpgme-devel-1.3.0-6.fc17.i686 # rpm -qR gpgme-devel.i686 /bin/sh /bin/sh /bin/sh /sbin/install-info /sbin/install-info gpgme = 1.3.0-6.fc17 libgpg-error-devel libgpgme-pth.so.11 libgpgme-pthread.so.11 libgpgme.so.11 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsXz) <= 5.2-1
Package gpgme-1.3.0-8.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gpgme-1.3.0-8.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-1726/gpgme-1.3.0-8.fc17 then log in and leave karma (feedback).
gpgme-1.3.0-8.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.