-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Make dependency on sdnotify optional. #5865
Comments
My understanding was that sdnotify was a no-op on such systems |
I was hit with an error, so ended up staying on 1.2.1. I'll give it another try tomorrow. |
please let us know what error you are seeing. |
I think line 75 in synapse/python_dependencies.py should be moved to the conditional_requirements, so we can use the systemd flag (line 95). https://github.com/matrix-org/synapse/blob/master/synapse/python_dependencies.py#L75 @richvdh The error I got was missing sdnotify dependency when building. Since it is not on the system. I'm in the process of updating the synapse package for void-linux from 0.99.3 to 1.3.0. 1.2.1 builds and installs no problem. |
building what? what command are you running, and what is the error text? |
Hello, Alpine Linux maintainer for synapse and previous original package of synapse for Void Linux. I'm commenting here since i'm having the same error and i think making a new issue would just be a duplicate. All tests fail with the following error (the message changes for each test and when running but the error is the same)
patching synapse/python_dependencies.py to move sdnotify to CONDITIONAL_REQUIREMENTS doesn't fix this error. EDIT: reverting #5732 fixes the issue, all tests are passing and will be included on Alpine Linux Edge |
... to save OSes which don't use it from having to maintain a port. Fixes #5865.
this suggests that your build script isn't correctly running |
As a workaround to this issue, I'm proposing that we reimplement |
... to save OSes which don't use it from having to maintain a port. Fixes #5865.
Description
Since #5732 was merged sdnotify is a hard dependency.
Make this an optional dependency to allow running on systems which don't use systemd.
Version information
1.2.1>
The text was updated successfully, but these errors were encountered: