This happens for me with both portage-2.0.53 rc3 and rc4. I currently have portage-2.0.51.22-r3 installed, and after doing an esync I get: # emerge -p world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild U ] sys-apps/man-pages-2.08 [2.07] [ebuild U ] sys-libs/glibc-2.3.5-r2 [2.3.5-r1] [ebuild U ] sys-apps/portage-2.0.53_rc4 [2.0.51.22-r3] *** Portage will stop merging at this point and reload itself, recalculate dependencies, and complete the merge. You may avoid the remerging of packages by updating portage on its own. [ebuild U ] x11-base/xorg-x11-6.8.2-r6 [6.8.2-r5] [ebuild U ] sys-apps/util-linux-2.12r [2.12q-r3] [ebuild U ] media-libs/libsdl-1.2.9-r1 [1.2.9] [ebuild U ] sys-apps/coreutils-5.3.0-r2 [5.3.0-r1] # So then, I do an 'emerge portage' which brings me up to 2.0.53_rc4, and I get: # emerge -p world These are the packages that I would merge, in order: Calculating world dependencies ...done! # I'm not sure why this is happening. I would expect it to still show that man-pages, glibc, etc still need to be emerged. As I said, this happened with version 2.0.53_rc3 also - I couldn't find any bugs relating to it, at least not matching my situation; so I ended up masking it in /etc/portage/package.mask. Now, 2.0.53_rc4 is available - and I'm still having the same problem. What can I do in order to debug the issue? I might add that when I add 2.0.53_rc4 to package.mask and revert to 2.0.51.22-r3 that an 'emerge -p world' again shows what I'd expect it to. Reproducible: Always Steps to Reproduce: 1. emerge =sys-apps/portage-2.0.53_rc4 2. emerge -p world 3. Actual Results: There were no packages to update. Expected Results: It should have shown packages that still needed to be updated. Here is emerge info from 2.0.51.22-r3: Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r1, 2.6.14-rc3 i686) ================================================================= System uname: 2.6.14-rc3 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.12.0_pre8 dev-lang/python: 2.2.3-r6, 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 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="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium4 -mno-sse2 -O3 -pipe" CHOST="i686-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 /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-march=pentium4 -mno-sse2 -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://lug.mtu.edu/gentoo http://prometheus.cs.wmich.edu/gentoo http://gentoo.seren.com/gentoo http://gentoo.chem.wisc.edu/gentoo/ http://gentoo.mirrors.tds.net/gentoo" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 X aalib alsa apache2 apm avi berkdb bitmap-fonts cdr crypt cscope cups curl dba directfb doc dvd eds emboss encode fam flac foomaticdb fortran gd gdbm ggi gif gnome gpm gstreamer gtk gtk2 guile imagemagick imlib ipv6 jack java jpeg junit kde ldap libg++ libwww mad mikmod motif mp3 mpeg mysql ncurses nls nptl ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba sasl sdl slang snmp spell sqlite ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts vorbis xine xinerama xml xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS And here is emerge info from 2.0.53_rc4 when it is installed: Portage 2.0.53_rc4 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r1, 2.6.14-rc3 i686) ================================================================= System uname: 2.6.14-rc3 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.12.0_pre8 dev-lang/python: 2.2.3-r6, 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 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="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium4 -mno-sse2 -O3 -pipe" CHOST="i686-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 /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-march=pentium4 -mno-sse2 -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://lug.mtu.edu/gentoo http://prometheus.cs.wmich.edu/gentoo http://gentoo.seren.com/gentoo http://gentoo.chem.wisc.edu/gentoo/ http://gentoo.mirrors.tds.net/gentoo" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 X aalib alsa apache2 apm avi berkdb bitmap-fonts cdr crypt cscope cups curl dba directfb doc dvd eds emboss encode fam flac foomaticdb fortran gd gdbm ggi gif gnome gpm gstreamer gtk gtk2 guile imagemagick imlib ipv6 jack java jpeg junit kde ldap libg++ libwww mad mikmod motif mp3 mpeg mysql ncurses nls nptl ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba sasl sdl slang snmp spell sqlite ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts vorbis xine xinerama xml xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS
Created attachment 69987 [details, diff] Default to --update for world and system targets This restores the behaviour.
I applied that patch, and yes - thank you: it seems to fix the problem. Afterwards, an 'emerge -p world' does what I'd expect it to.
`emerge -up world` is what is normally done, by the way. The regression is only that --update wasn't being automatically added when world or system is specified.
I'm seeing the same problem. Scared the living daylights out of me - thought something had got corrupted. Anywhow, could the priority on this be stepped up to save n00bs like me from heart-attacks?
It's fixed in subversion and there's a patch (that fixes it) attached to the bug. Stepping up priority isn't going to change anything. If something as simple of this scares the living daylights out of you, are you sure you should be running ~arch?
*** Bug 108582 has been marked as a duplicate of this bug. ***
Fixed in 2.0.53_rc5
.
(In reply to comment #5) > It's fixed in subversion and there's a patch (that fixes it) attached to the > bug. Stepping up priority isn't going to change anything. Alrighty - thanks for the fix. Do bear with me - I'm yet to fully understand the finer points of Gentoo's Bugzilla process. I asked for a priority step-up so that it'd be looked at - at that point of time there was no information to the effect that it was. > If something as simple of this scares the living daylights out of you, are you > sure you should be running ~arch? Ah, but I'm on ~arch just to have the living daylights scared out of me every once in a while. ;)
