There is a problem with portage in that the upgrading of evolution via "emerge -UuvD world" differs from "emerge -UuvD evolution. The system I am using was synced yesterday. Here is the output from the commands: emerge -UupvD evolution: ------------------------- root@base storri # emerge -UupvD evolution These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] net-print/foomatic-filters-3.0.0 +cups -samba [ebuild N ] net-print/foomatic-db-engine-3.0.0 [ebuild N ] net-print/foomatic-db-20030716 +cups -ppds [ebuild U ] net-print/foomatic-3.0.0 [2.0.0] emerge -UupvD world --------------------- root@base storri # emerge -UupvD world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild N ] net-print/foomatic-filters-3.0.0 +cups -samba [ebuild N ] net-print/foomatic-db-engine-3.0.0 [ebuild N ] net-print/foomatic-db-20030716 +cups -ppds [ebuild U ] net-print/foomatic-3.0.0 [2.0.0] [ebuild UD] net-mail/evolution-1.2.4 [1.4.3] +ssl +nls +mozilla +ldap -doc +spell -pda -ipv6 +kerberos +kde emerge info: -------------- Portage 2.0.48-r5 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1) ================================================================= System uname: 2.4.20-gentoo-r5 i686 Pentium III (Katmai) GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 X apm berkdb crypt cups evo gdbm gnome gtk2 gpm imap kde kerberos krb4 java ldap maildir mmx motif mozilla mysql ncurses nls oggvorbis opengl pam perl python readline sasl slang spell ssl tcpd xml zlib" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=pentium3 -O3 -pipe" CXXFLAGS="-march=pentium3 -O3 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j5" AUTOCLEAN="yes" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" FEATURES="ccache fixpackages userpriv sandbox" Reproducible: Always Steps to Reproduce: 1. upgrade evolution from 1.2.4 to 1.4.3 via emerge -UuvD world 2. emerge -UupvD world Actual Results: Emerge reports that evolution 1.4.3 should be downgraded to 1.2.4 Expected Results: Emerge should not downgrade evolution but do any other upgrades that are required.
I have a similar problem although the reason for it doesn't seem to be portage's fault. I tried to 'emerge -uU -p world' today and portage wanted to downgrade my evolution to 1.2.4 as well: [ebuild U ] sys-libs/db-3.2.9-r7 [3.2.9-r2] [ebuild U ] sys-devel/distcc-2.9 [2.8-r2] [ebuild U ] app-editors/vi-3.7-r4 [3.7-r3] [ebuild U ] sys-apps/util-linux-2.11z-r6 [2.11z-r4] [ebuild U ] dev-util/guile-1.6.4 [1.4.1] [ebuild U ] dev-java/java-config-0.2.8-r1 [0.2.8] [ebuild U ] net-www/mozilla-1.4-r3 [1.4-r2] [ebuild UD] net-mail/evolution-1.2.4 [1.4.3] [ebuild U ] app-office/gnumeric-1.0.13-r1 [1.0.13] [ebuild U ] net-misc/whois-4.6.6-r2 [4.6.6] The real reason for this evolution downgrade in my case is that gnumeric for some reason (gtk2 problems?) has a dependency limiting evolution version number. /usr/portage/app-office/gnumeric/gnumeric-1.0.13-r1.ebuild RDEPENDs have an entry for evolution: evo? ( <net-mail/evolution-1.3 )" I'm really not that familiar with portage and it's depency handling but my guess is that this causes the downgrade. Is this gnumeric's evolution version limitation really needed? - jn@zeizei.net
USE flags that caused the bug to occur were: USE="-* evo gtk2 imap kerberos ldap maildir sasl xml2" USE flags that worked around the bug were: USE="-* oss kerberos gtk2 imap sasl apm avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gtkhtml alsa gdbm berkdb slang readline arts tetex bonobo svga tcltk java guile mysql X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl mozilla ldap snmp cdr"
I have almost the same problem. "emerge -uD world" will upgade evolution to 1.4.3 if the version I have installed is 1.2.4. A second "emerge -uD world" (if 1.4.3 is installed) will downgrade to 1.2.4. If I continue this, I will forever be upgrading and downgrading. I do have Gnumeric installed. If this is a USE flag, which one?
David: Gnumeric's ebuild checks for 'evo' USE flag and if defined it wants to have Evolution < 1.3, which is 1.2.4 in this case. So if you don't have USE=evo portage probably doesn't want to downgrade.
this isn't really a portage bug. gnumeric 0.x depends on evolution-1.2.x if you have "evo" in your USE. remove that and it won't keep on trying to downgrade.
