I incidentally discovered one method for avoid the problem between Entropy and Portage...
If the user "mix" the two installation methods, Portage and Entropy, a problem may appear.... Entropy suggested prior versions of packages as the updated packages.....
viewtopic.php?f=76&t=14132&p=85487&hilit=entropy+confusion#p85487
viewtopic.php?f=83&t=14323&p=83341&hilit=entropy+confusion#p83341
viewtopic.php?f=76&t=14132&p=81506&hilit=entropy+confusion#p81506
To avoid this. DO NOT USE Portage ( emerge ) to updating or install Entropy (equo). Only use Entropy to update Entropy files...
Please not run emerge entropy equo,but use these commands:
$ su and password
#emerge --sync (for updating the packages)
emerge portage (for updating portage)
equo install equo (this will update equo and automatic uppdate entropy and spritz. you may use intead, equo install equo entropy spritz see (*))
equo update --force (this force the Entropy updating and solve the problem)
equo update && equo world
equo update
equo conf update
After some cycles of regular emerge --sync and equo update commands, the problem is solved.
(*) if you use:
# emerge --sync
# layman -d sabayon
#layman -a sabayon
# layman -S
# emerge entropy
You will taken the last testing version of Entropy from the Overlay ( Wolfden procedure). However, after i tried the commands in the begin of this post, the problem not return, only if i runned emerge equo....

