[CentOS] conflicts in updating to CR repo

Thu Sep 19 20:10:23 UTC 2019
Fred Smith <fredex at fcshome.stoneham.ma.us>

On Thu, Sep 19, 2019 at 12:10:41PM -0500, Johnny Hughes wrote:
> On 9/18/19 5:48 PM, Fred Smith wrote:
> > On Sat, Sep 14, 2019 at 07:20:35PM +0100, Phil Perry wrote:
> >> On 14/09/2019 19:06, Fred Smith wrote:
> >>> Note, first of all I haven't actually updated, I'm just running "yum update"
> >>> to see what conflicts, if any, I get so I can be prepared when the final
> >>> 7.7 release happens.
> >>>
> >>> I've traditionally used the nvidia packages from elrepo, but recently
> >>> enabled rpmfusion (back when I started using 7.x, I disabled rpmfusion
> >>> because it took them a looooong time to get a EL7 repository up).
> >>>
> >>> I use the priority plugin in yum, and have elrepo at priority 50
> >>> and rpmfusion at priority 60, so the elrepo nvidia packages
> >>> should "win", but yum seems to be confused about which packages
> >>> to use.
> >>>
> >>> So now when doing yum update (with CR enabled) I get this long list
> >>> of dependency issues regarding the nvidia packages. I don't see any
> >>> reason to switch to the rpmfusion packages, elrepo seems to do a good
> >>> job of packaging and keeping them up to date:
> >>>
> >>> --> Processing Dependency: xorg-x11-drv-nvidia-390xx-libs(x86-64) = 3:390.129-1.el7 for package: 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64
> >>> --> Processing Dependency: nvidia-settings-390xx(x86-64) = 390.129 for package: 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64
> >>> --> Processing Dependency: libnvidia-tls.so.390.129()(64bit) for package: 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64
> >>> --> Processing Dependency: libnvidia-glcore.so.390.129()(64bit) for package: 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64
> >>> --> Running transaction check
> >>> ---> Package nvidia-settings-390xx.x86_64 0:390.129-1.el7 will be installed
> >>> ---> Package xorg-x11-drv-nvidia-390xx-libs.x86_64 3:390.129-1.el7 will be installed
> >>> --> Processing Conflict: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 conflicts xorg-x11-drv-nvidia-390xx
> >>> Removing kmod-nvidia.x86_64 0:430.50-1.el7_7.elrepo - u due to obsoletes from kmod-nvidia-390xx.x86_64 3:390.129-3.el7 - u
> >>> --> Restarting Dependency Resolution with new changes.
> >>> --> Running transaction check
> >>> ---> Package kmod-nvidia.x86_64 0:430.50-1.el7_7.elrepo will be an update
> >>> --> Processing Dependency: nvidia-kmod = 430.50 for package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64
> >>> --> Processing Dependency: nvidia-kmod = 430.50 for package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64
> >>> ---> Package nvidia-x11-drv.x86_64 0:430.40-1.el7_6.elrepo will be updated
> >>> ---> Package nvidia-x11-drv.x86_64 0:430.40-1.el7_6.elrepo will be updated
> >>> --> Finished Dependency Resolution
> >>> --> Running transaction check
> >>> ---> Package kernel.x86_64 0:3.10.0-957.21.2.el7 will be erased
> >>> ---> Package kernel-devel.x86_64 0:3.10.0-957.21.2.el7 will be erased
> >>> ---> Package kmod-nvidia.x86_64 0:430.50-1.el7_7.elrepo will be an update
> >>> --> Processing Dependency: nvidia-kmod = 430.50 for package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64
> >>> --> Processing Dependency: nvidia-kmod = 430.50 for package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64
> >>> --> Processing Conflict: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 conflicts xorg-x11-drv-nvidia-390xx
> >>> --> Finished Dependency Resolution
> >>> Error: nvidia-x11-drv conflicts with 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64
> >>> Error: Package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 (elrepo)
> >>>            Requires: nvidia-kmod = 430.50
> >>>            Removing: kmod-nvidia-430.40-1.el7_6.elrepo.x86_64 (@elrepo)
> >>>                nvidia-kmod = 430.40-1.el7_6.elrepo
> >>>            Obsoleted By: 3:kmod-nvidia-390xx-390.129-3.el7.x86_64 (rpmfusion-nonfree-updates)
> >>>                Not found
> >>>            Updated By: kmod-nvidia-430.50-1.el7_7.elrepo.x86_64 (elrepo)
> >>>                nvidia-kmod = 430.50-1.el7_7.elrepo
> >>>            Available: 3:akmod-nvidia-430.40-2.el7.x86_64 (rpmfusion-nonfree-updates)
> >>>                nvidia-kmod = 3:430.40-2.el7
> >>>            Available: kmod-nvidia-430.14-1.el7_6.elrepo.x86_64 (elrepo)
> >>>                nvidia-kmod = 430.14-1.el7_6.elrepo
> >>>            Available: kmod-nvidia-430.26-1.el7_6.elrepo.x86_64 (elrepo)
> >>>                nvidia-kmod = 430.26-1.el7_6.elrepo
> >>>            Available: kmod-nvidia-430.34-1.el7_6.elrepo.x86_64 (elrepo)
> >>>                nvidia-kmod = 430.34-1.el7_6.elrepo
> >>>            Available: kmod-nvidia-430.40-2.el7_7.elrepo.x86_64 (elrepo)
> >>>                nvidia-kmod = 430.40-2.el7_7.elrepo
> >>>            Available: 3:kmod-nvidia-430.40-2.el7.x86_64 (rpmfusion-nonfree-updates)
> >>>                nvidia-kmod = 3:430.40-2.el7
> >>>            Available: 3:kmod-nvidia-3.10.0-1062.el7.x86_64-430.40-2.el7.x86_64 (rpmfusion-nonfree-updates)
> >>>                nvidia-kmod = 3:430.40-2.el7
> >>>  You could try using --skip-broken to work around the problem
> >>>
> >>> Thanks in advance for advice!
> >>>
> >>> Fred
> >>>
> >>
> >> This is an artefact of mixing elrepo and rpmfusion. I'd suggest you
> >> stick to one or the other, but not enable both at the same time.
> >>
> >> What does it look like if you just disable the rpmfusion repo?
> >>
> >> yum update --diaablerepo=rpmfusion
> >>
> >> Do things look more sane now?
> > 
> > Phil, can youclarify a bit for me pls?
> > 
> > I was under the impression that the priorities feature of yum was for
> > the specific purpose of controlling the order in which repos were used
> > for updates, etc.
> > 
> > I have elrepo set with a lower number (40) than rpmfusion (50), so
> > why wouldn't yum be prevented from installing files from rpmfusion in
> > preference to those from elrepo?
> > 
> > I've used the elrepo nvidia drivers for some years and been pleased
> > with the level of service you provide. For free, yet! :)
> > 
> 
> Because they have different things that require different versions of
> the same package.  Priorities will, if you have the exact same
> name-version-release in 2 places, the the package from the lower
> priority.  But if you have 2 different versions of the same package ..
> ie, abc-123-1 on one service and abc-123-2 in the other ... abc-123-2
> always gets installed because it is newer.
> 
> Not all repos work together.
> 
> If you mix repos (who don't work together to fix their conflicts) ..
> then you have t figure out what to exclude from one or the other to mkae
> things work.

Thanks Johnny!

I went to elrepo because back when I originally went to C7, rpmfusion
did not have an EL7 repo. I kept checking back, occasionally, for
several years, and only recently learned that they now do.

So now I"m stuck with elrepo. yum gives me a huge list of things from
elrepo (a lot of them are things I certainly didn't install on purpose,
must have been brought in as dependencies I guess.)

I also was using the nux repo because he had some things nobody
else had. but when I discovered that some of the things I had gotten
from nux were way out of date, I checked rpmfusion and saw they had
modern versions and installed them. (xfreerdp, VLC)

I'll have to go carefully through all the stuff from nux and elrepo
to see if I can replace them all by using rpmfusion. If I think I
can I guess I need to (probably) painfully remove them all. I can
imagine dependency hell happening there though.

Thanks for the explanation.

Fred



> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos


-- 
---- Fred Smith -- fredex at fcshome.stoneham.ma.us -----------------------------
                        The Lord is like a strong tower. 
             Those who do what is right can run to him for safety.
--------------------------- Proverbs 18:10 (niv) -----------------------------