When I do an emerge -u world, I get a list of files to update. After sometime they are copmpiled and installed. When I run the emerge -ud world again ( without doing a sync ) some of the files are listed again. Reproducible: Always Steps to Reproduce: 1.Emerge -u world 2.Emerge finishes 3. Files still sow in Emerge -u world Expected Results: After the update the list should be empty. Portage 2.0.51-r3 (default-linux/x86/2004.0, gcc-3.3.4, glibc-2.2.5-r2,glibc-2.3.4.20040808-r1, 2.6.7-gentoo-r9 i686) ================================================================= System uname: 2.6.7-gentoo-r9 i686 Pentium III (Coppermine) Gentoo Base System version 1.4.16 distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux-headers-2.4.18,sys-kernel/linux-headers-2.4.19,sys-kernel/linux-headers-2.4.21-r1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium3 -O3 -pipe -frerun-cse-after-loop -msse -mmmx -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/fax /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control /var/spool/fax/etc" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium3 -O3 -pipe -frerun-cse-after-loop -msse -mmmx -fomit-frame-pointer" DISTDIR="/data/distfiles" FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms userpriv" GENTOO_MIRRORS="http://gentoo.mirrors.pair.com/ http://gentoo.ccccom.com http://gentoo.eliteitminds.com" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/data/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="aalib alsa apache2 apm avi berkdb bitmap-fonts cddb cdr crypt cscope cups directfb encode esd f77 fam flac foomaticdb fortran gdbm gif gmail gpm gtk2 gtkhtml guile imagemagick imlib java jpeg libg++ libwww mad mikmod mmx motif mozilla mpeg mysql ncurses nls odbc oggvorbis opengl oss pam pdflib perl png postgres python qt quicktime readline ruby samba scanner sdl slang snmp spell sse ssl svga tcltk tcpd tetex tiff truetype usb x86 xml xml2 xmms xv zlib"
This can happen do to ebuilds which depend on different versions of other ebuilds. The result is a up/downgrade loop. Depending on the ebuild it may be possible to fix some dependency in the portage tree (if you tell us the affected ebuild) or the conflict may be not resolvable globally. In that case you'll have to decide what you want and edit you local configuration files accordingly -> `man portage`
could you provide the output to show what packages are listed twice?
Sorry about that. This time it's gtkmm which keeps showing up.
Better solutions exist. This one is the most friendly right now. Too many of these open.