Summary: | After updating portage fails to execute unpack-stage and stops after fetch | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mario Witte <mario.witte> |
Component: | [OLD] Core system | Assignee: | Please assign to toolchain <gcc-porting> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | mholzer |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Logfile of "emerge -v --debug gcc"
log of what emerging the new portage does. |
Description
Mario Witte
2004-02-10 04:19:20 UTC
does your harddisk work ? The harddisk works fine. To make sure I just ran a complete fsck and checked the logfiles for errors, but there is no indication of errors. I'm attaching a logfile of an "emerge -v --debug gcc", perhaps this sheds some light on my problem. Created attachment 25387 [details]
Logfile of "emerge -v --debug gcc"
After checking --verbose and --debug outputs and poking around inside the ebuild-scripts I just found a fairly simple solution: A binary package of portage-2.0.49-r21 (compiled on a different box) installed fine and works. The problem seems to be with the portage-2.0.50-r1 ebuild which doesn't install correctly on this box. I also have this problem. Anything I try to emerge it just acts like i passed -f to emerge. This also happens when I try ebuild /path/to/ebuild.ebuild unpack. Same thing, just gives me an MD5 and stops. I cannot continue using portage I guess. I have to untar an older portage-rescue to get emerge to work again, and I think I've had some ebuilds that won't emerge because I'm not using a new enough version. Untarring a binary version is not going to work for the future. I'd like to know why this happens, and how to fix it. Can someone offer a suggestion? what's RESOLVED WORKSFORME mean anyway? That this doesn't happen to everyone? Shouldn't be closed since it's obvious it doesn't happen to everyone. Anyway, what do I need to do to figure out what's going on here. This started happening to me when I went to sys-apps/portage-2.0.50-r6. Created attachment 31145 [details]
log of what emerging the new portage does.
I don't see anything weird here, but I dunno what I'm looking for.
emerge info: Portage 2.0.50-r1 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 2.6.6-rc3-love4) ================================================================= System uname: 2.6.6-rc3-love4 i686 AMD Athlon(tm) XP 2700+ Gentoo Base System version 1.4.3.13 distcc 2.12.1 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 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /opt/quake3/cpma/server.cfg /usr/X11R6/lib/X11/xkb /usr/kde/2/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/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage_local" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X aalib acl alsa apm avi berkdb bonobo cdr crypt cups dga dvd encode fb fbcon foomaticdb gdbm ggi gif gphoto2 gpm gtk gtk2 guile imlib java joystick jpeg kde kerberos ldap libg++ libwww mad matroska mikmod mmx motif mozilla moznocompose moznoirc mpeg mysql nas ncurses nls nptl nvidia oggvorbis openal opengl oss pam pdflib perl png ppds python qt quicktime readline samba sdl slang slp spell sse ssl svga tcltk tcpd tetex tiff truetype usb v4l x86 xinerama xml2 xmms xv xvid zlib" BTW, I've tried moving make.conf out of the way and using make.conf.example in it's place, and get the same results. |