Bug 65878 – ncurses-5.4-r5 fails to emerge due to not being unpacked properly

• Status: RESOLVED INVALID
• Product: Portage Development

[Description Kadmos 2004-09-29 23:03:19 UTC]

I am bootstrapping a new system (on an existing gentoo system) but bootstrap fails to emerge ncurses. From what I can gather from the error messages (and poking around) portage fails to unpack the ncurses tarball and then fails when trying to patch the non-existant ncurses source.

Reproducible: Always
Steps to Reproduce:
1. untar stage1
2. chroot, env-update, source /etc/profile, edit make.conf, emerge sync etc etc
3. ./scripts/bootsrap.sh

Actual Results:  
>>> /usr/share/info/sed.info-1.gz
>>> /usr/share/info/sed.info-2.gz
>>> sys-apps/sed-4.0.9 merged.
>>> emerge (3 of 6) sys-libs/ncurses-5.4-r5 to /
>>> md5 src_uri ;-) ncurses-5.4.tar.gz
>>> Unpacking source...
>>> Unpacking ncurses-5.4.tar.gz to /home/tmp/portage/ncurses-5.4-r5/work
/usr/sbin/ebuild.sh: line 25: cd:
/home/tmp/portage/ncurses-5.4-r5/work/ncurses-5.4: No such file or directory
 * Applying ncurses-5.4-xterm.patch...

 * Failed Patch: ncurses-5.4-xterm.patch!
 *
 * Include in your bugreport the contents of:
 *
 *   /home/tmp/portage/ncurses-5.4-r5/temp/ncurses-5.4-xterm.patch-28753.out


!!! ERROR: sys-libs/ncurses-5.4-r5 failed.
!!! Function epatch, Line 400, Exitcode 0
!!! Failed Patch: ncurses-5.4-xterm.patch!



In the ../portage/ncurses-5.4-r5/work directory is a single file:
ncurses-5.4.tar

From what I understand by the time the emerge (as above) gets to the patching
stage this tarball should be both uncompressed and unpacked. Obviously it is
still tar'ed. (Which in my inexpert deduction is the problem).

--- ncurses-5.4-r5.ebuild says (begin) ---
src_unpack() {
        unpack ${A}

        cd ${S}
        epatch ${FILESDIR}/${P}-xterm.patch
        # Bug #42336.
        epatch ${FILESDIR}/${P}-share-sed.patch
        gnuconfig_update
}
---ncurses ebuid end---

---ncurses emerge log (ncurses-5.4-xterm.patch-28753.out) begin---
***** ncurses-5.4-xterm.patch *****

===============================================================

PATCH COMMAND:  patch -p0 -g0 < /usr/portage/sys-libs/ncurses/files/ncurses-5.4-
xterm.patch

===============================================================
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- ncurses-5.3/misc/terminfo.src.orig 2002-10-05 20:40:53.000000000 +0200
|+++ ncurses-5.3/misc/terminfo.src      2003-05-23 15:50:57.000000000 +0200
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
===============================================================

PATCH COMMAND:  patch -p1 -g0 < /usr/portage/sys-libs/ncurses/files/ncurses-5.4-
xterm.patch

---end ncurses log---
NB: The ncurses log is an extract only (it being rather long), the above repeats
as far as I can tell however.

[Comment 1 SpanKY 2004-09-30 08:27:13 UTC]

you neglected to provide `emerge info` like the bug report page says to

also, what stage tarball are you starting with ?

[Comment 2 Kadmos 2004-09-30 17:25:06 UTC]

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).

[Comment 3 SpanKY 2004-09-30 17:37:37 UTC]

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

[Comment 4 Kadmos 2004-09-30 17:48:14 UTC]

Ah, now I see what you mean the tarball is:
stage1-x86-2004.2.tar.bz2.md5

[Comment 5 Kadmos 2004-09-30 17:50:54 UTC]

Obviously that should be:
stage1-x86-2004.2.tar.bz2
(I don't fancy my chances of using a md5 as a tarball... :-P )

[Comment 6 Kadmos 2004-10-02 18:15:28 UTC]

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...