On Tue, Sep 1, 2015 at 7:13 AM, <cov...@ccs.covici.com> wrote: > Rich Freeman <ri...@gentoo.org> wrote: >> >> Sounds like this is covered by: >> https://bugs.gentoo.org/show_bug.cgi?id=558168 >> https://bugs.gentoo.org/show_bug.cgi?id=555502 >> >> It seems to me like this is a portage issue with the resolver. >> Running emerge -1 python-systemd sounds like it fixes the issue. >> Apparently once it is installed portage will figure out it needs to >> hang onto it. > > And portage will not let me do that even though I have removed the > explicit python use flag from sys-apps/systemd -- in fact it will not > let me reinstall the same version of systemd without the python use > flag. >
Can you attach the emerge output of "emerge -1 python-systemd" ? I don't see that anywhere in this thread. As far as I can tell everything should work as long as you emerge that first, or on the same command line as fail2ban, as the bug indicates. You shouldn't have to mess with any systemd USE flag settings if you're on ~amd64, and in theory touching the flag won't change anything anyway. -- Rich
