When I updated my system, I found out that "emerge -up system" and "emerge -p system" gave me different order for the packages to be updated. For my understanding wrong order of the packages can lead some packages to be linked for the old version, which then is updated to newer version. Don't know if this is very serious or not serious at all, because I don't have enough knowledge of portage. I have specified ACCEPT_KEYWORDS="~x86" in my make.conf emerge --version gives: Portage 2.0.44 (default-1.0, gcc-2.95.3, glibc-2.2.5-r7) **************************************************************** emerge -up system These are the packages that I would merge, in order. Calculating system dependencies ...done! [ebuild U ] sys-devel/gettext-0.11.5-r1 [ebuild U ] sys-apps/gawk-3.1.1-r1 [ebuild U ] sys-apps/baselayout-1.8.5.4 [ebuild U ] sys-devel/binutils-2.13.90.0.14 [ebuild U ] net-ftp/ftp-0.17-r2 [ebuild U ] sys-apps/cpio-2.5 [ebuild U ] sys-apps/modutils-2.4.22 [ebuild U ] sys-apps/procps-3.1.1 [ebuild U ] sys-apps/psmisc-21.2 [ebuild U ] sys-apps/sed-4.0.3 [ebuild U ] sys-apps/texinfo-4.3 [ebuild U ] sys-devel/bin86-0.16.0 [ebuild U ] sys-devel/flex-2.5.23 **************************************************************** emerge -p system These are the packages that I would merge, in order. Calculating system dependencies ...done! [ebuild U ] sys-apps/gawk-3.1.1-r1 [ebuild U ] sys-apps/baselayout-1.8.5.4 [ebuild U ] sys-devel/binutils-2.13.90.0.14 [ebuild U ] net-ftp/ftp-0.17-r2 [ebuild U ] sys-apps/cpio-2.5 [ebuild U ] sys-apps/modutils-2.4.22 [ebuild U ] sys-apps/procps-3.1.1 [ebuild U ] sys-apps/psmisc-21.2 [ebuild U ] sys-apps/sed-4.0.3 [ebuild U ] sys-apps/texinfo-4.3 [ebuild U ] sys-devel/bin86-0.16.0 [ebuild U ] sys-devel/flex-2.5.23 [ebuild U ] sys-devel/gettext-0.11.5-r1
what does `emerge info` show ?
root@voltage ~ > emerge info Portage 2.0.44 (default-1.0, gcc-2.95.3, glibc-2.2.5-r7) ================================================================= System uname: 2.4.19-gentoo-r9 i686 Pentium III (Coppermine) USE="x86 apm avi crypt cups encode jpeg libg++ mikmod mmx mpeg ncurses pdflib qt mt quicktime spell truetype xml2 xmms xv berkdb esd gdbm gif gpm gtk guile imlib java libwww motif mozilla nls oggvorbis opengl perl png python qt scanner sdl s lang ssl tcltk tcpd tiff X oss sse dvd cdr -3dnow -aalib -alsa -arts -bonobo -di rectfb -ggi -kde -gnome -gnome-libs -ldap -mysql -nas -pam -postgres -readline - ruby -snmp -svga -tetex" ARCH="x86" COMPILER="" CHOST="i686-pc-linux-gnu" CFLAGS="-march=i686 -O3 -pipe" CXXFLAGS="-march=i686 -O3 -pipe" ACCEPT_KEYWORDS="x86 ~x86" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share /config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" MAKEOPTS="-j2" JDK_HOME="/opt/sun-jdk-1.3.1.04" JAVA_HOME="/opt/sun-jdk-1.3.1.04" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/gentoo"
When doing a install from stage1, if you do a emerge -u system instead of a emerge system, it will fail when emerging autoconf-2.57-r1 (configure says perl was not found). If you do a emerge -u system again, the first thing it does is to try to emerge perl. This means that not only is the order different for emerge without -u and emerge -u, but the order for emerge -u is wrong (autoconf depends on perl). So yes, this is serious. The portage version I am using is 2.0.47-r10
*** This bug has been marked as a duplicate of 16365 ***
