Previously, if boot was enabled but ukify wasn't, the check for the pefile Python module would be omitted. The check in want_ukify was incorrect — with Meson it's only possible to check for Python dependencies available for the build Python. When the build Python is not the same as the Python that will be used to run the installed ukify, this would incorrectly require ukify to be available to the build Python. The most common, but not the only case where this would happen would be when cross compiling. If bootloader and tests are disabled, there's no need for the build Python to have pefile even when installing ukify. Therefore, check in the more specific case of ukify's tests being enabled, in which case pefile is required at build time.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release
