rustyscience n00b
Joined: 22 Oct 2013 Posts: 5
|
Posted: Tue Oct 22, 2013 12:13 pm Post subject: sci-mathematics/gap-4.6.5 hangs at doins |
|
|
Hi all Gentoo users!
I've added sage-on-gentoo overlay, and trying to install sage. But one of the dependencies does not install
>>> Install gap-4.6.5 into /var/tmp/portage/sci-mathematics/gap-4.6.5/image/ category sci-mathematics
It hangs, I hit ^C, and it claims
Code: | QA Notice: file does not exist:
doins: pkg/factint/tables/brent/brfac15 does not exist
doins: pkg/factint/tables/brent/brfac5011 does not exist |
Full error log:
Code: |
Exiting on signal 2
sandbox:stop signal already caught and busy still cleaning up!
sandbox:stop caught signal 2 in pid 11688
Traceback (most recent call last):
File "/usr/lib/portage/bin/install.py", line 11, in <module>
from portage.util._argparse import ArgumentParser
File "/usr/lib/portage/pym/portage/__init__.py", line 21, in <module>
import platform
File "/usr/lib/python2.7/platform.py", line 245, in <module>
_lsb_release_version = re.compile(r'(.+)'
File "/usr/lib/python2.7/re.py", line 190, in compile
return _compile(pattern, flags)
File "/usr/lib/python2.7/re.py", line 240, in _compile
p = sre_compile.compile(pattern, flags)
File "/usr/lib/python2.7/sre_compile.py", line 501, in compile
p = sre_parse.parse(p, flags)
File "/usr/lib/python2.7/sre_parse.py", line 686, in parse
p = _parse_sub(source, pattern, 0)
File "/usr/lib/python2.7/sre_parse.py", line 309, in _parse_sub
itemsappend(_parse(source, state))
File "/usr/lib/python2.7/sre_parse.py", line 646, in _parse
p = _parse_sub(source, state)
KeyboardInterrupt
!!! doins: pkg/factint/tables/brent/brfac15 does not exist
^Csandbox:stop signal already caught and busy still cleaning up!
Traceback (most recent call last):
File "/usr/lib/portage/bin/install.py", line 11, in <module>
from portage.util._argparse import ArgumentParser
File "/usr/lib/portage/pym/portage/__init__.py", line 21, in <module>
import platform
File "/usr/lib/python2.7/platform.py", line 244, in <module>
_release_filename = re.compile(r'(\w+)[-_](release|version)')
File "/usr/lib/python2.7/re.py", line 190, in compile
return _compile(pattern, flags)
File "/usr/lib/python2.7/re.py", line 240, in _compile
p = sre_compile.compile(pattern, flags)
File "/usr/lib/python2.7/sre_compile.py", line 505, in compile
code = _code(p, flags)
File "/usr/lib/python2.7/sre_compile.py", line 490, in _code
_compile(code, p.data, flags)
File "/usr/lib/python2.7/sre_compile.py", line 102, in _compile
_compile(code, av[1], flags)
File "/usr/lib/python2.7/sre_compile.py", line 41, in _compile
for op, av in pattern:
File "/usr/lib/python2.7/sre_parse.py", line 131, in __getitem__
def __getitem__(self, index):
KeyboardInterrupt
!!! doins: pkg/factint/tables/brent/brfac5011 does not exist
^Csandbox:stop signal already caught and busy still cleaning up!
/var/lib/layman/sage-on-gentoo/sci-mathematics/gap/gap-4.6.5.ebuild: src_install aborted; exiting.
^Csandbox:stop signal already caught and busy still cleaning up!
Sandboxed process killed by signal: Interrupt
* QA Notice: file does not exist:
*
* doins: pkg/factint/tables/brent/brfac15 does not exist
* doins: pkg/factint/tables/brent/brfac5011 does not exist
^Csandbox:stop caught signal 2 in pid 31502
Sandboxed process killed by signal: Interrupt
* 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.
|
|
|