I have a problem updating Fedora 17. When I try yum distro-sync - it fails with dependency error. When I add --skip-broken option, it also fails to resolve dependencies. What should I do to upgrade my system? Why there are packages marked x86-32? Isn't it too early for this ABI to be introduced in F17?
Here is what yum says in first case:
--> Running transaction check ---> Package libstdc++-devel.i686 0:4.7.0-5.fc17 will be installed --> Processing Dependency: libstdc++(x86-32) = 4.7.0-5.fc17 for package: libstdc++-devel-4.7.0-5.fc17.i686 ---> Package libstdc++-devel.x86_64 0:4.7.0-5.fc17 will be updated --> Finished Dependency Resolution Error: Package: libstdc++-devel-4.7.0-5.fc17.i686 (fedora) Requires: libstdc++(x86-32) = 4.7.0-5.fc17 Removing: libstdc++-4.7.0-5.fc17.i686 (@fedora) libstdc++(x86-32) = 4.7.0-5.fc17 Updated By: libstdc++-4.7.2-2.fc17.i686 (updates) libstdc++(x86-32) = 4.7.2-2.fc17 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
When I add --skip-broken as suggested yum fails with following error:
Error: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing it that there is a problem. Eg.:
1. You have an upgrade for libgfortran which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of libgfortran of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what).
2. You have multiple architectures of libgfortran 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 libgfortran 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: libgfortran-4.7.0-5.fc17.i686 != libgfortran-4.7.2-2.fc17.x86_64 Error: Protected multilib versions: libquadmath-4.7.0-5.fc17.i686 != libquadmath-4.7.2-2.fc17.x86_64 Error: Protected multilib versions: libgomp-4.7.2-2.fc17.x86_64 != libgomp-4.7.0-5.fc17.x86_64
Here is my yum repolist output:
adobe-linux-x86_64 Adobe Systems Incorporated 2 fedora Fedora 17 - x86_64 27,033 fedora-chromium-stable Builds of the "stable" tag of the Chromium Web Browser 20 rpmfusion-free RPM Fusion for Fedora 17 - Free 449 rpmfusion-free-updates RPM Fusion for Fedora 17 - Free - Updates 313 rpmfusion-nonfree RPM Fusion for Fedora 17 - Nonfree 193 rpmfusion-nonfree-updates RPM Fusion for Fedora 17 - Nonfree - Updates 193 updates Fedora 17 - x86_64 - Updates 8,915
Mateusz Marzantowicz
Do you have clang installed? If so see https://bugzilla.redhat.com/show_bug.cgi?id=860861 . You can temporarily remove clang to do the update, or install the updates-testing version, or just wait for it to get pushed to stable.
On Thu, Sep 27, 2012 at 01:02:26PM +0200, Mateusz Marzantowicz wrote:
I have a problem updating Fedora 17. When I try yum distro-sync - it fails with dependency error. When I add --skip-broken option, it also
[...]
Error: Package: libstdc++-devel-4.7.0-5.fc17.i686 (fedora)
Since this is a devel package, the easiest thing you can do to make your upgrade go smoothly is to simply remove it with yum remove. In fact, this generally goes for everything -- if a package is giving you a problem, remove it (assuming it isn't required by too many other essential things). Once the upgrade is done, you can put them back.
On 27.09.2012 15:49, Andre Robatino wrote:
Do you have clang installed? If so see https://bugzilla.redhat.com/show_bug.cgi?id=860861 . You can temporarily remove clang to do the update, or install the updates-testing version, or just wait for it to get pushed to stable.
Thanks! I removed clang package from my system (btw, it is useless in F17) and now update procedure goes smoothly.
Thank you Matthew for your suggestion about removing broken packages. I usually do this step when something is broken with updates but now I decided to wait because of number of dependent packages to be removed.
Mateusz Marzantowicz
-
Andre Robatino -
Mateusz Marzantowicz -
Matthew Miller