Description of problem: When running: yum install libyaz-devel the corresponding output is: " .... --> Finished Dependency Resolution Error: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing out that there is a problem. Eg.: 1. You have an upgrade for libgcrypt which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of libgcrypt of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). You can try redoing the upgrade with --exclude libgcrypt.otherarch ... this should give you an error message showing the root cause of the problem. 2. You have multiple architectures of libgcrypt installed, but yum can only see an upgrade for one of those arcitectures. If you don't want/need both architectures anymore then you can remove the one with the missing update and everything will work. 3. You have duplicate versions of libgcrypt installed already. You can use "yum check" to get yum show these errors. ...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems). Protected multilib versions: libgcrypt-1.5.0-6.fc18.i686 != libgcrypt-1.5.0-8.fc18.x86_64 " Then it failed on installing libyaz-devel. Version-Release number of selected component (if applicable): yum-3.4.3-47.fc18.noarch rpm-4.10.2-1.fc18.x86_64 libgcrypt-1.5.0-8.fc18.x86_64 How reproducible: Steps to Reproduce: 1. Having Fedora 18 installed. 2. Run: yum install libyaz-devel 3. Actual results: Error: Multilib version problems found Expected results: yum can install libyaz-devel. Additional info:
Created attachment 670739 [details] Output of "yum install libyaz-devel"
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.