>=systemd-221 is coming with -without-python
# Moved to dev-python/python-systemd
however fail2ban is depending on systemd built with python, this it blocks upgrading systemd above version 221
No --backtrace= or removing/reemerging systemd or fail2ban will resolve this blocker. However if you emerge python-systemd manually and add it to your world then the blocker is gone.
No clues how one can do to check for versions of systemd or test if it has been compiled with python support but in case pyton support is missing it should depend on python-systemd
AFAICT that's already in place.
(In reply to Zoltán Maróti from comment #0)
> However if you emerge python-systemd manually and add it to your
> world then the blocker is gone.
Oh, so it does work?
You don't even need to add it to world. Just installing it with --oneshot is enough to give portage the kick in the but it needs.
(In reply to Mike Gilbert from comment #3)
> You don't even need to add it to world. Just installing it with --oneshot is
> enough to give portage the kick in the but it needs.
This has come up on gentoo-user. It seems like there is some kind of bug here, if not in the ebuild then in the resolver. Granted, portage getting stuck on conflict resolution is nothing new.
*** Bug 559324 has been marked as a duplicate of this bug. ***
Giving this to the portage team.
To summarize: fail2ban has this dependency:
|| ( dev-python/python-systemd sys-apps/systemd[python(-)] )
>=sys-apps/systemd-220 no longer has a 'python' USE flag. So, portage has two solutions to the above dependency:
1. Hold sys-apps/systemd to a version less than 220.
2. Install dev-python/python-systemd.
Currently, portage chooses option 1, which is less than ideal.
So, we want it prefer choices where the latest unmasked version matches.
*** Bug 579516 has been marked as a duplicate of this bug. ***
The fact that sys-apps/systemd is already installed will tend to increase affinity for the sys-apps/systemd[python(-)] choice, so we'll need it to account for the fact that the choice prevents an update to a newer version of sys-apps/systemd.
*** Bug 601422 has been marked as a duplicate of this bug. ***
I just discovered that `dev-python/python-systemd` does not yet seem to support `PYTHON_TARGETS=python3_6`.