On 06/06/2014 16:34, Gevisz wrote: > After today's emerge-webrsync, I have found out that usual > # emerge --update --deep --with-bdeps=y --newuse --ask world > does not work, trying but being unable to emerge systemd. > > As I have found out, the reason for it was that upower > suddenly decided that it needs systemd but, for some > (lucky :) reason, it could not be emerged as my system > uses OpenRC. > > The latest news said the following: > > "UPower discontinued hibernate and suspend support in favor of systemd. > Because of this, we have created a compability package at > sys-power/upower-pm-utils which will give you the old UPower with > sys-power/pm-utils support back. > Some desktops have integrated the sys-power/pm-utils support directly > to their code, like Xfce, and as a result, they work also with the new > UPower as expected. > > All non-systemd users are recommended to choose between: > > # emerge --oneshot --noreplace 'sys-power/upower-pm-utils' > > or > > # emerge --oneshot --noreplace '>=sys-power/upower-0.99.0' > > However, all systemd users are recommended to stay with > sys-power/upower." > > However, that news did *not* say that without > # emerge --oneshot --noreplace 'sys-power/upower-pm-utils' > it is impossible to update the system even if you use xfce.
The news item is a compromise as the problem you ran into is really a very minor one; it's the presence of systemd and two blocking upower packages that cause confusion. Extra points for the magic flame war-inducing trigger-word "systemd" - see the enormous threads here and on -dev for proof. So the news item clarifies that you are not being forced to use systemd and explains the alternatives in a concise manner. Once you have that done, anything that comes next is simple routine portage blockers which you are expected to know how to deal with, and are not at all worthy of mention in a news item. > Only after executing the last command, which installed > upower-pm-utils and unistalled upower, the > # emerge --update --deep --with-bdeps=y --newuse --ask world > worked as desired. > > upower was not in my world file, so I think it's a some kind of a bug. It's not a bug and upower is not supposed to be in world. It's a simple dep library that portage will pull in if you have any other packages that need it. Keep it and upower-pm-utils out of world so that Samuli's next planned phase of this change in UPower will go smoothly. The reason for all the confusion is due to how portage works internally. Briefly, it sees you have a choice between upower and upower-pm-utils and usually ends up picking upower. It's similar to virtuals where portage doesn't know what you want so just picks the first in the list. If you want the second, then you have to emerge it yourself first, stopping portage from deciding. As I said above, this simple package addition produces the magic flamewar trigger word "systemd" whcih always gets half the audience very very upset indeed. -- Alan McKinnon alan.mckin...@gmail.com
