Open tuesdaycodes opened 2 years ago
Usually it's either because of dependency we dont want to pull in, or simply that we havent considered if it should be dependency from the -all subpackage yet.
In this case it seems like it has the same dependencies as multiple other agents that are included, so we can add it.
If you run:
./autogen.sh
./configure
make
It'll generate a version without .py (with Python binary and other replacements done if necessary).
To get it into EPEL someone needs to volunteer to maintain it.
I see there's a bz about it: https://bugzilla.redhat.com/show_bug.cgi?id=2029251
@oalbrigt i have same issue. is being fix by clusterlabs for spec in repo even if not in epel? or require comm pr?
It needs to be fixed in EPEL, since the CentOS package only provides the subpackages from the RHEL package.
i see on bugzilla they blame rhel there, wont fix epel. if rhel use repo here needs fix here for rhel to fix = fix in epel
https://github.com/ClusterLabs/fence-agents/blob/master/fence-agents.spec.in#L33
unclear why not included but would be helpful if it was. if unable to package how would someone use it with a pacemaker install otherwise? just copy the .py to some directory?
can these agents also be packaged in epel for easier consumption? looks like only a few are.