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.
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@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@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
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@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@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.
libldb
dnf install @idm:DL1 Last metadata expiration check: 0:03:54 ago on Fri 17 Apr 2020 16:08:56 EDT. Error: Problem: package ipa-client-4.8.0-13.module_el8.1.0+265+e1e65be4.x86_64 requires sssd-tools >= 2.2.0-1, but none of the providers can be installed - conflicting requests - nothing provides libldb.so.1()(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 - nothing provides libldb.so.1(LDB_0.9.10)(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Same issue with libldb when I tried to install CentOS Stream using the pxeboot images and the installation failed. Seems libldb was updated to 2.0.7 which broke some dependencies. https://koji.mbox.centos.org/koji/packageinfo?packageID=1007
On 18/04/2020 01:04, Chen, Ming A wrote:
libldb
dnf install @idm:DL1 Last metadata expiration check: 0:03:54 ago on Fri 17 Apr 2020 16:08:56 EDT. Error: Problem: package ipa-client-4.8.0-13.module_el8.1.0+265+e1e65be4.x86_64 requires sssd-tools >= 2.2.0-1, but none of the providers can be installed - conflicting requests - nothing provides libldb.so.1()(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 - nothing provides libldb.so.1(LDB_0.9.10)(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Same issue with libldb when I tried to install CentOS Stream using the pxeboot images and the installation failed. Seems libldb was updated to 2.0.7 which broke some dependencies. https://koji.mbox.centos.org/koji/packageinfo?packageID=1007
Yes we discussed this and Carl was already working on fixing it. I see (this morning, CET time) that during the night some jenkins jobs validated an updated tree so hopefully should go out to mirrors soon
On la, 18 huhti 2020, Fabian Arrotin wrote:
On 18/04/2020 01:04, Chen, Ming A wrote:
libldb
dnf install @idm:DL1 Last metadata expiration check: 0:03:54 ago on Fri 17 Apr 2020 16:08:56 EDT. Error: Problem: package ipa-client-4.8.0-13.module_el8.1.0+265+e1e65be4.x86_64 requires sssd-tools >= 2.2.0-1, but none of the providers can be installed - conflicting requests - nothing provides libldb.so.1()(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 - nothing provides libldb.so.1(LDB_0.9.10)(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Same issue with libldb when I tried to install CentOS Stream using the pxeboot images and the installation failed. Seems libldb was updated to 2.0.7 which broke some dependencies. https://koji.mbox.centos.org/koji/packageinfo?packageID=1007
Yes we discussed this and Carl was already working on fixing it. I see (this morning, CET time) that during the night some jenkins jobs validated an updated tree so hopefully should go out to mirrors soon
Can we also fix https://bugs.centos.org/view.php?id=16929 ?
You always need to rebuild idm:DL1 module stream after you change/update Samba and libldb.
It is quite embarrasing that this is open for more than 3 months already with no reaction from however maintains CentOS repositories and build system.
On 18/04/2020 10:26, Alexander Bokovoy wrote:
On la, 18 huhti 2020, Fabian Arrotin wrote:
On 18/04/2020 01:04, Chen, Ming A wrote:
libldb
dnf install @idm:DL1 Last metadata expiration check: 0:03:54 ago on Fri 17 Apr 2020 16:08:56 EDT. Error: Problem: package ipa-client-4.8.0-13.module_el8.1.0+265+e1e65be4.x86_64 requires sssd-tools >= 2.2.0-1, but none of the providers can be installed - conflicting requests - nothing provides libldb.so.1()(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 - nothing provides libldb.so.1(LDB_0.9.10)(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Same issue with libldb when I tried to install CentOS Stream using the pxeboot images and the installation failed. Seems libldb was updated to 2.0.7 which broke some dependencies. https://koji.mbox.centos.org/koji/packageinfo?packageID=1007
Yes we discussed this and Carl was already working on fixing it. I see (this morning, CET time) that during the night some jenkins jobs validated an updated tree so hopefully should go out to mirrors soon
Can we also fix https://bugs.centos.org/view.php?id=16929 ?
You always need to rebuild idm:DL1 module stream after you change/update Samba and libldb.
It is quite embarrasing that this is open for more than 3 months already with no reaction from however maintains CentOS repositories and build system.
Carl, Brian, Johnny ? Can we have a look at mentioned bug and see what's the best way to solve it ? it seems impact CentOS 8 and don't know about Stream though
On 18/04/2020 09:26, Alexander Bokovoy wrote:
On la, 18 huhti 2020, Fabian Arrotin wrote:
On 18/04/2020 01:04, Chen, Ming A wrote:
libldb
dnf install @idm:DL1 Last metadata expiration check: 0:03:54 ago on Fri 17 Apr 2020 16:08:56 EDT. Error: Problem: package ipa-client-4.8.0-13.module_el8.1.0+265+e1e65be4.x86_64 requires sssd-tools >= 2.2.0-1, but none of the providers can be installed - conflicting requests - nothing provides libldb.so.1()(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 - nothing provides libldb.so.1(LDB_0.9.10)(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Same issue with libldb when I tried to install CentOS Stream using the pxeboot images and the installation failed. Seems libldb was updated to 2.0.7 which broke some dependencies. https://koji.mbox.centos.org/koji/packageinfo?packageID=1007
Yes we discussed this and Carl was already working on fixing it. I see (this morning, CET time) that during the night some jenkins jobs validated an updated tree so hopefully should go out to mirrors soon
Can we also fix https://bugs.centos.org/view.php?id=16929 ?
You always need to rebuild idm:DL1 module stream after you change/update Samba and libldb.
It is quite embarrasing that this is open for more than 3 months already with no reaction from however maintains CentOS repositories and build system.
Yes, I too was thinking that a horde of devel would rush to fix that next day. It cannot be just a tiny bunch of IPA+samba users, these two must be critical to many setups.
many thanks, L.
On la, 18 huhti 2020, lejeczek via CentOS-devel wrote:
On 18/04/2020 09:26, Alexander Bokovoy wrote:
On la, 18 huhti 2020, Fabian Arrotin wrote:
On 18/04/2020 01:04, Chen, Ming A wrote:
libldb
dnf install @idm:DL1 Last metadata expiration check: 0:03:54 ago on Fri 17 Apr 2020 16:08:56 EDT. Error: Problem: package ipa-client-4.8.0-13.module_el8.1.0+265+e1e65be4.x86_64 requires sssd-tools >= 2.2.0-1, but none of the providers can be installed - conflicting requests - nothing provides libldb.so.1()(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 - nothing provides libldb.so.1(LDB_0.9.10)(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Same issue with libldb when I tried to install CentOS Stream using the pxeboot images and the installation failed. Seems libldb was updated to 2.0.7 which broke some dependencies. https://koji.mbox.centos.org/koji/packageinfo?packageID=1007
Yes we discussed this and Carl was already working on fixing it. I see (this morning, CET time) that during the night some jenkins jobs validated an updated tree so hopefully should go out to mirrors soon
Can we also fix https://bugs.centos.org/view.php?id=16929 ?
You always need to rebuild idm:DL1 module stream after you change/update Samba and libldb.
It is quite embarrasing that this is open for more than 3 months already with no reaction from however maintains CentOS repositories and build system.
Yes, I too was thinking that a horde of devel would rush to fix that next day. It cannot be just a tiny bunch of IPA+samba users, these two must be critical to many setups.
None of FreeIPA or Samba developers are involved in CentOS rebuilds. I wish I could help but we aren't privy to those packages in CentOS main repositories.
The only influence I have is by being upstream to it (in RHEL and actual FreeIPA / Samba projects). But the issue like this one is local to CentOS itself.
On 18/04/2020 14:32, Fabian Arrotin wrote:
On 18/04/2020 01:04, Chen, Ming A wrote:
Same issue with libldb when I tried to install CentOS Stream using the pxeboot images and the installation failed. Seems libldb was updated to 2.0.7 which broke some dependencies. https://koji.mbox.centos.org/koji/packageinfo?packageID=1007
Yes we discussed this and Carl was already working on fixing it. I see (this morning, CET time) that during the night some jenkins jobs validated an updated tree so hopefully should go out to mirrors soon
Thank you guys for the quick fix! I'll try it out next week.
Ming Chen
On 18/04/2020 07:32, Fabian Arrotin wrote:
On 18/04/2020 01:04, Chen, Ming A wrote:
libldb
dnf install @idm:DL1 Last metadata expiration check: 0:03:54 ago on Fri 17 Apr 2020 16:08:56 EDT. Error: Problem: package ipa-client-4.8.0-13.module_el8.1.0+265+e1e65be4.x86_64 requires sssd-tools >= 2.2.0-1, but none of the providers can be installed - conflicting requests - nothing provides libldb.so.1()(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 - nothing provides libldb.so.1(LDB_0.9.10)(64bit) needed by sssd-tools-2.2.0-19.el8_1.1.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Same issue with libldb when I tried to install CentOS Stream using the pxeboot images and the installation failed. Seems libldb was updated to 2.0.7 which broke some dependencies. https://koji.mbox.centos.org/koji/packageinfo?packageID=1007
Yes we discussed this and Carl was already working on fixing it. I see (this morning, CET time) that during the night some jenkins jobs validated an updated tree so hopefully should go out to mirrors soon
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
hi, there is still problem with:
... No available modular metadata for modular package 'criu-3.12-9.module_el8.1.0+294+988780c8.x86_64', it cannot be installed on the system
and the conflict of:
corosynclib.x86_64 3.0.3-2.el8 Stream-AppStream VS corosynclib.i686 3.0.2-3.el8_1.1 HighAvailability
Should corosync even be in Stream-AppStream?
regards, L.
-
Alexander Bokovoy -
Chen, Ming A -
Fabian Arrotin -
lejeczek -
Troy Dawson