Bugzilla Bug 114067

After upgrading to kde-meta-3.4.3, emerge -uD world wanted to downgrade 
kdelibs to 3.4.1. This was because vimpart was not upgraded and still 3.4.1 
although a stable 3.4.2 was available. After downgrading kdelibs to 3.4.1 
emerge -uD world wanted to upgrade 3.4.3 again... It turns out the ebuild for 
kdeaddons-meta-3.4.3 does not require an update of vimpart to 3.4.2 although 
it should (to avoid cycle mentioned above).    

Reproducible: Always
Steps to Reproduce:
1.emerge -uD kde-meta-3.4.3 
2.emerge -uD world 
3.emerge -uD world 
 
 
Actual Results:  
emerge cycles between 3.4.1 and 3.4.3 

Expected Results:  
upgrade to 3.4.3 

Portage 2.0.51.22-r3 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 
2.6.14-gentoo-r2 x86_64) 
================================================================= 
System uname: 2.6.14-gentoo-r2 x86_64 AMD Opteron(tm) Processor 252 
Gentoo Base System version 1.6.13 
dev-lang/python:     2.3.5-r2, 2.4.2 
sys-apps/sandbox:    1.2.12 
sys-devel/autoconf:  2.13, 2.59-r6 
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 
sys-devel/binutils:  2.16.1 
sys-devel/libtool:   1.5.20 
virtual/os-headers:  2.6.11-r2 
ACCEPT_KEYWORDS="amd64" 
AUTOCLEAN="yes" 
CBUILD="x86_64-pc-linux-gnu" 
CFLAGS="-march=opteron -O2 -pipe" 
CHOST="x86_64-pc-linux-gnu" 
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /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" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" 
CXXFLAGS="-march=opteron -O2 -pipe" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="autoconfig distlocks sandbox sfperms strict" 
GENTOO_MIRRORS="http://128.213.5.34/gentoo 
http://www.ibiblio.org/pub/Linux/distributions/gentoo" 
MAKEOPTS="-j3" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="/usr/local/portage" 
SYNC="rsync://rsync.gentoo.org/gentoo-portage" 
USE="amd64 X alsa arts audiofile avi berkdb bitmap-fonts bzip2 cdr crypt cups 
curl dv dvd dvdr dvdread eds emacs emboss encode exif expat fam ffmpeg flash 
font-server foomaticdb fortran gd gdbm gif glut gpm gstreamer gtk gtk2 idn 
ieee1394 imagemagick imap imlib ipv6 java jpeg kde lcms libwww live lua lzw 
lzw-tiff mad mjpeg mng motif mp3 mpeg ncurses nls nptl odbc ogg opengl pam 
pcre pdflib perl plotutils png postgres ppds python qt quicktime readline 
samba sdl spell ssl tcpd tetex threads tiff truetype truetype-fonts 
type1-fonts udev usb userlocales vorbis wmf xinerama xml2 xpm xv zlib 
userland_GNU kernel_linux elibc_glibc" 
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

Here is a simple diff for the kdeaddons-meta-3.4.3.ebuild which fixes this 
sympton: 
 
diff old.ebuild new.ebuild 
 
19c19 
< $(deprange 3.4.1 $MAXKDEVER kde-base/vimpart) 
--- 
> $(deprange 3.4.2 $MAXKDEVER kde-base/vimpart) 
 

Thanks for the report, this can be fixed as soon as the ppc64 team add the 
ppc64 keyword to vimpart-3.4.2. Probably they missed it because of this bug, 
sorry guys. 

vimpart-3.4.2 stable on ppc64 

Fixed now. 

Thanks