Description of problem: setools-console has no dependency on libselinux-python3 libselinux-python3 is not strictly needed, but it is needed to analyse currently loaded policy. Therefore it should be considered to make libselinux-python3 a soft dependency for setools(-console) Version-Release number of selected component (if applicable): fedora 26
It makes sense. Thanks! Given that selinux python module seems to be imported from setools-python3 package I would add a weak dependency there: diff --git a/setools.spec b/setools.spec index 8f4ce26..6671e03 100644 --- a/setools.spec +++ b/setools.spec @@ -77,6 +77,7 @@ This package includes the following console tools: %package python Summary: Policy analysis tools for SELinux +Recommends: libselinux-python %description python SETools is a collection of graphical tools, command-line tools, and @@ -85,6 +86,7 @@ Python 2 modules designed to facilitate SELinux policy analysis. %package python3 Summary: Policy analysis tools for SELinux Obsoletes: setools-libs < 4.0.0, setools-libs-tcl +Recommends: libselinux-python3 %description python3 SETools is a collection of graphical tools, command-line tools, and Please try the following scratch build if it works as expected - https://koji.fedoraproject.org/koji/taskinfo?taskID=19630142
Not sure what I supposed to be testing here but I can confirm that the scratch built now considers libselinux-python3 a weak dependency. So from my (python3) perspective everything looks good. Thanks
setools-4.1.0-3.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-441bfbabc5
setools-4.1.0-3.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-441bfbabc5
setools-4.1.0-3.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.