mplayer dependencies
I am having trouble installing mplayer rpms on my machine. Currently running RH9. I am running into dependecies problems: # rpm -Uvh mplayer-common-0. 92-1. i386. rpm error: Failed dependencies: mplayer = 0.
I am having trouble installing mplayer rpms on my machine. Currently running RH9.
I am running into dependecies problems:
[root@localhost mplayer]# rpm -Uvh mplayer-common-0.92-1.i386.rpm
error: Failed dependencies:
mplayer = 0.92 is needed by mplayer-common-0.92-1
So then I will run:
[root@localhost mplayer]# rpm -Uvh mplayer-0.92-1.i386.rpm
error: Failed dependencies:
mplayer-common = 0.92 is needed by mplayer-0.92-1
Each one is calling for the other one. It is like a never ending circle. Can someone please help.
I am running into dependecies problems:
[root@localhost mplayer]# rpm -Uvh mplayer-common-0.92-1.i386.rpm
error: Failed dependencies:
mplayer = 0.92 is needed by mplayer-common-0.92-1
So then I will run:
[root@localhost mplayer]# rpm -Uvh mplayer-0.92-1.i386.rpm
error: Failed dependencies:
mplayer-common = 0.92 is needed by mplayer-0.92-1
Each one is calling for the other one. It is like a never ending circle. Can someone please help.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Isn't RPM wonderful? It was crap like that that forced RH8.0 off my machine and made me vow never to install another RPM-based distro again.
If you really want to persist with Red Hat and RPM though you could try using the force parameter (-f I think but check the RPM man page) on both packages to tell RPM to ignore the failed dependencies and install them anyway.
If you really want to persist with Red Hat and RPM though you could try using the force parameter (-f I think but check the RPM man page) on both packages to tell RPM to ignore the failed dependencies and install them anyway.
Using the force option is now a good idea.
Instead download YUM from http://shrike.freshrpms.net/rpm.html?id=1559 and change the /etc/yum.conf like this:
Code:
Now you can run yum install mplayer to install mplayer
Instead download YUM from http://shrike.freshrpms.net/rpm.html?id=1559 and change the /etc/yum.conf like this:
Code:
[main]cachedir=/var/cache/yumdebuglevel=2logfile=/var/log/yum.logpkgpolicy=newestdistroverpkg=redhat-releasegpgcheck=1tolerant=1exactarch=1[os]name=Red Hat Linux $releasever - $basearch - osbaseurl=http://ayo.freshrpms.net/redhat/$releasever/$basearch/os[updates]name=Red Hat Linux $releasever - $basearch - updatesbaseurl=http://ayo.freshrpms.net/redhat/$releasever/$basearch/updates[freshrpms]name=Red Hat Linux $releasever - $basearch - freshrpmsbaseurl=http://ayo.freshrpms.net/redhat/$releasever/$basearch/freshrpms
Now you can run yum install mplayer to install mplayer
A better solution would be the people creating the RPMs getting a bit of sense and supplying stuff like this as a single package instead of trying to split it up into as many components as possible regardless of whether or not those components are useful on their own. This isn't such a bad thing in packages such as Samba or MySQL, which allow you to seperate the server from the client, but with mplayer and the Mozilla packages I had so much trouble with it's just ridiculous. YUM doesn't eliminate the problem (you'll probably find it calls RPM with -f to deal with it itself) it just sweeps it under the carpet.