-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request: configure PowerTools (or codeready-developer) repo on CentOS 8 (or RHEL 8) #93
Comments
Interesting, the epel-release package doesn’t install/configure a package/repo for Powertools, so one does wonder how required it is. A feature flag that defaults to disabled seems reasonable though, since others may already manage that through another module. For codeready, that’s a subscription manager thing, I think that’s beyond the scope of this module. |
It’s definitely not required for any of the packages I’m using (well, at least the ones that still exist in 8). I’m a little unclear on why the EPEL packages would require it at runtime, since it’s mostly I have absolutely no problem with just closing this. |
I’ll go ahead and close it for now, and if it turns out that it’s problematic, we can reopen and work on it. Thanks for bringing it up! |
Just as feedback: We have been bitten by this while rolling out monitoring for our new CentOS 8 nodes.
See also https://bugzilla.redhat.com/show_bug.cgi?id=1754947 So, all Nagios monitoring scripts using Perl do not work, as that package relies on PowerTools being there. I'm unsure if that's enough reason for it to be enabled broadly... |
We've just run into this issue trying to install amavisd-new on CentOS Stream 8 Thanks, |
I’ve found documentation that the PowerTools/codeready-developer repos are important to some packages in EPEL when used on CentOS/RHEL 8. I haven’t actually run into this myself, though.
Perhaps the PowerTools/codeready-developer repos should be configured by this package?
The text was updated successfully, but these errors were encountered: