Fedora 20: How to resolve dependency resolution errors with `librtmp`?
Doing a yum update
gives me the ff. dependency resolution messages:
--> Finished Dependency Resolution
Error: Package: mencoder-1.1-16.20131125svn.fc20.x86_64 (@rpmfusion-free)
Requires: librtmp.so.0()(64bit)
Removing: librtmp-2.4-0.3.20110811gitc58cfb3e.fc19.x86_64 (@rpmfusion-free)
librtmp.so.0()(64bit)
Updated By: librtmp-2.4-1.20131205.gitdc76f0a.fc20.x86_64 (rpmfusion-free-updates)
~librtmp.so.1()(64bit)
Error: Package: mplayer-1.1-16.20131125svn.fc20.x86_64 (@rpmfusion-free)
Requires: librtmp.so.0()(64bit)
Removing: librtmp-2.4-0.3.20110811gitc58cfb3e.fc19.x86_64 (@rpmfusion-free)
librtmp.so.0()(64bit)
Updated By: librtmp-2.4-1.20131205.gitdc76f0a.fc20.x86_64 (rpmfusion-free-updates)
~librtmp.so.1()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Being new to Fedora, I don't know how to go about this. Some questions:
- If I use
--skip-broken
flag, then yum will not updatelibrtmp
and leave it to version 2.4-0.3. I just have to wait for RPMFusion to getmencoder
andmplayer
updated with usinglibrtmp-2.4-1...
package and ayum update
will resolve this error. Is this line of thinking correct? - I have no idea what
rpm -Va --nofiles --nodigest
does...can someone care to explain?
Yum gives you a bad advice (--skip-broken or using rpm directly, i think these error messages should be improved because they confuse users too often). As always in case of yum problems do first:
yum clean all; yum repolist
- are all repos enabled as expected? See for a similar problem here https://ask.fedoraproject.org/question/29534/a-problem-in-installing-spe-python-editor/I'm still getting the same error messages after doing
yum clean all
andyum repolist
. AFAIK, I didn't disable any repos, and added onlyadobe-linux
and therpmfusion*
repos. Looking closely at the error, it's trying to update fromlibrtmp-2.4-0.3.20110811gitc58cfb3e.fc19.x86_64
tolibrtmp-2.4-1.20131205.gitdc76f0a.fc20.x86_64
, so should I just wait for maintainers ofmencoder
andmplayer
to fix this?I see this is indeed inconsistency between the mplayer/mencoder from rpmfusion-free and librtmp from rpmfusion-free-updates -
yum update librtmp
triggers your error. Follow one of the answers below depending on your temperament - or simply wait withyum update
a couple of days, applying only critical updatesFor "rpm -Va --nofiles --nodigest" - see man rpm, section "VERIFY OPTIONS" - the command "verifies" all packages (-a option combined with -V)
I'm dealing with a similar issue with npm & nodejs; though, I do have librtmp already installed, seemingly from a 3rd-party source--since yum simply says
Repo: installed
. I suppose it's as simple as waiting it out, since newest doesn't always mean greatest.