On Tue, Sep 13, 2022 at 8:46 PM Mukundan Ragavan <nonamedotc@xxxxxxxxx> wrote: > > > I have a packaging question - > > One of the packages I maintain, nextcloud-client, fails to execute in > EPEL-9. It is being blocked by SELinux policy. > > getsebool selinuxuser_execmod is off in EL9. > > Is it even allowed to change SELinux rule in, for example, %post? > > I suspect the correct way to do this is to file a bug, correct? > > Thanks. > > -- > GPG Key: E5C8BC67 > _______________________________________________ > epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue I've never seen anything prohibiting it. In the caddy package I set some SELinux booleans, fcontexts, and ports in %post. To avoid hard dependencies on the tools I wrap the commands in an if statement that checks for the relevant binary. https://src.fedoraproject.org/rpms/caddy/blob/rawhide/f/caddy.spec#_232-250 Grepping through other spec files I see a quite a few other examples of setsebool and semanage commands in scriptlets. -- Carl George _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
