There was quite a large update of some 73 packages:
- Code: Select all
>> @@ These are the packages that would be installed:
>> ## [U] [sabayonlinux.org] net-misc/iputils-20101006-r2|0 [20101006|0]
>> ## [U] [sabayonlinux.org] dev-libs/glib-2.32.1|0 [2.30.2|0]
>> ## [U] [sabayonlinux.org] x11-libs/cairo-1.10.2-r2|2 [1.10.2-r2|1]
>> ## [U] [sabayonlinux.org] x11-libs/pango-1.30.0|0 [1.29.4|0]
>> ## [N] [sabayonlinux.org] dev-libs/gobject-introspection-common-1.32.0|0
>> ## [U] [sabayonlinux.org] app-arch/bzip2-1.0.6-r3|0 [1.0.6-r1|0]
>> ## [U] [sabayonlinux.org] dev-lang/python-2.7.2-r3|3 [2.7.2-r3|2]
>> ## [U] [sabayonlinux.org] dev-libs/gobject-introspection-1.32.0|0 [1.30.0-r2|0]
>> ## [U] [sabayonlinux.org] x11-libs/gdk-pixbuf-2.26.1|0 [2.24.0-r1|2]
>> ## [U] [sabayonlinux.org] x11-libs/gtk+-3.4.1|0 [3.2.4-r1|0]
>> ## [U] [sabayonlinux.org] x11-libs/vte-0.32.0|0 [0.30.1-r3|0]
>> ## [U] [sabayonlinux.org] net-libs/libsoup-2.38.0|0 [2.36.1|0]
>> ## [U] [sabayonlinux.org] net-libs/webkit-gtk-1.8.0-r300|0 [1.7.1-r300|0]
>> ## [U] [sabayonlinux.org] dev-libs/dbus-glib-0.98|1 [0.98|0]
>> ## [U] [sabayonlinux.org] dev-libs/gjs-1.32.0|0 [1.30.0|0]
>> ## [U] [sabayonlinux.org] gnome-extra/sushi-0.2.1|1 [0.2.1|0]
>> ## [U] [sabayonlinux.org] sys-libs/glibc-2.13-r4|2 [2.13-r4|1]
>> ## [U] [sabayonlinux.org] x11-drivers/nvidia-userspace-295.40|1 [295.40|0]
>> ## [U] [sabayonlinux.org] app-arch/gzip-1.4|1 [1.4|0]
>> ## [U] [sabayonlinux.org] gnome-base/gsettings-desktop-schemas-3.4.0|0 [3.2.0-r1|0]
>> ## [U] [sabayonlinux.org] gnome-base/librsvg-2.36.0|0 [2.34.2|0]
>> ## [U] [sabayonlinux.org] x11-themes/gtk-engines-2.20.2|3 [2.20.2|2]
>> ## [U] [sabayonlinux.org] x11-themes/gnome-themes-standard-3.4.1|0 [3.2.1|0]
>> ## [U] [sabayonlinux.org] sys-apps/net-tools-1.60_p20120127084908|0 [1.60_p20111120203157|0]
>> ## [U] [sabayonlinux.org] dev-python/pygobject-base-3.2.0|0 [3.0.4|0]
>> ## [U] [sabayon-weekly->sabayonlinux.org] dev-python/pygobject-cairo-3.2.0|0 [3.0.4|0]
>> ## [U] [sabayonlinux.org] dev-python/pygobject-3.2.0|0 [3.0.4|1]
>> ## [U] [sabayonlinux.org] app-arch/xz-utils-5.0.3|1 [5.0.3|0]
>> ## [U] [sabayonlinux.org] app-arch/tar-1.26-r1|0 [1.25-r1|0]
>> ## [U] [sabayonlinux.org] sys-libs/e2fsprogs-libs-1.42.1|0 [1.41.14|0]
>> ## [U] [sabayonlinux.org] sys-fs/e2fsprogs-1.42.1|0 [1.41.14|0]
>> ## [U] [sabayonlinux.org] sys-apps/which-2.20|3 [2.20|2]
>> ## [U] [sabayonlinux.org] sys-apps/sed-4.2.1-r1|1 [4.2.1-r1|0]
>> ## [U] [sabayonlinux.org] dev-libs/libpeas-1.2.0-r1|1 [1.2.0-r1|0]
>> ## [U] [sabayonlinux.org] sys-apps/coreutils-8.16|0 [8.14|0]
>> ## [U] [sabayonlinux.org] app-shells/bash-4.2_p24|0 [4.1_p9|0]
>> ## [U] [sabayonlinux.org] app-admin/perl-cleaner-2.10|1 [2.10|0]
>> ## [U] [sabayonlinux.org] sys-process/psmisc-22.16|0 [22.15|0]
>> ## [U] [sabayonlinux.org] sys-apps/openrc-0.9.9.3|0 [0.9.8.1|0]
>> ## [U] [sabayonlinux.org] sys-devel/base-gcc-4.6.2|3 [4.6.2|2]
>> ## [U] [sabayonlinux.org] net-misc/networkmanager-0.9.4.0-r2|0 [0.9.2.0-r2|0]
>> ## [U] [sabayonlinux.org] net-misc/wget-1.13.4-r1|1 [1.13.4-r1|0]
>> ## [U] [sabayonlinux.org] media-gfx/xsane-0.998-r1|0 [0.998|1]
>> ## [U] [sabayonlinux.org] sys-apps/grep-2.11|1 [2.11|0]
>> ## [U] [sabayonlinux.org] sys-apps/gawk-4.0.0|1 [4.0.0|0]
>> ## [U] [sabayonlinux.org] app-portage/gentoolkit-0.3.0.6|0 [0.3.0.4-r5|0]
>> ## [U] [sabayonlinux.org] dev-python/pygobject-2.28.6-r52|0 [2.28.6-r50|0]
>> ## [U] [sabayonlinux.org] sys-process/procps-3.3.2_p2-r1|0 [3.2.8-r2|0]
>> ## [U] [sabayonlinux.org] app-text/calibre-0.8.47|0 [0.8.46|0]
>> ## [U] [sabayonlinux.org] net-libs/libsoup-gnome-2.38.0|0 [2.36.1|0]
>> ## [U] [sabayonlinux.org] gnome-base/gconf-3.2.5|0 [3.2.3-r1|0]
>> ## [U] [sabayonlinux.org] x11-wm/mutter-3.2.2-r1|0 [3.2.2|0]
>> ## [U] [sabayonlinux.org] sys-apps/findutils-4.5.10-r1|1 [4.5.10-r1|0]
>> ## [U] [sabayonlinux.org] dev-lang/python-2.6.6-r2|1 [2.6.6-r2|0]
>> ## [U] [sabayonlinux.org] sys-devel/patch-2.6.1|1 [2.6.1|0]
>> ## [U] [sabayonlinux.org] sys-devel/binutils-2.22-r1|0 [2.20.1-r1|0]
>> ## [U] [sabayonlinux.org] mail-client/thunderbird-11.0.1|0 [11.0|0]
>> ## [U] [sabayonlinux.org] sys-devel/gcc-4.4.7|0 [4.4.6-r1|0]
>> ## [U] [sabayonlinux.org] sys-apps/texinfo-4.13-r1|1 [4.13-r1|0]
>> ## [U] [sabayon-weekly->sabayonlinux.org] x11-wm/muffin-1.0.2-r1|0 [1.0.2|0]
>> ## [U] [sabayonlinux.org] net-libs/xulrunner-2.0.1-r1|5 [2.0.1-r1|4]
>> ## [U] [sabayonlinux.org] www-client/firefox-11.0|1 [11.0|0]
>> ## [U] [sabayonlinux.org] sys-devel/llvm-3.0-r2|0 [3.0|0]
>> ## [U] [sabayonlinux.org] net-misc/rsync-3.0.9-r2|0 [3.0.8|0]
>> ## [U] [sabayon-weekly->sabayonlinux.org] app-cdr/brasero-3.4.0|0 [3.2.0|0]
>> ## [U] [sabayonlinux.org] sys-devel/base-gcc-4.5.3-r2|0 [4.5.3-r1|6]
>> ## [U] [sabayonlinux.org] sys-devel/gcc-4.5.3-r2|0 [4.5.3-r1|7]
>> ## [U] [sabayonlinux.org] dev-libs/libffi-3.0.11|0 [3.0.10|0]
>> ## [U] [sabayonlinux.org] sys-devel/gnuconfig-20120116|0 [20110202|0]
>> ## [U] [sabayonlinux.org] sys-apps/diffutils-3.2|1 [3.2|0]
>> ## [U] [sabayonlinux.org] sys-apps/less-445-r1|1 [445-r1|0]
>> ## [U] [sabayonlinux.org] sys-apps/file-5.11|1 [5.11|0]
>> ## [U] [sabayonlinux.org] sys-apps/kbd-1.15.3|1 [1.15.3|0]
>> ## [U] [sabayonlinux.org] sys-devel/make-3.82-r1|1 [3.82-r1|0]
>> @@ These are the packages that would be removed (conflicting/substituted):
>> ## [W] [from: sabayonlinux.org] app-misc/realpath-1.16
There were several error messages during the update and most were similar to this one:
- Code: Select all
>> ++ (63/74) >>> sys-devel/llvm-3.0-r2
>> ## Unpacking: sys-devel:llvm-3.0-r2~0.tbz2
>> ## SPM: setup phase
/usr/lib/portage/bin/phase-functions.sh: line 140: /usr/bin/python2.7: No such file or directory
* ERROR: sys-devel/llvm-3.0-r2 failed (setup phase):
* filter-bash-environment.py failed
*
* Call stack:
* ebuild.sh, line 466: Called preprocess_ebuild_env
* phase-functions.sh, line 159: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
* phase-functions.sh, line 140: Called die
* The specific snippet of code:
* "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
*
* If you need support, post the output of 'emerge --info =sys-devel/llvm-3.0-r2',
* the complete build log and the output of 'emerge -pqv =sys-devel/llvm-3.0-r2'.
* The complete build log is located at '/var/lib/entropy/logs/sys-devel:llvm-3.0-r2:20120423-182758.log'.
* The ebuild environment file is located at '/var/tmp/entropy/packages-nonfree/x86/5/sys-devel_llvm-3.0-r2_0.tbz2/portage/sys-devel/llvm-3.0-r2/temp/environment'.
* S: '/var/tmp/entropy/packages-nonfree/x86/5/sys-devel_llvm-3.0-r2_0.tbz2/portage/sys-devel/llvm-3.0-r2/work/llvm-3.0'
/usr/lib/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.7: No such file or directory
* The ebuild phase 'setup' 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.
/usr/lib/portage/bin/phase-functions.sh: line 140: /usr/bin/python2.7: No such file or directory
* ERROR: sys-devel/llvm-3.0-r2 failed:
* filter-bash-environment.py failed
*
* Call stack:
* misc-functions.sh, line 17: Called source '/usr/lib/portage/bin/ebuild.sh'
* ebuild.sh, line 466: Called preprocess_ebuild_env
* phase-functions.sh, line 159: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
* phase-functions.sh, line 140: Called die
* The specific snippet of code:
* "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
*
* If you need support, post the output of 'emerge --info =sys-devel/llvm-3.0-r2',
* the complete build log and the output of 'emerge -pqv =sys-devel/llvm-3.0-r2'.
* The complete build log is located at '/var/lib/entropy/logs/sys-devel:llvm-3.0-r2:20120423-182758.log'.
* The ebuild environment file is located at '/var/tmp/entropy/packages-nonfree/x86/5/sys-devel_llvm-3.0-r2_0.tbz2/portage/sys-devel/llvm-3.0-r2/temp/environment'.
* S: '/var/tmp/entropy/packages-nonfree/x86/5/sys-devel_llvm-3.0-r2_0.tbz2/portage/sys-devel/llvm-3.0-r2/work/llvm-3.0'
/usr/lib/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.7: No such file or directory
* The ebuild phase 'die_hooks' 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.
>> ## Installing package: sys-devel/llvm-3.0-r2
>> ## [Low Level Virtual Machine]
>> ## Updating database: sys-devel/llvm-3.0-r2
>> ## Cleaning previously installed application data.
>> ## Cleaning: sys-devel/llvm-3.0-r2
>> ++ (64/74) >>> net-misc/rsync-3.0.9-r2
>> ## Unpacking: net-misc:rsync-3.0.9-r2~0.tbz2
>> ## Installing package: net-misc/rsync-3.0.9-r2
>> ## [File transfer program to keep remote files into sync]
>> ## Protecting config file: /etc/init.d/rsyncd
>> ## Automerging config file, never modified: /etc/init.d/rsyncd
>> ## Updating database: net-misc/rsync-3.0.9-r2
>> ## Cleaning previously installed application data.
>> ## SPM: post-install phase
/usr/lib/portage/bin/phase-functions.sh: line 140: /usr/bin/python2.7: No such file or directory
* ERROR: net-misc/rsync-3.0.9-r2 failed (pretend phase):
* filter-bash-environment.py failed
*
* Call stack:
* ebuild.sh, line 466: Called preprocess_ebuild_env
* phase-functions.sh, line 159: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
* phase-functions.sh, line 140: Called die
* The specific snippet of code:
* "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
*
* If you need support, post the output of 'emerge --info =net-misc/rsync-3.0.9-r2',
* the complete build log and the output of 'emerge -pqv =net-misc/rsync-3.0.9-r2'.
* The complete build log is located at '/var/lib/entropy/logs/net-misc:rsync-3.0.9-r2:20120423-182806.log'.
* The ebuild environment file is located at '/var/tmp/entropy/packages/x86/5/net-misc_rsync-3.0.9-r2_0.tbz2/portage/net-misc/rsync-3.0.9-r2/temp/environment'.
* S: '/var/tmp/entropy/packages/x86/5/net-misc_rsync-3.0.9-r2_0.tbz2/portage/net-misc/rsync-3.0.9-r2/work/rsync-3.0.9'
/usr/lib/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.7: No such file or directory
* The ebuild phase 'pretend' 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.
/usr/lib/portage/bin/phase-functions.sh: line 140: /usr/bin/python2.7: No such file or directory
* ERROR: net-misc/rsync-3.0.9-r2 failed:
* filter-bash-environment.py failed
*
* Call stack:
* misc-functions.sh, line 17: Called source '/usr/lib/portage/bin/ebuild.sh'
* ebuild.sh, line 466: Called preprocess_ebuild_env
* phase-functions.sh, line 159: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
* phase-functions.sh, line 140: Called die
* The specific snippet of code:
* "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
*
* If you need support, post the output of 'emerge --info =net-misc/rsync-3.0.9-r2',
* the complete build log and the output of 'emerge -pqv =net-misc/rsync-3.0.9-r2'.
* The complete build log is located at '/var/lib/entropy/logs/net-misc:rsync-3.0.9-r2:20120423-182806.log'.
* The ebuild environment file is located at '/var/tmp/entropy/packages/x86/5/net-misc_rsync-3.0.9-r2_0.tbz2/portage/net-misc/rsync-3.0.9-r2/temp/environment'.
* S: '/var/tmp/entropy/packages/x86/5/net-misc_rsync-3.0.9-r2_0.tbz2/portage/net-misc/rsync-3.0.9-r2/work/rsync-3.0.9'
/usr/lib/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.7: No such file or directory
* The ebuild phase 'die_hooks' 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.
>> ## Cleaning: net-misc/rsync-3.0.9-r2
>> ++ (65/74) >>> app-cdr/brasero-3.4.0
>> ## Unpacking: app-cdr:brasero-3.4.0~0.tbz2
>> ## SPM: setup phase
/usr/lib/portage/bin/phase-functions.sh: lin
Several problems have emerged; A lot of letters have been replaced by empty boxes in KDE. In other DEs there are no letters at all - just boxes. Attempting to run equo update I get
- Code: Select all
localhost robin # equo update --force
bash: /usr/bin/equo: /usr/bin/python2: bad interpreter: No such file or directory
localhost robin #
entropy store won't run (same error).
I don't know if this is a bug or a problem in my update but it's quite serious as I'm stuck with no entropy.
Let me know if there's other information you require.
Edit; a few minutes later; The letters/boxes problem is solved using the method from joost here:
http://forum.sabayon.org/viewtopic.php?f=53&t=27063
