Bug 558168 – sys-apps/portage fails to switch from sys-apps/systemd[python] to dev-python/python-systemd (prefer choices that match the latest unmasked version)

• Status: CONFIRMED
• Product: Gentoo Linux

[Description Zoltán Maróti 2015-08-19 13:16:28 UTC]

>=systemd-221 is coming with -without-python

                # Moved to dev-python/python-systemd
                --disable-python-devel
                --without-python


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

[Comment 1 Jeroen Roovers (RETIRED) 2015-08-23 07:01:48 UTC]

AFAICT that's already in place.

[Comment 2 Jeroen Roovers (RETIRED) 2015-08-23 07:03:38 UTC]

(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?

[Comment 3 Mike Gilbert 2015-08-23 14:39:54 UTC]

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.

[Comment 4 Richard Freeman 2015-09-01 10:14:05 UTC]

(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.

[Comment 5 Mike Gilbert 2015-09-02 14:57:32 UTC]

*** Bug 559324 has been marked as a duplicate of this bug. ***

[Comment 6 Mike Gilbert 2015-09-02 15:02:10 UTC]

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.

[Comment 7 Zac Medico 2015-09-02 16:35:13 UTC]

So, we want it prefer choices where the latest unmasked version matches.

[Comment 8 Mike Gilbert 2016-04-12 19:56:47 UTC]

*** Bug 579516 has been marked as a duplicate of this bug. ***

[Comment 9 Zac Medico 2017-03-15 15:43:18 UTC]

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.

[Comment 10 Jeroen Roovers (RETIRED) 2017-12-20 03:26:44 UTC]

*** Bug 601422 has been marked as a duplicate of this bug. ***

[Comment 11 Leho Kraav (:macmaN @lkraav) 2017-12-23 06:02:44 UTC]

I just discovered that `dev-python/python-systemd` does not yet seem to support `PYTHON_TARGETS=python3_6`.