On Thu, Jul 2, 2020 at 12:38 AM Alexander Bokovoy abokovoy@redhat.com wrote:
On ke, 01 heinä 2020, Brian Stinson wrote:
On Wed, Jul 1, 2020, at 14:33, Alexander Bokovoy wrote:
On ke, 01 heinä 2020, lejeczek via CentOS-devel wrote:
hi guys
latest in the repo krb5 packages - 1.18.2-2.el8 - brake freeIPA if already installed and conflict if want to install.
# dnf install -y ipa-server-dns Last metadata expiration check: 1:21:31 ago on Wed 01 Jul 2020 11:00:25 BST. Error:  Problem: package ipa-server-dns-4.8.4-7.module_el8.2.0+374+0d2d74a1.noarch requires ipa-server = 4.8.4-7.module_el8.2.0+374+0d2d74a1, but none of the providers can be installed  - conflicting requests  - nothing provides krb5-kdb-version = 7.0 needed by ipa-server-4.8.4-7.module_el8.2.0+374+0d2d74a1.x86_64
Going back to the actual issue, the only solution right now is not to use CentOS 8 Stream, at least until all the required rebuilds are in place.
Right now CentOS 8 Stream contains exactly same IPA version as CentOS 8.2.2004. So you are not gaining anything by using the stream right now.
In CentOS Stream we're working on staying caught up to RHEL 8.3 development to jumpstart the automation that will handle this going forward. During this process we're finding that modules are a little bit unwieldy.
There are several rebases in RHEL 8.3 that require rebuild of idm module streams: krb5, samba, libldb are the requirements that need to be rebuilt before idm modules streams can be built. And changes in those packages also require rebuilding SSSD.
I don't think there is a support for a combined non-modular + modular sidetag rebuild in CentOS (it does not exist anywhere else too), so I would suggest taking care of the rebuilds together before pushing them into a publicly accessible tree. Otherwise there will be breakages like this -- which apparently is there for more than 3 weeks already.
Yep. There are breakages in idm, and other packages. But, there are two things that this entire conversation is completely missing.
1 - CentOS Stream is NOT equal to RHEL 8.<next> general release, it IS equal to RHEL 8.<next> Alpha. Yes, Alpha. Not even Beta. This whole conversation is acting like CentOS Stream should be production ready. It should not. It is to allow the general public to see what is going into the next release, problems and all. If people are running their production machines on CentOS Stream ... well, in my opinion, that's their problem.
2 - CentOS Stream was announced that it would be ready in December 2020. That's still 5 months from now. Give the team a break. They are still setting up infrastructure, workflows, and who knows what else.
For years people have gotten on CentOS's case because they are not transparent enough, and don't give people access to stuff before it's 100% ready. And now when they do, you are acting like they should take the whole thing back and wait until it's completely ready. Well, completely ready is not CentOS Stream. That's CentOS.
Troy