Summary: | emerge -pu world fails with "IndexError: list index out of range" | ||
---|---|---|---|
Product: | Portage Development | Reporter: | adam morley <axm135> |
Component: | Unclassified | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | hanno, kch, vapier |
Priority: | Low | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
adam morley
2003-06-16 22:14:55 UTC
Does the same thing happen with portage 2.0.48-r1? I have also this problem with Portage 2.0.48-r1. This is my emerge info: Portage 2.0.48-r1 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1) ================================================================= System uname: 2.4.20-patched i686 Intel(R) Pentium(R) 4 CPU 1.60GHz GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config" 7CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 apm avi crypt cups gif jpeg kde libg++ mikmod ncurses nls png spell xml2 xmms xv zlib gdbm berkdb slang readline arts aalib svga guile sdl gpm tcpd pam libwww ssl perl python imlib qt motif mozilla gphoto2 ldap -3dnow gnome bonobo evo gb gtkhtml sse see2 tcltk cdr dga directfb encode esd gtk gtk2 java maildir mpeg oggvorbis oss pcmcia quicktime opengl acpi4linux -pdflib mysql truetype mmx alsa X" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=pentium3 -O3 -pipe -fforce-addr -fomit-frame-pointer -funroll-loops -frerun-loop-opt -frerun-cse-after-loop -falign-functions=4" CXXFLAGS="-march=pentium3 -O3 -pipe -fforce-addr -fomit-frame-pointer -funroll-loops -frerun-loop-opt -frerun-cse-after-loop -falign-functions=4" ACCEPT_KEYWORDS="x86 ~x86" MAKEOPTS="-j8" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox buildpkg ccache userpriv usersandbox" My 50 last emerges: tail -50 /var/log/emerge.log 1055788175: Started emerge on: Jun 16, 2003 20:29:35 1055788175: *** emerge --buildpkg search gimp 1055788207: *** terminating. 1055788246: *** terminating. 1055788254: Started emerge on: Jun 16, 2003 20:30:54 1055788254: *** emerge --buildpkg gimp-freetype 1055788254: >>> emerge (1 of 1) media-gfx/gimp-freetype-0.2-r3 to / 1055788254: === (1 of 1) Cleaning (/usr/portage/media-gfx/gimp-freetype/gimp-freetype-0.2-r3.ebuild) 1055788256: === (1 of 1) Compiling/Packaging (/usr/portage/media-gfx/gimp-freetype/gimp-freetype-0.2-r3.ebuild) 1055788310: === (1 of 1) Merging (/usr/portage/media-gfx/gimp-freetype/gimp-freetype-0.2-r3.ebuild) 1055788314: === (1 of 1) Updating world file (/usr/portage/media-gfx/gimp-freetype/gimp-freetype-0.2-r3.ebuild) 1055788314: === (1 of 1) Post-Build Cleaning (/usr/portage/media-gfx/gimp-freetype/gimp-freetype-0.2-r3.ebuild) 1055788316: >>> AUTOCLEAN: media-gfx/gimp-freetype 1055788316: --- AUTOCLEAN: Nothing unmerged. 1055788316: ::: completed emerge (1 of 1) media-gfx/gimp-freetype-0.2-r3 to / 1055788316: *** Finished. Cleaning up... 1055788335: *** exiting successfully. 1055788338: *** terminating. 1055832698: Started emerge on: Jun 17, 2003 08:51:38 1055832698: *** emerge --buildpkg sync 1055832698: === rsync 1055833105: *** terminating. 1055833768: *** terminating. 1055833971: *** terminating. 1055833977: *** terminating. 1055833996: Started emerge on: Jun 17, 2003 09:13:16 1055833996: *** emerge --buildpkg portage 1055833997: >>> emerge (1 of 1) sys-apps/portage-2.0.48-r1 to / 1055833997: === (1 of 1) Cleaning (/usr/portage/sys-apps/portage/portage-2.0.48-r1.ebuild) 1055833998: === (1 of 1) Compiling/Packaging (/usr/portage/sys-apps/portage/portage-2.0.48-r1.ebuild) 1055834025: === (1 of 1) Merging (/usr/portage/sys-apps/portage/portage-2.0.48-r1.ebuild) 1055834137: === (1 of 1) Post-Build Cleaning (/usr/portage/sys-apps/portage/portage-2.0.48-r1.ebuild) 1055834151: >>> AUTOCLEAN: sys-apps/portage 1055834151: --- AUTOCLEAN: Nothing unmerged. 1055834151: ::: completed emerge (1 of 1) sys-apps/portage-2.0.48-r1 to / 1055834151: *** Finished. Cleaning up... 1055834171: *** exiting successfully. 1055834174: *** terminating. 1055834271: *** terminating. 1055834294: *** terminating. 1055835049: *** terminating. 1055835068: *** terminating. 1055835117: *** terminating. 1055835408: *** terminating. 1055835789: Started emerge on: Jun 17, 2003 09:43:09 1055835789: *** emerge --buildpkg search portage 1055835794: *** terminating. 1055838315: Started emerge on: Jun 17, 2003 10:25:15 1055838315: *** emerge --buildpkg info 1055838318: *** terminating. Do you need any more information to help you to solve the problem? Hi, have the same problem with portage-2.0.48-r1. I didn't emerge or update anything, only thing was an rsync, so the problem must be something in the rsync-tree. I think the error is in the php eclass. If you don't have gd in your USE flags and try to emerge mod_php or php you get the same error message. Now it works. Only waiting some hours and reemerging the portage tree (emerge rsync) the problem it's solved. Does anybody make a successfull emerge world after doing a make rsync at 14:00 AM (GMT) or later? Nope, just synced and still have the error. Same here (synced 1330GMT). Had to go back to php.eclass v1.44 (http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo-x86/eclass/php.eclass?rev=1.44&content-type=text/vnd.viewcvs-markup) to get rid of the error. So it seems definitely the php eclass is the problem. It works with the cvs-version 1.49 of the eclass (1.50 is the current one). This is what has changed: - gd? ( media-libs/libgd >=media-libs/jpeg-6b >=media-libs/libpng-1.2.5 ) + || ( + gd-bundled? () + gd? ( media-libs/libgd >=media-libs/jpeg-6b >=media-libs/libpng-1.2.5 ) + ) vapier, what is the meaning of this change? http://forums.gentoo.org/viewtopic.php?t=61153 Reversing the change from 1.49 to 1.50 would also fix it, I don't know what gd-bundled is supposed to be, but it's not in my use.desc I don't know if this is a good way to deal with it, but putting "" in the empty () and adding a fallback default case to the || in the RDEPEND seems to fix the problem. With USE="gd-bundled", I was seeing "No masked or unmasked ebuilds to satisfy ()". So changing the || clause in the php eclass RDEPEND to look like this: || ( gd-bundled? ( "" ) gd? ( media-libs/libgd >=media-libs/jpeg-6b >=media-libs/libpng-1.2.5 ) ( "" ) ) ...appears to solve things. I'm just wondering, but shouldn't it not be possible to break the portage tree for everyone with a misconfiguration of one file? I don't really know how to file it, but it might be a good feature enhancement to make it say the file/eclass or whatever is bogus and still be able to run without it in some sort of degraded mode. That, or implement some form of change management, so that something like this doesn't happen, though I'm guessing this probably already exists? that bug should be fixed in the latest portage ... it hung around for a while until nick got around to fixing it Bug 12630 This one is fixed. |