1 |
On Tue, Sep 16, 2014 at 7:07 PM, Michael Orlitzky <mjo@g.o> wrote: |
2 |
> On 09/16/2014 11:51 AM, Alexander Kapshuk wrote: |
3 |
>> Recently, I updated xfce-extra/xfce4-power-manager to version 1.3.1, |
4 |
>> which is unstable, in order to prevent lvm2 from being pulled in as a |
5 |
>> dependency. |
6 |
>> |
7 |
>> [ebuild UD ] xfce-extra/xfce4-power-manager-1.3.0 [1.3.1] |
8 |
>> USE="policykit udisks%* -debug -networkmanager -systemd (-lxpanel%)" |
9 |
>> XFCE_PLUGINS="brightness -battery" 0 kB |
10 |
>> |
11 |
>> Total: 6 packages (1 downgrade, 4 new, 1 in new slot), Size of downloads: 0 kB |
12 |
>> |
13 |
>> emerge trying to downgrade a package, Is that a bug or feature? This |
14 |
>> is the first time I've encountered it. I googled it as well, but so |
15 |
>> far found nothing relevant. |
16 |
> |
17 |
> Version 1.3.1 (which you had installed) used two XFCE_PLUGINS: "battery" |
18 |
> and "brightness". The newer 1.4.0 only uses "power". Since you still |
19 |
> have "brightness" in your XFCE_PLUGINS, it's pulling in the only version |
20 |
> that supports that, the previous 1.3.0. Try replacing "brightness" with |
21 |
> "power" in your XFCE_PLUGINS. |
22 |
> |
23 |
> |
24 |
|
25 |
Replacing brightness with power in XFCE_PLUGINS, followed by running |
26 |
'emerge -avuND @world', still tried to downgrade the package in |
27 |
question. |
28 |
|
29 |
I then ran 'emerge -avuND '>xfce-extra/xfce4-power-manager-1.3.1' |
30 |
which suggested adding '=xfce-extra/xfce4-power-manager-1.4.0 ~x86' to |
31 |
/etc/portage/package.accept_keywords. |
32 |
|
33 |
I did that, followed by running 'emerge -avuND @world', which pulled |
34 |
in xfce-extra/xfce4-power-manager-1.4.0. |
35 |
|
36 |
Thanks. |