/var/tmp/portage/._unmerge_/g-octave/optiminterp-0.3.2/temp/build.log

build.log (text/plain), 4.28 KB, created by Juergen Rose on 2012-01-23 14:48:20 UTC

 [32;01m*[0m Running on_uninstall routines to prepare the package to remove.
No package files given... Grabbing a set.
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/test_optiminterp_mult.m
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/test_optiminterp.m
--- !found   obj /usr/share/octave/packages/optiminterp-0.3.2/packinfo/on_uninstall.m
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/packinfo/dist_admin
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/packinfo/INDEX
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/packinfo/DESCRIPTION
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/packinfo/ChangeLog
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/packinfo/COPYING
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/packinfo/.autoload
--- replaced dir /usr/share/octave/packages/optiminterp-0.3.2/packinfo
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/optiminterpn.m
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/optiminterp4.m
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/optiminterp3.m
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/optiminterp2.m
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/optiminterp1.m
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/example_optiminterp.m
--- replaced obj /usr/share/octave/packages/optiminterp-0.3.2/doc-cache
--- replaced dir /usr/share/octave/packages/optiminterp-0.3.2
--- replaced dir /usr/share/octave/packages
--- replaced dir /usr/share/octave
--- replaced dir /usr/share
--- replaced obj /usr/libexec/octave/packages/optiminterp-0.3.2/x86_64-pc-linux-gnu-api-v48+/optiminterp.oct
--- replaced dir /usr/libexec/octave/packages/optiminterp-0.3.2/x86_64-pc-linux-gnu-api-v48+
--- replaced dir /usr/libexec/octave/packages/optiminterp-0.3.2
--- replaced dir /usr/libexec/octave/packages
--- replaced dir /usr/libexec/octave
--- replaced dir /usr/libexec
--- replaced dir /usr
 [32;01m*[0m Rebuilding the Octave package database.
 [31;01m*[0m ERROR: g-octave/optiminterp-0.3.2 failed (postrm phase):
 [31;01m*[0m   failed to rebuild the package database
 [31;01m*[0m 
 [31;01m*[0m Call stack:
 [31;01m*[0m     ebuild.sh, line   85:  Called pkg_postrm
 [31;01m*[0m   environment, line 2828:  Called g-octave_pkg_postrm
 [31;01m*[0m   environment, line 1936:  Called die
 [31;01m*[0m The specific snippet of code:
 [31;01m*[0m       ${OCT_BIN} -H --silent --eval 'pkg rebuild' &>/dev/null || die 'failed to rebuild the package database'
 [31;01m*[0m 
 [31;01m*[0m If you need support, post the output of 'emerge --info =g-octave/optiminterp-0.3.2',
 [31;01m*[0m the complete build log and the output of 'emerge -pqv =g-octave/optiminterp-0.3.2'.
 [31;01m*[0m This ebuild used the following eclasses from overlays:
 [31;01m*[0m   /var/lib/g-octave/eclass/g-octave.eclass
 [31;01m*[0m This ebuild is from a repository named 'g-octave'
 [31;01m*[0m The complete build log is located at '/var/tmp/portage/._unmerge_/g-octave/optiminterp-0.3.2/temp/build.log'.
 [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/._unmerge_/g-octave/optiminterp-0.3.2/temp/environment'.
 [31;01m*[0m S: '/var/tmp/portage/._unmerge_/g-octave/optiminterp-0.3.2/work/optiminterp-0.3.2'
!!! FAILED postrm: 1
[31;01m * [39;49;00mThe 'postrm' phase of the 'g-octave/optiminterp-0.3.2' package has
[31;01m * [39;49;00mfailed with exit value 1.
[31;01m * [39;49;00m
[31;01m * [39;49;00mThe problem occurred while executing the ebuild file named
[31;01m * [39;49;00m'optiminterp-0.3.2.ebuild' located in the
[31;01m * [39;49;00m'/var/db/pkg/g-octave/optiminterp-0.3.2' directory. If necessary,
[31;01m * [39;49;00mmanually remove the environment.bz2 file and/or the ebuild file located
[31;01m * [39;49;00min that directory.
[31;01m * [39;49;00m
[31;01m * [39;49;00mRemoval of the environment.bz2 file is preferred since it may allow the
[31;01m * [39;49;00mremoval phases to execute successfully. The ebuild will be sourced and
[31;01m * [39;49;00mthe eclasses from the current portage tree will be used when necessary.
[31;01m * [39;49;00mRemoval of the ebuild file will cause the pkg_prerm() and pkg_postrm()
[31;01m * [39;49;00mremoval phases to be skipped entirely.