Bug 28423 – KDevelop is wrongly upgraded from 3.0 to 2.1.5

• Status: RESOLVED DUPLICATE of bug 33520
• Product: Gentoo Linux

[Description Simon Ejsing 2003-09-11 00:52:46 UTC]

When I emerge -Up kdevelop the script outputs: 
[ebuild     U ] dev-util/kdevelop-2.1.5 [3.0_alpha5] 
 
So it seems that the ebuild files are wrong for kdevelop somehow? 3.0_alpha5 is 
ofcourse an unstable release, but it should see it as > 2.1.5. So -U should disregard this 
"update". 
 
To reproduce, emerge kdevelop-3.0_alpha5 and emerge -Up kdevelop afterwards.

[Comment 1 Patrick Kursawe (RETIRED) 2003-09-11 01:11:13 UTC]

Please add your "emerge info" output.

[Comment 2 Simon Ejsing 2003-09-11 02:05:58 UTC]

emerge info: 
Portage 2.0.49-r3 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.20-gentoo-r5) 
================================================================= 
System uname: 2.4.20-gentoo-r5 i686 Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-march=pentium4 -msse2 -O3 -pipe" 
CHOST="i686-pc-linux-gnu" 
COMPILER="gcc3" 
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" 
CXXFLAGS="-march=pentium4 -msse2 -O3 -pipe" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="sandbox ccache" 
GENTOO_MIRRORS="ftp://gentoo.bzimage.dk/pub/gentoo" 
MAKEOPTS="-j2" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="" 
SYNC="rsync://rsync.bzImage.dk/gentoo-portage" 
USE="x86 oss apm avi crypt cups encode foomaticdb gif jpeg gnome libg++ mad mikmod mmx 
mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gdbm berkdb slang 
readline arts tetex svga java mysql X sdl gpm tcpd pam libwww ssl perl python esd imlib 
oggvorbis gtk qt kde motif opengl mozilla" 
 
 

[Comment 3 Gregorio Guidi (RETIRED) 2003-09-11 02:57:49 UTC]

The meaning of -U is preventing downgrades, but portage does not want to 
downgrade kdevelop, it just want to install also the most stable version. (the 
two versions are slotted and can coexist. 
 

[Comment 4 Simon Ejsing 2003-09-11 03:03:44 UTC]

Why isn't it marked as [ebuild N] then? I don't have kdevelop-2.1.x installed at all, and when I do 
a emerge -p world it outputs: 
[ebuild     U ] dev-util/kdevelop-2.1.5 [3.0_alpha5] 
 
And even with -Up it still wants to upgrade it. 
 
So it must be linked to kdevelop-3.0 somehow. 

[Comment 5 Marius Mauch (RETIRED) 2003-11-24 22:36:43 UTC]

newer portage versions show it as N

*** This bug has been marked as a duplicate of 33520 ***