Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 49142 - 'emerge -e world' does not update all versions of packages and 'emerge depclean' does not want to delete them
Summary: 'emerge -e world' does not update all versions of packages and 'emerge depcle...
Status: RESOLVED DUPLICATE of bug 47921
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Portage team
Depends on:
Reported: 2004-04-27 03:09 UTC by Andre Hinrichs
Modified: 2009-05-26 11:50 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Andre Hinrichs 2004-04-27 03:09:26 UTC
I just did a 'emerge -e world' and saw by doing 'ls -lat /var/tmp/portage' that
not all installed versions all various packages have been updated.
The system is clean, means, 'emerge depclean' does not want to delete anything.
For instance, 'etcat -v python' says:

[ Results for search key           : python ]
[ Candidate applications found : 5 ]

 Only printing found installed programs.

*  dev-lang/python :
        [   ] 2.1.3-r1 (2.1)
        [   ] 2.2.2 (2.2)
        [  I] 2.2.3-r5 (2.2)
        [  I] 2.3.3 (2.3)
        [M~ ] 2.3.3-r1 (2.3)

So, there are two different versions of python installed on my system. This may
be ok, but 'emerge -e world' does only update version 2.3.3.

This appears only for packages, where more than one version is installed.
So, either the not updated version is no longer required and should be deleted by 'emerge depclean', or the package is required and should be updated by 'emerge -e world'.

Here is a list of installed package versions which were not updated by the last
'emerge -e world' command:


Reproducible: Always
Steps to Reproduce:
1.emerge -e world -lat /var/tmp/portage

Portage 2.0.50-r6 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.5-gentoo-r1)
System uname: 2.6.5-gentoo-r1 i686 Pentium III (Coppermine)
Gentoo Base System version 1.4.9
distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.8.3
CFLAGS="-O3 -march=i686 -funroll-loops -pipe"
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/share/config
/usr/lib/mozilla/defaults/pref /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/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=i686 -funroll-loops -pipe"
FEATURES="autoaddcvs ccache sandbox"
USE="X Xaw3d aalib acl alsa apache2 apm arts audiofile avi berkdb bonobo cdr
crypt cups curl dvd emacs encode esd flac flash foomaticdb gd gdbm ggi gif gmp
gnome gphoto2 gpm gtk gtk2 gtkhtml guile icq imagemagick imlib java jpeg kde
lcms ldap leim libg++ libwww mad maildir mikmod motif mozilla mpeg mysql nas
ncurses nls nocardbus odbc oggvorbis opengl oss pam pcmcia pda pdflib perl
plotutils png ppds python qt quicktime readline samba sasl scanner sdl slang
spell ssl svga tcltk tcpd tetex theora tiff truetype unicode usb wmf wxwindows
x86 xml xml2 xmms xv zlib"
Comment 1 Gregorio Guidi (RETIRED) gentoo-dev 2004-04-27 05:48:49 UTC
Probably one of the consequences of bad SLOT handling: bug 4698.
Comment 2 Andre Hinrichs 2004-04-27 07:32:14 UTC
hmm... after reading the whole report of bug 4698 I think it's most likely the
same. It's a pity that they stopped discussing it, since the bug is not fixed yet.
Is there a chance to reactivate the discussion?
Are dependencies to specific SLOTs introduced/implemented?
Comment 3 SpanKY gentoo-dev 2004-04-27 15:04:31 UTC

*** This bug has been marked as a duplicate of 47921 ***
Comment 4 Andre Hinrichs 2004-04-28 01:36:04 UTC
I don't think, that this is a duplicate of bug 47921.
By now, I'll not reopen it before any comments have been arrived.
I would agree to mark this as a duplicate of bug 4698.