On 16/09/2014 17:51, Alexander Kapshuk wrote:
> Recently, I updated xfce-extra/xfce4-power-manager to version 1.3.1,
> which is unstable, in order to prevent lvm2 from being pulled in as a
> dependency.
>
> grep xfce-extra/xfce4-power-manager /etc/portage/package.*
> /etc/portage/package.accept_keywords:=xfce-extra/xfce4-power-manager-1.3.1
> ~x86
>
> As I ran 'emerge -avuND @world' today, I got this output:
> These are the packages that would be merged, in order:
>
> Calculating dependencies ..... . .. ..... done!
> [ebuild N ] sys-apps/sg3_utils-1.37 USE="-static-libs" 0 kB
> [ebuild N ] sys-apps/rescan-scsi-bus-1.29 0 kB
> [ebuild N ] sys-block/thin-provisioning-tools-0.3.2-r1 USE="{-test}" 0
> kB
> [ebuild N ] sys-fs/lvm2-2.02.109 USE="readline thin udev (-clvm)
> (-cman) -device-mapper-only -lvm1 -lvm2create_initrd (-selinux)
> -static -static-libs -systemd" 0 kB
> [ebuild NS ] sys-fs/udisks-1.0.5-r1:0 [2.1.3:2] USE="nls -debug
> -remote-access (-selinux)" 0 kB
> [ebuild UD ] xfce-extra/xfce4-power-manager-1.3.0 [1.3.1]
> USE="policykit udisks%* -debug -networkmanager -systemd (-lxpanel%)"
> XFCE_PLUGINS="brightness -battery" 0 kB
>
> Total: 6 packages (1 downgrade, 4 new, 1 in new slot), Size of downloads: 0 kB
>
> emerge trying to downgrade a package, Is that a bug or feature? This
> is the first time I've encountered it. I googled it as well, but so
> far found nothing relevant.
portage is doing what the ebuilds and make.conf tell it to do.
For some reason xfce-power-manager-1.3.1 does not satisfy what the local
install needs but 1.3.0 does. So portage wants to make it so.
Downgrades are not common, but neither are they unusual. It's not a
feature either, it's a necessaity that portage be able to do this.
>
> The list's input would be appreciated.
>
>
>
--
Alan McKinnon
[email protected]
