fix: use ConditionPathExists for update service checks#14
Merged
RoyalOughtness merged 1 commit intosecureblue:mainfrom Feb 13, 2026
Merged
fix: use ConditionPathExists for update service checks#14RoyalOughtness merged 1 commit intosecureblue:mainfrom
RoyalOughtness merged 1 commit intosecureblue:mainfrom
Conversation
The ConditionFileIsExecutable check doesn't seem to be working properly for some users, and ConditionPathExists should definitely work. Also use `/bin/sh` instead of `/usr/bin/bash` in these services for portability.
da30834 to
51136c6
Compare
RoyalOughtness
approved these changes
Feb 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The ConditionFileIsExecutable check doesn't seem to be working properly for some users, and ConditionPathExists should definitely work.
Also use
/bin/shinstead of/usr/bin/bashin these services for portability.Should fix secureblue/secureblue#1929.