![]() This system is receiving updates from RHN Classic or RHN Satellite. Just regard the references to Red Hat, Inc to be an alias for CentOS and the references to Dag Apt Repository to be an alias for Repoforge and all should be clear.įor completeness, this is what is available to me ~]$ sudo yum list gstreamer\* Gstreamer-plugins-ugly Dag Apt Repository, Gstreamer-plugins-bad Dag Apt Repository, from package gstreamer-plugins-bad-free-extras-0.10.686. #HOW TO INSTALL GSTREAMER PLUGINS INSTALL#from install of gstreamer-plugins-bad-0.10.i686. I wish epel and rpmforge would talk to each other. Transaction Check Error: file /usr/lib/gstreamer-0.10/libgstfbdevsink.so from install of gstreamer-plugins-bad-0.10.i686 conflicts with file from package gstreamer-plugins-bad-free-extras-0.10.686 If a repo has no priority= line then it is given priority=99 by default.Įven with yum-plugin-priorities installed and configured correctly, it's sometimes necessary to exclude individual packages from some repos - so you might, for example, need to add "exclude=libmodplug" to the EPEL repo file if, in general, you'd rather pick packages from EPEL than from rpmforge but you have the situation you have now. Priority 1 is the highest priority and means that packages from that repo are always preferred. In CentOS-Base.repo it's best to assign priority=1 to base, updates, extras and perhaps centosplus. If it isn't already installed, install it, edit the various *.repo files in /etc/ and add lines to each repo stanza in the files there that you want to prioritise. This lets you set priorities per repo and helps to avoid such conflicts in the future - unfortunately it's not perfect and things like this do still happen sometimes. ![]() We usually recommend that people install and configure the yum-plugin-priorities package. If the package is also in rpmforge then you can remove libmodplug and its dependent package and install both from rpmforge along with gstreamer etc. Otherwise you need to decide if the thing that requires libmodplug from EPEL is more important to you than the thing that requires libmodplug from RPMForge or if the thing that is installed from EPEL is also available from RPMForge. If nothing requires it then libmodplug will be the only thing that yum is trying to remove and it's safe to go ahead and let it do so. If something that is already installed requires libmodplug then yum will be trying to remove it (or them). ![]() RunĪnd do not blindly type Y when asked to confirm but read the list of packages that it says it will remove. So you have somethig from EPEL installed that requires libmodplug so your first task is to find out what that is by attempting to remove it. The conflict is with the libmodplug RPM from EPEL. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |