GNOME users are stuck with it. Most others are not. You did not provide the full package dependency tree, so we cannot see why you are scheduled to merge the packages which require systemd. Mask systemd and the immediate reverse dependencies for it, then try again.

That's because it shouldn't be needed. I'm guessing something on your system is set up in a way that causes issues (either something masked that shouldn't be or an older ebuild that needs to be updated [maybe in an overlay?])

I would recommend trying to figure out what is causing the issue and fixing it, it will probably cause more issues down the road for you is all.

If you're not using systemd, you need remove sys-power/upower and install sys-power/upower-pm-utils.

Or, if you are like me and you couldn't care less about power-management bells and whistles, just get rid of upower altogether: add "-upower" to your USE flags in make.conf. Doing that just made my life a lot simpler.

I know that most times things like this happen because users are unable to read what they have just in front of their faces.

But we have to admit as well that having upower, and thus systemd, as a default is quite strange for a distro that's not supposed to default to systemd. I guess some bug filling is due here._________________Gentoo Handbook | My website

My bad, I understand that gentoo now uses systemd because of this, I did all the steps in the wiki to migrate to systemd, resulting in non-usable system.

STOP SPREADING FUD!
Gentoo uses systemd as much as it uses vanilla-sources for its kernel or lilo for its boot manager.

The user has a choice, Gentoo ONLY forces python,bash,portage (plus a few other little things) to ensure the system can be managed. EVERYTHING else is purely dependencies of user chosen packages.

upower (upstream) changed to depend on systemd. If you CHOOSE to stay with upower obviously you will need systemd because upower demands it.
specifics surrounding upower on gentoo and co are different and are ~arch specific iirc, testing ground for mitigation._________________The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king

My bad, I understand that gentoo now uses systemd because of this, I did all the steps in the wiki to migrate to systemd, resulting in non-usable system.

STOP SPREADING FUD!
Gentoo uses systemd as much as it uses vanilla-sources for its kernel or lilo for its boot manager.

The user has a choice, Gentoo ONLY forces python,bash,portage (plus a few other little things) to ensure the system can be managed. EVERYTHING else is purely dependencies of user chosen packages.

upower (upstream) changed to depend on systemd. If you CHOOSE to stay with upower obviously you will need systemd because upower demands it.
specifics surrounding upower on gentoo and co are different and are ~arch specific iirc, testing ground for mitigation.

upower (upstream) changed to depend on systemd. If you CHOOSE to stay with upower obviously you will need systemd because upower demands it.

Then I think that portage should handle the transition to sys-power/upower-pm-utils automatically when systemd is not present as a use flag in make.conf. If I have understood correctly, this could be handled by a virtual.

Naib wrote:

specifics surrounding upower on gentoo and co are different and are ~arch specific iirc, testing ground for mitigation.

In my case, turning off the global "systemd" USE flag has seemingly prevented upower-0.9.23-r2 from pulling in systemd.

However, this state of affairs confuses me. If systemd is an optional dependency of upower-0.9.23-r2, as seems to be the case(?), then shouldn't the dependency graph have shown "sys-apps/systemd-212-r5 (systemd? >=sys-apps/systemd-200) amd64" instead?

upower (upstream) changed to depend on systemd. If you CHOOSE to stay with upower obviously you will need systemd because upower demands it.

That's wrong, you are oversimplifying a complex issue. New upower is meant also for non-systemd users.

XavierMiller wrote:

Did you read the news ? upower is for systemd, upower-pm-utils is for non-systemd.

That's not what the news item said. That's oversimplifying the issue. It says "or" followed by "# emerge --oneshot --noreplace '>=sys-power/upower-0.99.0'" in the non-systemd section. Meaning that new UPower is for non-systemd users too.

If it had been easy as you make it sound, somekind of USE="systemd" would have been possible, and Portage would be able to solve it more sanely, but it's not that easy because Gentoo offers so many different setups to have, more than
other distributions.

Last edited by SamuliSuominen on Thu Jun 05, 2014 12:12 pm; edited 1 time in total

upower (upstream) changed to depend on systemd. If you CHOOSE to stay with upower obviously you will need systemd because upower demands it.

That's wrong, you are oversimplifying a complex issue. New upower is meant also for non-systemd users.

It was over-simplified to stress gentoo doesn't actually demand stuff like this_________________The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king

My bad, I understand that gentoo now uses systemd because of this, I did all the steps in the wiki to migrate to systemd, resulting in non-usable system.

STOP SPREADING FUD!

Naib ... that doesn't read like FUD but a combination of language use (note they are located in Spain, and therefore probably not a native english speaker) and the fact that having being presented with systemd as a dependency had assumed this was a *necessary* upgrade path. That's an easy mistake to make given output from emerge.

Naib wrote:

The user has a choice, Gentoo ONLY forces python,bash,portage (plus a few other little things) to ensure the system can be managed. EVERYTHING else is purely dependencies of user chosen packages.

Yes, but when systemd has the stated goal of a "standard base system", and when dependencies are "gently pushing" that "standard base system" then at some point there will be no "choice" involved but to adopt that "standard base system". For users who don't know how to go about avoiding said "gentle push" and have come to depend on various components working with their currently installed init then this "choice" is not simply a matter of "you have the choice", because that "choice" can involve technical understanding that the user may not have, and/or involve abandoning some functionality.

Yes, but when systemd has the stated goal of a "standard base system", and when dependencies are "gently pushing" that "standard base system" then at some point there will be no "choice" involved but to adopt that "standard base system". For users who don't know how to go about avoiding said "gentle push" and have come to depend on various components working with their currently installed init then this "choice" is not simply a matter of "you have the choice", because that "choice" can involve technical understanding that the user may not have, and/or involve abandoning some functionality.

Funny post but... I still have a choice and my choice is to NOT install systemd. And it is still working.
Of course it needs a bit technical understanding and a bit googling, too. But who's using Gentoo without this skills?! I expect this from a Gentoo-user, otherwise there are many "simpler" distros out there (even if I'm missing the comfort of Portage in most other distros ).

I am sure at some point some REALLY nasty update will pretty much force systemd on the general user so much so that the effort to not use it will be a massive detriment to the end-user. But that isn't now (wait till apache/nginx depends on sysd for instance ..)_________________The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king