| 1 |
On 01/09/2015 12:18, Marc Joliet_1 wrote: |
| 2 |
> On Tuesday 01 September 2015 11:55:12 Alan McKinnon wrote: |
| 3 |
>> On 01/09/2015 02:12, covici@××××××××××.com wrote: |
| 4 |
> [...] |
| 5 |
>> |
| 6 |
>> Got it, finally :-) |
| 7 |
>> |
| 8 |
>> fail2ban wants sys-apps/systemd[python(-)], and systemd-219_p112 is the |
| 9 |
>> highest version with an explicit python USE flag. All later versions do |
| 10 |
>> not have the flag at all. |
| 11 |
>> |
| 12 |
>> Your choices are either to have fail2ban fixed to deal with recent |
| 13 |
>> systemd USE, and tolerate the systemd downgrade meanwhile; or to replace |
| 14 |
>> fail2ban with something equivalent |
| 15 |
> |
| 16 |
> That'll be because the systemd python bindings were split into a separate |
| 17 |
> package upstream. But fail2ban already depends on it: |
| 18 |
> |
| 19 |
> systemd? ( $(python_gen_cond_dep '|| ( |
| 20 |
> dev-python/python-systemd[${PYTHON_USEDEP}] |
| 21 |
> sys-apps/systemd[python(-),${PYTHON_USEDEP}] |
| 22 |
> )' 'python*' ) ) |
| 23 |
> |
| 24 |
> So maybe the OP just needs to unmask python-systemd? |
| 25 |
|
| 26 |
|
| 27 |
That makes sense. |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Alan McKinnon |
| 32 |
alan.mckinnon@×××××.com |
Archives