1145962206: ::: completed emerge (50 of 102) sys-apps/debianutils-2.15 to / 1145962206: >>> emerge (51 of 102) sys-apps/portage-2.0.54-r1 to / 1145962206: === (51 of 102) Cleaning (sys-apps/portage-2.0.54-r1::/usr/portage/sys-apps/portage/portage-2.0.54-r1.ebuild) 1145962207: === (51 of 102) Compiling/Merging (sys-apps/portage-2.0.54-r1::/usr/portage/sys-apps/portage/portage-2.0.54-r1.ebuild) 1145962215: === (51 of 102) Post-Build Cleaning (sys-apps/portage-2.0.54-r1::/usr/portage/sys-apps/portage/portage-2.0.54-r1.ebuild) 1145962216: >>> AUTOCLEAN: sys-apps/portage 1145962216: --- AUTOCLEAN: Nothing unmerged. 1145962216: *** RESTARTING emerge via exec() after change of portage version. 1145962216: Started emerge on: Apr 25, 2006 11:50:16 1145962216: *** emerge --emptytree system 1145962217: >>> emerge (1 of 102) sys-devel/patch-2.5.9 to / emerge info Portage 2203-svn (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.3.6-r3, 2.6.16-gentoo-r3 i686) ================================================================= System uname: 2.6.16-gentoo-r3 i686 Intel(R) Pentium(R) M processor 1.86GHz Gentoo Base System version 1.6.14 dev-lang/python: 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.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium3 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O2 -march=pentium3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://www.mirrorservice.org/sites/www.ibiblio.org/gentoo/ http://ftp.mirrorservice.org/sites/www.ibiblio.org/gentoo/ ftp://gentoo.blueyonder.co.uk http://mirrors.blueyonder.co.uk/mirrors/gentoo" LC_ALL="en_GB.utf8" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X a52 aac aalib acpi alsa asf audiofile avi bash-completion berkdb bitmap-fonts bzip2 cdda cddb cdparanoia cdr cjk cli crypt cscope cups curl daap dbus dlloader dri dvd dvdr emboss encode exif expat fam fbcon ffmpeg firefox flac foomaticdb fortran ftp gd gdbm gif glut graphviz gstreamer gtk2 hal idn imagemagick imap isdnlog jack jpeg lcms libcaca libg++ libwww live lua mad maildir matroska mbox mikmod mmx mng motif mp3 mp4 mpeg mysql ncurses nls nptl ogg opengl pam pcre pdf pdflib perl png pppd python quicktime readline real reflection ruby samba sdl session spell spl sse sse2 ssl svg svga tcpd theora tiff truetype truetype-fonts type1-fonts udev unicode usb userlocales vcd vidix vorbis win32codecs x264 xine xorg xv xvid xvmc zlib video_cards_radeon video_cards_fglrx video_cards_vesa video_cards_ati input_devices_keyboard input_devices_mouse userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, INSTALL_MASK, LANG, LDFLAGS, LINGUAS
what flags did you use on the 'emerge' command line?
Oh, sorry, that was emerge -e system Incidentally, if I do, say, `emerge patch portage coreutils` it emerges patch, portage, patch, coreutils and then finishes. But I'm pretty confident that emerge -e system will go on forever - it went through the cycle several times while I was away, and the total number of packages didn't decrease.
This has been fixed in 2.1 already.
Created attachment 85477 [details, diff] use --resume functionality to restart portage This patch is the same one that went into 2.1 for bug 117988 and it applies to 2.0.54 as well.
That patch fixes it, as far as I'm concerened you can commit it and mark this as fixed.
It will be tested and included in the -r2 release.
Adding release@ since this affects stage3 building.
*** Bug 131639 has been marked as a duplicate of this bug. ***
Created attachment 85766 [details, diff] restart_resume-r1.patch Zac posted a new backported patch on IRC for this problem. If everybody could help test it will put us closer to an -r2
*** Bug 131708 has been marked as a duplicate of this bug. ***
(In reply to comment #9) > Created an attachment (id=85766) [edit] > restart_resume-r1.patch > > Zac posted a new backported patch on IRC for this problem. > If everybody could help test it will put us closer to an -r2 Got feedback from a few users who managed to do an -e world with the v2 patch saying it solves the problem. Patch commited to svn. 2.0.54-r2 is expected sometime tmw afternoon (EST)
*** Bug 131832 has been marked as a duplicate of this bug. ***
confirmed that the patch works fine on x86.
*** Bug 132121 has been marked as a duplicate of this bug. ***
I have also some problem.. Portage 2203-svn (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r3, 2.6.16-ck6 i686) ================================================================= System uname: 2.6.16-ck6 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz Gentoo Base System version 1.6.14 ccache version 2.3 [enabled] dev-lang/python: 2.4.2 dev-util/ccache: 2.3 dev-util/confcache: [Not Present] 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.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium4 -msse2 -mfpmath=sse -pipe -ffast-math" 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/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -msse2 -mfpmath=sse -pipe -ffast-math" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig candy ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://darkstar.ist.utl.pt/pub/gentoo/ http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://gentoo.ngi.it http://linuv.uv.es/mirror/gentoo/ http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/" LANG="pt_PT.UTF-8" LC_ALL="pt_PT.UTF-8" LINGUAS="pt_PT" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 X a52 aac aalib acl acpi adns alsa apache2 apm audiofile avi bash-completion berkdb bidi bindist bitmap-fonts bluetooh bono bonobo bzip2 canna caps cdb cdr cjk cli crypt curl dba dbase dbm dbus dga dio directfb dloader dts dv dvb dvd dvdr dvdread emboss encode esd ethereal exif expat fam fastcgi fbcon ffmpeg flac flash foomaticdb fortran ftp gd gdbm gif ginatic glut gmp gnome gnutls gpm gstreamer gtk gtk2 gtkhtml hal hardened iconv idn imagemagick imlib innodb isdnlog java javascript jikes jpeg jpeg2k krb4 lcms libcaca libg++ libwww lm_sensors mad mbox mhash mikmod mime ming mmap mmx mng mono motif mp3 mpeg mpi msn mysql mysqli ncurses nls nptl nptlonly offensive ogg oggvorbis openal opengl openssl pam pcre pda pdf pdflib perl php png posix pppd python qt quicktime readline reflection ruby samba sdl session slang snmp soap sockets speel speex spell spl sse sse2 ssl svg svga szip tcltk tcpd tiff truetype truetype-fonts type1-fonts udev unicode usb userlocales vorbis win32codecs wmf wxwindows xien xml xml2 xmms xorg xosd xpm xv xvid zlib linguas_pt_PT userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, INSTALL_MASK, LDFLAGS, PORTDIR_OVERLAY --- I will patch emerge this afernon and report any news later.
Confirmed! Fully working here now.. :) thanks for all
fixed and released in portage-2.0.54-r2 ~arch
Forgive my stupidity for even asking this, but as someone who wasted days on this problem, why is 2.0.54-r1 even around? In my opinion, it should be removed from portage immediately (reverting to 2.0.54 until 2.0.54-r2 is stable).
(In reply to comment #18) > Forgive my stupidity for even asking this, but as someone who wasted days on > this problem, why is 2.0.54-r1 even around? > > In my opinion, it should be removed from portage immediately (reverting to > 2.0.54 until 2.0.54-r2 is stable). > The patch that fixes it applies to 2.0.54 as well, so the bug theoretically exists in 2.0.54 (and probably all stable versions of portage).
*** Bug 132505 has been marked as a duplicate of this bug. ***
(In reply to comment #19) > (In reply to comment #18) > > Forgive my stupidity for even asking this, but as someone who wasted days on > > this problem, why is 2.0.54-r1 even around? > > > > In my opinion, it should be removed from portage immediately (reverting to > > 2.0.54 until 2.0.54-r2 is stable). > > > > The patch that fixes it applies to 2.0.54 as well, so the bug theoretically > exists in 2.0.54 (and probably all stable versions of portage). I never encountered that problem (on several machines) with 2.0.54 (and judging from the forum posts and bug reports, nobody else did either).
"-e" means "empty tree" or with other words "don't care about the list of already-installed packages". SCNR: this "-e world" has a long tradition in waisting computing hours at gentoo users's installations. ;-) IMO it's time to get rid of that behaviour. Enough computing hours have been wasted by such endless loops. Couldn't portage have some Environment "Switch" Variable which instructs it NOT to restart, eg. sth. equivalent to shell pseudo-code like if [[ "$NEW_VERSION" != "PORTAGE_RESTARTED" ]]; then export PORTAGE_RESTARTED="$NEW_VERSION" # in the case of bug#132505 this would be "2.0.54-r1" # eventually check for second restart? # PORTAGE_RESTARTED_TWICE="$NEW_VERSION" exec "$0" "$@" fi # "else": continue normally so it would at least only re-emerge the first part of packages (in bug#132505: 57 packages) before itself and then finally come to an end? Thanks for fixing that. ;-)
regarding comment#18: this has been in portage for a very long time, AFAIK. Please check if it did not hit You with Your other installations because: - no update to portage was available, before "emerge -e world" was run - You did not change USE-Flags that affect portage - and the same with any packages which would require a rebuild of portage Basically, if You do "-e whatever" and portage itself is in the list of packages, then You'll get an emerge-loop - at least since mid 2005 afaik. :-/
(In reply to comment #22) > Couldn't portage have some Environment "Switch" Variable which instructs it NOT > to restart, eg. sth. equivalent to shell pseudo-code like No such workaround is needed since we already have a patch that fixes the problem correctly.
*** Bug 132663 has been marked as a duplicate of this bug. ***
What do we need to resolve this? Just get arm, m68k, ppc-macos, s390, and sh to stable 2.0.54-r2?
(In reply to comment #26) > What do we need to resolve this? Just get arm, m68k, ppc-macos, s390, and sh > to stable 2.0.54-r2? > or 2.1, it should be canidate for stable "soon" :)
All arches have 2.1-r1 stable now, so this can be resolved.
