Ask Your Question
0

Error: Package: libx264_130-0.130-18_20130509.2245.fc20.x86_64

asked 2014-12-26 00:02:46 -0600

this post is marked as community wiki

This post is a wiki. Anyone with karma >750 is welcome to improve it.

I am having a problem with updating Yum, also when fedora send me updates and i update this libx264 package shows problem

sudo yum update
Loaded plugins: langpacks, refresh-packagekit, tmprepo
Existing lock /var/run/yum.pid: another copy is running as pid 2706.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: PackageKit
    Memory : 120 M RSS (436 MB VSZ)
    Started: Fri Dec 26 07:54:21 2014 - 00:59 ago
    State  : Uninterruptible, pid: 2706
Resolving Dependencies
--> Running transaction check
---> Package MariaDB-Galera-server.x86_64 0:10.0.14-1.fc20 will be updated
---> Package MariaDB-Galera-server.x86_64 0:10.0.15-1.fc20 will be an update
---> Package MariaDB-client.x86_64 0:10.0.14-1.fc20 will be updated
---> Package MariaDB-client.x86_64 0:10.0.15-1.fc20 will be an update
---> Package MariaDB-common.x86_64 0:10.0.14-1.fc20 will be updated
---> Package MariaDB-common.x86_64 0:10.0.15-1.fc20 will be an update
---> Package MariaDB-shared.x86_64 0:10.0.14-1.fc20 will be updated
---> Package MariaDB-shared.x86_64 0:10.0.15-1.fc20 will be an update
---> Package NetworkManager.x86_64 1:0.9.9.0-44.git20131003.fc20 will be updated
---> Package NetworkManager.x86_64 1:0.9.9.0-46.git20131003.fc20 will be an update
---> Package NetworkManager-glib.x86_64 1:0.9.9.0-44.git20131003.fc20 will be updated
---> Package NetworkManager-glib.x86_64 1:0.9.9.0-46.git20131003.fc20 will be an update
---> Package akregator.x86_64 0:4.14.2-1.fc20 will be updated
---> Package akregator.x86_64 0:4.14.3-1.fc20 will be an update
---> Package akregator-libs.x86_64 0:4.14.2-1.fc20 will be updated
---> Package akregator-libs.x86_64 0:4.14.3-1.fc20 will be an update
---> Package apper.x86_64 0:0.8.2-2.fc20 will be updated
---> Package apper.x86_64 0:0.8.2-3.fc20 will be an update
---> Package ark.x86_64 0:4.14.2-1.fc20 will be updated
---> Package ark.x86_64 0:4.14.3-2.fc20 will be an update
---> Package ark-libs.x86_64 0:4.14.2-1.fc20 will be updated
---> Package ark-libs.x86_64 0:4.14.3-2.fc20 will be an update
---> Package at.x86_64 0:3.1.13-14.fc20 will be updated
---> Package at.x86_64 0:3.1.13-15.fc20 will be an update
---> Package atlas.x86_64 0:3.8.4-12.fc20 will be updated
---> Package atlas.x86_64 0:3.8.4-13.fc20 will be an update
---> Package audit.x86_64 0:2.4-1.fc20 will be updated
---> Package audit.x86_64 0:2.4.1-1.fc20 will be an update
---> Package audit-libs.i686 0:2.4-1.fc20 will be updated
---> Package audit-libs.x86_64 0:2.4-1.fc20 will be updated
---> Package audit-libs.i686 0:2.4.1-1.fc20 will be an update
---> Package audit-libs.x86_64 0:2.4.1-1.fc20 will be an update
---> Package audit-libs-python.x86_64 0:2.4-1.fc20 will be updated
---> Package audit-libs-python.x86_64 0:2.4.1-1.fc20 will be an update
---> Package autocorr-en.noarch 1:4.2.7.2-6.fc20 will be updated
---> Package autocorr-en.noarch 1:4 ...
(more)
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2014-12-26 09:39:44 -0600

cobra gravatar image

updated 2014-12-26 09:48:24 -0600

It looks a bit like a problem with conflicting repositories. Check which 3rd party repositories you have installed and make sure that they don't conflict with each other.

Also I can't see a reason why the 64 bit version of libx264 is causing a problem with uninstalling the 32bit glibc. It could be that there is a problem with the build of the packages themselves. If this is the problem, then it should be resolved by the maintainers in a few days - if it isn't you could try raising a bug against the repository that carries the broken .rpm file.

Note: on my Fedora 64 bit system there is no package libx264 available or installed. The only additional repos I'm using are the rpmfusion repository, Adobe flash repository and the Google Chrome repository.

Did you try the --skip-broken option, as it suggests:

sudo yum update --skip-broken

which should do as much of the update as it can, but miss out the broken files.

edit flag offensive delete link more

Comments

I tried sudo yum update --skip-broken

I got this error: 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 mesa-filesystem which is missing some
        dependency that another package requires. Yum is trying to
        solve this by installing an older version of mesa-filesystem 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 mesa-filesystem.otherarch ... this should give you an error
        message showing the root cause of the problem.

     2. You have multiple architectures of mesa-filesystem installed, but
        yum can only see an upgrade for one of those architectures.
        If you don't want/need both architectures anymore then you
        can remove the one ...
(more)
Alig2x gravatar imageAlig2x ( 2015-01-11 18:28:08 -0600 )edit

Question Tools

1 follower

Stats

Asked: 2014-12-26 00:02:46 -0600

Seen: 190 times

Last updated: Dec 26 '14