We have the following dependencies net-im/empathy-3.12.1 (>=net-im/telepathy-mission-control-5.14) net-im/telepathy-mission-control-5.16.1: upower? ( >=sys-power/upower-0.9.11 <sys-power/upower-0.99 ) gnome-base/gnome-settings-daemon-3.12.1 (>=sys-power/upower-0.99) This dependency graph is not satisfiable without masking >=telepathy-mission-control-5.16 or disabling the upower USE flag. This seems to be a roadbump with upgrading to GNOME 3.12.
I have seen upower support is disabled in telepathy-mission-control on Fedora, OpenSuSE and Fedora. In OpenSuSE spec the following is explained: * Tue Nov 19 2013 dimstar@opensuse.org - Drop pkgconfig(upower-glib) BuildRequires: the required API are no longer available in UPower 1.0 and the corresponding functionality is already used from logind. Then, I would change the USE flag to be named "systemd" on telepathy-mission-control, that flag would disable-upower when it's enabled and, then, should solve this for gnome setups (that should run systemd) while allowing other consumers to still prevent systemd running
IMHO the best way to solve this while being friendly to non-Gnome desktops is: 1. rename upower flag to systemd; 2. change the dep to !systemd? ( >=upower-0.9.11 <upower-0.99 ) 3. don't clean out upower-0.9.23-rx for some time.
(In reply to Pacho Ramos from comment #1) Sorry, I didn't read your comment, you already came up with the same solution :)
+ 05 May 2014; Alexandre Rostovtsev <tetromino@gentoo.org> + telepathy-mission-control-5.14.0-r1.ebuild, + telepathy-mission-control-5.14.1.ebuild, + telepathy-mission-control-5.16.1.ebuild, metadata.xml: + Rename USE=upower to USE=-systemd in light of upower-0.99 API changes and + upstream comments (bug #509508, thanks to Mark R. Pariente and Pacho Ramos).
