Make fail2ban work again #11683
Make fail2ban work again #11683
Conversation
rvl
commented
Dec 13, 2015
rvl
commented
- fail2ban depends on the systemd python module which has changed location.
- There was some problem with the location of installed files (issue fail2ban: $out/etc is missing #11534).
- Update to the latest release (0.9.3 2015/08/01 - lets-all-stay-friends) for good measure.
|
By analyzing the blame information on this pull request, we identified @lovek323, @offlinehacker and @bjornfor to be potential reviewers |
|
@rvl the Travis build fails with: Do you have chroot building enabled for nix? That might help to reproduce it. |
| }; | ||
|
|
||
| buildInputs = [ unzip ]; | ||
|
|
||
| pythonPath = (stdenv.lib.optional stdenv.isLinux systemd) | ||
| pythonPath = (stdenv.lib.optional stdenv.isLinux pythonPackages.systemd) |
There was a problem hiding this comment.
could you use propagatedBuildInputs here
|
@cillianderoiste Thanks for the tip. I tried chroot building just then but couldn't get it to work. As a workaround I have removed @FRidh I have implemented your suggestions, thanks. |
|
Looking forward to getting fail2ban working again (China really wants my root account, it seems); thanks for this. |
|
No prob @jeaye. Can I ask @domenkozar to kindly check the |
This module has been split out from the main systemd repository.
…ixes #11534) Removed path substitutions from setup.py because these should be handled by the setuptools install prefix. Except that the install prefix won't quite work until issue #4968 is resolved. In the meantime there are preInstall and postInstall scripts so that this package continues to work with the nix python packaging improvements.
The python module has been split off from systemd since v223.
|
Ok great @domenkozar that explains it. I have changed it to use that workaround. However this |
|
@rvl tnx! |
|
@garbas thx for merging |
