Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 248469 - app-admin/eselect-1.0.11-r1 - The ebuild phase 'unpack' has exited unexpectedly
Summary: app-admin/eselect-1.0.11-r1 - The ebuild phase 'unpack' has exited unexpectedly
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Portage team
: 247030 (view as bug list)
Depends on:
Blocks: 210077 216231
  Show dependency tree
Reported: 2008-11-23 21:38 UTC by Mark Knecht
Modified: 2008-11-27 20:33 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Mark Knecht 2008-11-23 21:38:04 UTC
emerge fails

Reproducible: Always

Steps to Reproduce:
emerge portage requiring eselect-1.0.11-r1

Actual Results:  
lightning ~ # emerge portage
Calculating dependencies... done!
>>> Verifying ebuild Manifests...
>>> starting parallel fetching pid 27419

>>> Emerging (1 of 3) app-admin/eselect-1.0.11-r1 to /
 * eselect-1.0.11.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                 [ ok ]
 * checking ebuild checksums ;-) ...                                      [ ok ]
 * checking auxfile checksums ;-) ...                                     [ ok ]
 * checking miscfile checksums ;-) ...                                    [ ok ]
 * checking eselect-1.0.11.tar.bz2 ;-) ...                                [ ok ]
>>> Unpacking source...
>>> Unpacking eselect-1.0.11.tar.bz2 to /var/tmp/portage/app-admin/eselect-1.0.11-r1/work
 * Applying eselect-1.0.11-fix-paludis-command.patch ...                  [ ok ]
>>> Source unpacked.
 * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313).

 * Messages for package app-admin/eselect-1.0.11-r1:

 * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313).
lightning ~ #

Expected Results:  
Should emerge without errors

lightning ~ # emerge --info
Portage (default-linux/amd64/2007.0/desktop, gcc-4.1.2, glibc-2.6.1-r0, 2.6.24-rt1 x86_64)
System uname: 2.6.24-rt1 x86_64 AMD Athlon(tm) 64 Processor 3000+
Timestamp of tree: Sun, 23 Nov 2008 17:35:01 +0000
ccache version 2.4 [enabled]
app-shells/bash:     3.2_p33
dev-java/java-config: 1.3.7, 2.1.6
dev-lang/python:     2.5.2-r7
dev-util/ccache:     2.4-r7
sys-devel/autoconf:  2.13, 2.61-r2
sys-devel/automake:  1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1-r1
sys-devel/binutils:  2.18-r3
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   1.5.26
virtual/os-headers:  2.6.23-r3
CFLAGS="-march=k8 -O2 -pipe"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-march=k8 -O2 -pipe"
EMERGE_DEFAULT_OPTS="--with-bdeps y"
FEATURES="ccache distclean distlocks metadata-transfer parallel-fetch sandbox sfperms strict unmerge-orphans userfetch"
LINGUAS="en en_US"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
USE="3dnow 3dnowext X a52 acl acpi alsa amd64 apache2 audiofile berkdb cairo cdr cjk cli cracklib crypt cups dbus dri dvd dvdr dvdread emboss encode evo fam firefox flac fluidsynth fortran gdbm gif gimp gimpprint gnome gpm gstreamer gtk hal i8x0 iconv ipv6 isdnlog jack jack-tmpfs java jpeg kde kerberos ladspa ldap mad midi mikmod mjpeg mmx mmxext mp3 mpeg mudflap mysql mythtv ncurses nls nptl nptlonly ogg opengl openmp oss pam pcre pdf perl png ppds pppd python qt3 qt3support qt4 quicktime radeon readline realmedia reflection sdl session sndfile spell spl sse sse2 ssl svg tcltk tcpd tiff truetype unicode usb v4l v4l2 vorbis xine xml xorg xscreensaver xv xvid zlib" ALSA_CARDS="hdsp9652 hdsp" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en en_US" USERLAND="GNU" VIDEO_CARDS="radeon vesa"

lightning ~ #
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2008-11-26 17:40:55 UTC
Here we go again. :)
Comment 2 Zac Medico gentoo-dev 2008-11-26 18:35:11 UTC
This message usually baffles most people so I've updated it to include some more details:

 * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

In essence, you've probably got either a corrupt bash binary or a hardware problem.
Comment 3 Zac Medico gentoo-dev 2008-11-26 18:40:01 UTC

*** This bug has been marked as a duplicate of bug 205044 ***
Comment 4 Zac Medico gentoo-dev 2008-11-27 19:31:09 UTC
Bug 205044 was an entirely separate issue.

This bug is more similar to bug 244979 and bug 247100.
Comment 5 Zac Medico gentoo-dev 2008-11-27 19:33:04 UTC
Marking as fixed since the error message is more informative in 2.1.6_rc2, as shown in comment #2.
Comment 6 Zac Medico gentoo-dev 2008-11-27 19:39:06 UTC
*** Bug 247030 has been marked as a duplicate of this bug. ***