https://bugzilla.redhat.com/show_bug.cgi?id=1936080 Aleksei Bavshin <alebastr89@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alebastr89@xxxxxxxxx --- Comment #2 from Aleksei Bavshin <alebastr89@xxxxxxxxx> --- > - It seems hikari needs seituid permissions: As far as I can see, nothing here requires suid. `hikari` works with logind wlroots backend and `hikari-unlocker` only needs permission to authenticate current user, which does not require suid in Linux pam. The documentation might be just a tad biased towards BSD systems. > chmod 755 %{buildroot}%{_bindir}/%{name} I believe the canonical way to do that in rpm spec is `%attr(0755,-,-) %{_bindir}/%{name}` in %files section. --- Timothée, do you mind delaying import of `hikari` until f34 final freeze? wlroots 0.13.0 ETA is end of March and I'm not sure if we will be able to get compatible release of hikari fast enough to meet f34 update deadlines. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
