Am 13.06.22 um 13:41 schrieb Josh Boyer:
On Sun, Jun 12, 2022 at 6:50 AM Sérgio Basto sergio@serjux.com wrote:
On Sun, 2022-06-05 at 00:54 +0200, Neal Gompa wrote:
Let me start with examples that I get *regularly*: Pagure fails to install from EPEL on RHEL/CentOS/Alma/etc. because python3-markdown is not available. KDE Plasma fails to install because of a mass of missing dependencies.
if epel use crb to build some package, crb should be enabled when we install epel repo, yes , that is my opinion
If the dependency is only needed at build time, which is what CRB content is intended for, then there is no reason to default to having CRB enabled because nothing will be installed from CRB anyway. The issue that people are running into is that EPEL packages have developed *runtime* dependencies on CRB content. For a subset of users, that is probably fine. However, if a package needs something at runtime it would be better to first inquire about putting that dependency in BaseOS or AppStream rather than just blindly using it from CRB.
Not sure if there is a misconception but crb repo has all kind of packages also runtime ones. The concept that RH is applying against crb is; supported or not supported period. Everthing else would mean that RH should move everything without -devel in %{NAME} into appstream or baseos.
Example (powertools aka crb):
#repoquery --repoid=powertools ladspa Last metadata expiration check: 1 day, 1:43:56 ago on Sun Jun 12 13:02:39 2022. ladspa-0:1.13-20.el8.x86_64
# rpm -ev --test ladspa.x86_64 error: Failed dependencies: ladspa is needed by (installed) rubberband-1.9.0-1.el8.x86_64
# repoquery --repoid=epel rubberband Last metadata expiration check: 1 day, 1:44:41 ago on Sun Jun 12 13:02:40 2022. rubberband-0:1.9.0-1.el8.x86_64
# repoquery --repoid=powertools ladspa-devel Last metadata expiration check: 1 day, 1:46:06 ago on Sun Jun 12 13:02:39 2022. ladspa-devel-0:1.13-20.el8.i686 ladspa-devel-0:1.13-20.el8.x86_64
-- Leon