When an emerge -C program_name is done, the program is unmerged. However on the next emerge -p world it says "*** Package in world file is not installed: program_name" and the world file still lists the package you unmerged. Reproducible: Always Steps to Reproduce: 1. Emerge something 2. Unmerge it 3. emerge -p world Actual Results: *** Package in world file is not installed: on emerge -p world, but it does successfully uninstall. Expected Results: Have deleted the entry from the world file. System uname: 2.4.20-ck2 i686 AMD Athlon(tm) processor GENTOO_MIRRORS="ftp://ftp.gtlib.cc.gatech.edu/pub/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="/mnt/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="oss apm crypt libg++ libwww mikmod ncurses nls pdflib qtmt quicktime zlib gdbm berkdb slang readline svga tcltk java guile sdl gpm tcpd pam ssl perl python imlib motif X x86 arts aalib avi cdr dga dvd encode -esd gif -gtk2 jpeg kde qt imap mmx mozilla mpeg png truetype xv xmms spell -gtk -gnome alsa xml xml2 mysql opengl oggvorbis cups 3dnow usb" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-tbird -Os -pipe -fpeephole -fgcse -mmmx -m3dnow -ffast-math -fforce-addr -fomit-frame-pointer -funroll-loops -falign-functions=4 -maccumulate-outgoing-args" CXXFLAGS="-march=athlon-tbird -Os -pipe -fpeephole -fgcse -mmmx -m3dnow -ffast-math -fforce-addr -fomit-frame-pointer -funroll-loops -falign-functions=4 -maccumulate-outgoing-args" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache buildpkg" If you look at features in my makeconf I have # packages that are merged. FEATURES="buildpkg" # # RSYNC_RETRIES sets the number of times portage will attempt to retrieve So this may be another bug.
Known issue. Fixed in 2.0.47-r1
