You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The FPM build script seems to have added in python3-daemon as a dependency, but this should only be required when running SSM as a daemon/service. This has caused issues for users.
As reported by email:
apel-client-2.1.0-1.el9.noarch requires apel-ssm >= 3.2.0, but none of the providers can be installed
package apel-ssm-3.4.1-1.el9.noarch requires python3-daemon, but none of the providers can be installed
cannot install the best candidate for the job
nothing provides python3.9dist(docutils) needed by python3-daemon-2.3.2-1.el9.noarch
Looks like apel-ssm requires python3-daemon but on our current setup the python-daemon installation fails.
Also on the release note of the 3.3.0 you state that python-daemon hard requirement was remove but on 3.4.1 the requirement it's still there.
It should be removed from the base package, but if it's possible to add it to the service/pleaserun packages then it can go there as it would be required when running SSM as a service.
The text was updated successfully, but these errors were encountered:
The FPM build script seems to have added in python3-daemon as a dependency, but this should only be required when running SSM as a daemon/service. This has caused issues for users.
As reported by email:
It should be removed from the base package, but if it's possible to add it to the service/pleaserun packages then it can go there as it would be required when running SSM as a service.
The text was updated successfully, but these errors were encountered: