Require systemd v243+, recommend systemd v245+, test against systemd v245 #117
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This makes existing requirements explicit, but doesn't increase them. Due to that, its not really breaking.
Changes
This isn't breaking because v0.17 is already broken for systemd version <243 because the OOMPolicy config set in Don't kill the whole service when a single proces OOMs #101 was [introduced in systemd version 243] (systemd/systemd@afcfaa6) and makes user servers fail to start.
This is motivated by us only testing on systemd version 245.
Version 245 is easy for us to test against, because its part of Ubuntu 20.04. Yuvi suggested testing against the second most newest ubuntu LTS release's systemd version, which is a perfect policy in my mind because of the environments provided by CI systems like GitHub Actions. In GitHub actions, Ubuntu 20.04 and 22.04 is available, but Ubuntu 18.04 isn't available any more and was removed a while after 22.04 had been added.
Related