On Mon, Feb 08, 2016 at 09:27:31AM -0600, S A wrote: > > I posted a while back about conflicts that came up under 7.1 when the kernel > for 7.2 was dropped into the 7.1 security repo. I had issues with VirtualBox > kernel modules and dependencies to packages not backported from 7.2 into 7.1. > Since that time I had avoided doing kernel updates and stayed on > 3.10.0-229.14.1. Now that 7.2 is GA, I've made a couple of attempts to > update and am running into several problems. >
Yes, I too find it very inconvinient that the kernel in 7.2 is explicitely binary incompatible with the kernel in 7.1. For example, some ELREPO kernel modules will not load because "they are for 7.1". Do we must have ELREPO-7.1, ELREPO-7.2, etc? With luck this will settle soon enough, but I did not see any explanation for this binary incompatibility, should I think that this is the new way of things - each new release junks all the old driver kernel modules and I must harrass the hardware vendors to issue new drivers? > > Error: libX11 conflicts with libxcb-1.9-5.el7.x86_64 > Error: avahi-glib conflicts with avahi-0.6.31-15.el7.x86_64 > You could try using --skip-broken to work around the problem > ** Found 91 pre-existing rpmdb problem(s), 'yum check' output follows: > PackageKit-glib-1.0.7-5.sl7.x86_64 is a duplicate with > PackageKit-glib-0.8.9-11.sl7.x86_64 > accountsservice-0.6.35-9.el7.x86_64 is a duplicate with > accountsservice-0.6.35-7.el7.x86_64 > ...<snip>... > > I've successfully removed the avahi package, as I don't need it. Removing > libxcb produces a dependency chain of an additional 412 packages to remove - > basically all of Gnome/X11, so I didn't attempt that. I've attempted > package-cleanup tool to list the dupes and run the cleanup, but this results > with the following: > > --> Finished Dependency Resolution > Error: Trying to remove "yum", which is protected > ** Found 90 pre-existing rpmdb problem(s), 'yum check' output follows: > PackageKit-glib-1.0.7-5.sl7.x86_64 is a duplicate with > PackageKit-glib-0.8.9-11.sl7.x86_64 > > Attempting to cleanup dupes again with --skip-broken does not change the > result. > > Anyone have any advice to cleanup this dupes problem? > I ran into similar problems - after an aborted "yum update" many dup packages. You have to clean them up pretty much by hand (hint: write a perl script). Compared to el6, the el7 yum+rpm had a much harder time recovering from this, for example el7 yum bombed with errors like this: - rpm shows both foo-15 and foo-20 installed - "yum update foo" says "updating foo" "foo-20" will be an update - "sorry, foo-20 is already installed, bomb!". Well, duh! The el7 too "package-cleanup --clean-dupes" just went into an infinite loop trying to remove all of everything. Another fine example of something that kind of worked in el6 works worse in el7. -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
