Kai Lüke
761c664110
While for sysupdate it's fine to consume a large set of all possible update payloads in a single directory this is not so handy for managing and serving the update payloads. Since this large update folder is not where the build output directly gets written to one has to create copies and later possibly delete this added set of files. Support matching for filenames in subdirectories by having a new **/ match pattern prefix which matches any number of nested subdirectories or no subdirectory at all. For simplicity it's only allowed at the start of a pattern and not a regular wildcard as the rest because the main use case is to descend into subdirectories and only do the pattern matching for the basenames. This way one can create a SHA256SUMS file in the top folder and have it include all update payloads from the release-specific (or arch-specific) subdirectories. Something similar was already supported for directory sources where the match pattern can start with a subdirectory path. Do also support this for SHA256SUMS for parity while we are at it. Having the new wildcard makes mirroring also easier because one does not have to follow the exact subdirectory layout and one can filter by folder instead of by filename. It also makes it possible to point the same transfer files with the new wildcard to either a SHA256SUMS file that uses release-specific (or arch-specific) subdirectories and includes all versions or to a SHA256SUMS file as generated from mkosi that does not use subdirectories because it only has files for a single version. With the upcoming UAPI.16 JSON format we will also be able to encode subdirectories and it makes sense to add this to SHA256SUMS for being able to convert them. It also supports custom URLs for each entry which is more powerful than the (arbitrary) subdirectory feature used here but subdirectories have the advantage that they don't break mirroring. This change also fixes the existing subdirectory handling bugs where everything greater than two subdirectory levels failed to work because rel_joined instead of de->d_name got used, symlinks were followed, and we would continue silently on non-ENOENT errors.
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