Closed hashbrowncipher closed 3 years ago
Thanks for reporting, this is known , and for the life of me I could swear that I included that in the readme ... Apparently I did not, I will fix that ..
Sadly by the way that cython works, it make really hard to not include the symbols...
Will update the task with a PR for the readme
Once again, Thanks for reporting!!
I have been using pystemd for a bit now with a backported systemd-234 on centos7. I was surprised when I updated packages today found this error. I cannot find any backports of systemd-237 or above. Any suggestions for me?
oh dude, i'm really sorry we broke you... i would recommend pin to version 0.5, while we come up with a solution that is not terrible horrible... this surface as a import error at runtime, so it may be possible to attach this programatically. i just need to sit and think of something clever.
i'll update the issue, when i have an idea!
@shorton3, we have a systemd 241 backport for CentOS 7 at https://github.com/facebookincubator/rpm-backports fyi
Thanks David, I'll give it a try. We can close this thread. I will either stay with 0.5 or migrate to your newer systemd.
Change to older version or fix this ? version 0.8.0 still has this problem.
pystemd version 0.6.0 references
sd_bus_match_signal
, which only exists in systemd >=237. Users on older OSes (e.g. Ubuntu Xenial) will experience an error importing pystemd, like so:Possible solutions include a) document the required systemd version or b) disable the feature when compiled against versions not including the necessary symbols.