I have the same problem, but I think someone isn’t building the dependencies properly.
Problem 1: package libstdc++-devel-8.5.0-3.el8.x86_64 requires libstdc++(x86-64) = 8.5.0-3.el8, but none of the providers can be installed
- cannot install both libstdc++-8.5.0-4.el8_5.x86_64 and libstdc++-8.5.0-3.el8.x86_64
- cannot install the best update candidate for package libstdc++-devel-8.4.1-1.el8.x86_64
- cannot install the best update candidate for package libstdc++-8.4.1-1.el8.x86_64
Problem 2: libgomp-8.5.0-3.el8.i686 has inferior architecture
- package gcc-8.5.0-3.el8.x86_64 requires libgomp = 8.5.0-3.el8, but none of the providers can be installed
- cannot install both libgomp-8.5.0-4.el8_5.x86_64 and libgomp-8.5.0-3.el8.x86_64
- cannot install the best update candidate for package libgomp-8.4.1-1.el8.x86_64
- cannot install the best update candidate for package gcc-8.4.1-1.el8.x86_64
Note that the previous package is libgomp-8.5.0-3.el8.x86_64 and the new one libgomp-8.5.0-4.el8_5.x86_64 - the difference instead of being el8, it has been done as el8_5. The same with the libstdc package as well. The naming convention should have been the same so el8 and not el8_5, so there are a mix of packages not being built to the dependencies properly. So one package is relying on the old package, and others on the new package, but because both cannot be installed at the same time, a conflict occurs.
This occurred for me once when I started using Rocky and needed to install a pip for python I couldn’t do it because of this.