On 17/04/2020 15:54, Troy Dawson wrote: > So, it looks like you are using CentOS Stream, and still have the > regular CentOS repositories enabled. > Which, last time I installed CentOS Stream, was the default. > > My opinion: I think if you install CentOS Stream, you should have > only the CentOS Stream repo's enabled by default. > (^^ This is a note to the CentOS Stream developers) > Having the other repositories enabled just messes things up, like this example. > > Anyway, for my stream machines, I do the following after an install. > > dnf config-manager --disable AppStream > dnf config-manager --disable BaseOS > dnf config-manager --disable extras > dnf config-manager --disable PowerTools > dnf config-manager --enable Stream-PowerTools > > On Fri, Apr 17, 2020 at 7:21 AM lejeczek via CentOS-devel > <centos-devel at centos.org> wrote: >> hi everyone. >> >> dnf updates collide: >> >> $ dnf update corosynclib >> Last metadata expiration check: 0:19:02 ago on Fri 17 Apr >> 2020 14:57:48 BST. >> Error: >> Problem: problem with installed package >> corosync-3.0.2-3.el8_1.1.x86_64 >> - package corosync-3.0.2-3.el8_1.1.x86_64 requires >> corosynclib(x86-64) = 3.0.2-3.el8_1.1, but none of the >> providers can be installed >> - cannot install both corosynclib-3.0.3-2.el8.x86_64 and >> corosynclib-3.0.2-3.el8_1.1.x86_64 >> - cannot install the best update candidate for package >> corosynclib-3.0.2-3.el8_1.1.x86_64 >> (try to add '--allowerasing' to command line to replace >> conflicting packages or '--skip-broken' to skip >> uninstallable packages or '--nobest' to use not only best >> candidate packages) >> >> $ dnf list corosynclib --showduplicates >> Last metadata expiration check: 0:18:45 ago on Fri 17 Apr >> 2020 14:57:48 BST. >> Installed Packages >> corosynclib.x86_64 >> 3.0.2-3.el8_1.1 >> @AppStream >> Available Packages >> corosynclib.i686 >> 3.0.2-3.el8 >> AppStream >> corosynclib.x86_64 >> 3.0.2-3.el8 >> AppStream >> corosynclib.i686 >> 3.0.2-3.el8_1.1 >> AppStream >> corosynclib.i686 >> 3.0.2-3.el8_1.1 >> HighAvailability >> corosynclib.x86_64 >> 3.0.2-3.el8_1.1 >> AppStream >> corosynclib.i686 >> 3.0.3-2.el8 >> Stream-AppStream >> corosynclib.x86_64 >> 3.0.3-2.el8 >> Stream-AppStream >> >> It cannot be that those(some of?) repos exclude each other, >> right? >> >> many thanks, L. >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel at centos.org >> https://lists.centos.org/mailman/listinfo/centos-devel That is not the problem here I don't believe. It has not been so far. Besides the problem starts between these two: corosynclib.x86_64 3.0.2-3.el8_1.1 @AppStream Available Packages corosynclib.x86_64 3.0.3-2.el8 Stream-AppStream and then the issue of Stream-AppStream having higher version of corosynclib than HighAvailability and HighAvailability is where pacemaker + corosync(and more) come from. But yes, on Centos Steam note, OS after clean installation off a CentOS-Stream-x86_64-dvd1.iso does not even have Steam repos installed/configured and you one has to install centos-release-stream-8.1-1.1911.0.9.el8.x86_64, I had to. Yes, very confusing as to which repos should "Steam" use.