build.log

bzr-gtk-0.100.0:20110925-092235.log (text/plain), 2.14 KB, created by Agostino Sarubbo on 2011-09-25 09:26:30 UTC

 * Package:    dev-vcs/bzr-gtk-0.100.0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        amd64 elibc_glibc gconf gnome-keyring gpg kernel_linux multilib nautilus sourceview userland_GNU
 * FEATURES:   sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking bzr-gtk-0.100.0.tar.gz to /tmp/portage/dev-vcs/bzr-gtk-0.100.0/work
>>> Source unpacked in /tmp/portage/dev-vcs/bzr-gtk-0.100.0/work
>>> Preparing source in /tmp/portage/dev-vcs/bzr-gtk-0.100.0/work/bzr-gtk-0.100.0 ...
>>> Source prepared.


!!! Failed to complete python imports. These are internal modules for
!!! python and failure here indicates that you have a problem with python
!!! itself and thus portage is not able to continue processing.

!!! You might consider starting python with verbose flags to see what has
!!! gone wrong. Here is the information we got for this exception:
    cannot import name getstatusoutput

Traceback (most recent call last):
  File "/usr/lib64/portage/bin/ebuild-ipc.py", line 32, in <module>
    import portage
  File "/usr/lib64/portage/pym/portage/__init__.py", line 25, in <module>
    from subprocess import getstatusoutput as subprocess_getstatusoutput
ImportError: cannot import name getstatusoutput
 * The ebuild phase 'prepare' 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.