I'm not sure if this is a problem with portage its self or Evolution's ebuilds; I've emerged Evolution 1.4.0 without problems and it's running fine. Of course I exported ACCEPT_KEYWORDS="~x86". Now since Evolution 1.2.4 was recently unmasked, if I run a emerge -puv world, portage wants to emerge net-mail/evolution-1.2.4 along with app-text/gnome-spell-0.5, gnome-base/gconf-1.0.8-r5, and dev-libs/popt-1.7-r1 which with the exception of popt, are all older versions of what I have currently installed. Now portage reports that the installed evolution is 1.4.0 and the one it wants to install is 1.2.4. I'm running sys-apps/portage-2.0.48-r1. Reproducible: Always Steps to Reproduce: 1. emerge -puv world 2. 3. Actual Results: emerge -puv world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild U ] dev-libs/popt-1.7-r1 [1.6.3] +nls [ebuild U ] gnome-base/gconf-1.0.8-r5 [2.2.0] +nls [ebuild U ] app-text/gnome-spell-0.5 [1.0.4] +nls [ebuild UD] net-mail/evolution-1.2.4 [1.4.0] +ssl +nls -mozilla -ldap -doc +spell -pda -ipv6 +kerberos -kde
its may not seem like an exact duplicate, but it is *** This bug has been marked as a duplicate of 13616 ***
