| 1 |
On Tue, Sep 1, 2015 at 5:55 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 2 |
> Got it, finally :-) |
| 3 |
> |
| 4 |
> fail2ban wants sys-apps/systemd[python(-)], and systemd-219_p112 is the |
| 5 |
> highest version with an explicit python USE flag. All later versions do |
| 6 |
> not have the flag at all. |
| 7 |
> |
| 8 |
> Your choices are either to have fail2ban fixed to deal with recent |
| 9 |
> systemd USE, and tolerate the systemd downgrade meanwhile; or to replace |
| 10 |
> fail2ban with something equivalent |
| 11 |
> |
| 12 |
|
| 13 |
Sounds like this is covered by: |
| 14 |
https://bugs.gentoo.org/show_bug.cgi?id=558168 |
| 15 |
https://bugs.gentoo.org/show_bug.cgi?id=555502 |
| 16 |
|
| 17 |
It seems to me like this is a portage issue with the resolver. |
| 18 |
Running emerge -1 python-systemd sounds like it fixes the issue. |
| 19 |
Apparently once it is installed portage will figure out it needs to |
| 20 |
hang onto it. |
| 21 |
|
| 22 |
-- |
| 23 |
Rich |
Archives