| View previous topic :: View next topic |
| Author |
Message |
ian.au
Guru
Joined: 07 Apr 2011
Posts: 592
Location: Australia
|
 Posted: Wed Aug 19, 2015 12:50 pm Post subject: |
 |
|
Sorry, I didn't notice that you were already on 0.9.3
In that case I would try | Code: | | USE="python_single_target_python2_7" emerge -pv fail2ban |
and see if it wants to build |
|
| Back to top |
|
 |
ZMaroti
n00b
Joined: 01 Dec 2005
Posts: 41
|
| Posted: Wed Aug 19, 2015 1:03 pm Post subject: |
|
|
| franzf wrote: | 0.9.3 already is ~ARCH.
What he needs according to the DEP in the ebuild is python-systemd (as already suggested by sling). That package still is ~arch. Add it to package.accept_keywords and the blocker should go away. |
emerging python-systemd manually did the trick, fail2ban itself was not pulling this package itself so probably fail2ban ebuild should be updated later on to add the dependency on python-systemd package
thank you very much for everyone, I am changing the topic solved |
|
| Back to top |
|
|
franzf
Advocate
Joined: 29 Mar 2005
Posts: 4565
|
| Posted: Wed Aug 19, 2015 1:13 pm Post subject: |
|
|
Great you finally got it working 
Are you running completely testing? (ACCEPT_KEYWORDS="~amd64" in make.conf)
Or did you add python-systemd to package.accept_keywords before installing it manually? Because here everything went smooth after adding python-systemd to package.accept_keywords. No seperate installation of python-systemd needed, dep. resolution worked... |
|
| Back to top |
|
|
|
Portage & Programming
