1 |
On Tue, Sep 1, 2015 at 7:13 AM, <covici@××××××××××.com> wrote: |
2 |
> Rich Freeman <rich0@g.o> wrote: |
3 |
>> |
4 |
>> Sounds like this is covered by: |
5 |
>> https://bugs.gentoo.org/show_bug.cgi?id=558168 |
6 |
>> https://bugs.gentoo.org/show_bug.cgi?id=555502 |
7 |
>> |
8 |
>> It seems to me like this is a portage issue with the resolver. |
9 |
>> Running emerge -1 python-systemd sounds like it fixes the issue. |
10 |
>> Apparently once it is installed portage will figure out it needs to |
11 |
>> hang onto it. |
12 |
> |
13 |
> And portage will not let me do that even though I have removed the |
14 |
> explicit python use flag from sys-apps/systemd -- in fact it will not |
15 |
> let me reinstall the same version of systemd without the python use |
16 |
> flag. |
17 |
> |
18 |
|
19 |
Can you attach the emerge output of "emerge -1 python-systemd" ? I |
20 |
don't see that anywhere in this thread. |
21 |
|
22 |
As far as I can tell everything should work as long as you emerge that |
23 |
first, or on the same command line as fail2ban, as the bug indicates. |
24 |
You shouldn't have to mess with any systemd USE flag settings if |
25 |
you're on ~amd64, and in theory touching the flag won't change |
26 |
anything anyway. |
27 |
|
28 |
-- |
29 |
Rich |