Summary: | ncurses-5.4-r5 fails to emerge due to not being unpacked properly | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Kadmos <bcml> |
Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kadmos
2004-09-29 23:03:19 UTC
you neglected to provide `emerge info` like the bug report page says to also, what stage tarball are you starting with ? Portage 2.0.50-r11 (default-x86-2004.2, gcc-3.3.3, glibc-2.3.3.20040420-r0, 2.4.25_pre7-gss-r9) ================================================================= System uname: 2.4.25_pre7-gss-r9 i586 Gentoo Base System version 1.4.16 Autoconf: Automake: ACCEPT_KEYWORDS="" AUTOCLEAN="yes" CFLAGS="-march=i686 -Os -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=i686 -Os -pipe -fomit-frame-pointer" DISTDIR="/mnt/dumbledore-scratch/distfiles" FEATURES="autoaddcvs ccache distcc userpriv" GENTOO_MIRRORS="ftp://mirror.pacific.net.au/linux/Gentoo/ http://mirror.pacific.net.au/gentoo ftp://planetmirror.com.au/pub/gentoo" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/home/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" USE="X gtk gtk2 mmx x86" I am using a stage1 tarball (as above). i dont know what 'as above' means because we have many stage1 tarballs i'm going to assume you mean the i686 stage1 from 2004.2 Ah, now I see what you mean the tarball is: stage1-x86-2004.2.tar.bz2.md5 Obviously that should be: stage1-x86-2004.2.tar.bz2 (I don't fancy my chances of using a md5 as a tarball... :-P ) I have attempted to reproduce the problem on another system, but it works fine. I'll have to look into this a bit more and see if I can find out a bit more of what is causing the problem. For now I'll close the bug... |