Bug 475154 – app-editors/nano-2.3.2 - /usr/bin/sandbox "/usr/lib64/portage/bin/ebuild.sh" unpack: /usr/lib64/portage/pym/portage/_selinux.py", line 80, in setexec if selinux.setexeccon(ctx) < 0: OSError: [Errno 22] Invalid argument

• Product: Portage Development
• Status: RESOLVED NEEDINFO

[Description Kirill Berezin 2013-06-28 22:22:30 UTC]

gentoo-test wgetpaste-2.22 # emerge nano

 * IMPORTANT: 2 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.

Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) app-editors/nano-2.3.2
 * nano-2.3.2.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                                      [ ok ]
[Errno 22] Invalid argument:
   /usr/bin/sandbox "/usr/lib64/portage/bin/ebuild.sh" unpack
Traceback (most recent call last):
  File "/usr/lib64/portage/pym/portage/process.py", line 271, in spawn
    env, gid, groups, uid, umask, pre_exec, close_fds)
  File "/usr/lib64/portage/pym/portage/process.py", line 418, in _exec
    pre_exec()
  File "/usr/lib64/portage/pym/portage/_selinux.py", line 119, in _pre_exec
    setexec(self._con)
  File "/usr/lib64/portage/pym/portage/_selinux.py", line 80, in setexec
    if selinux.setexeccon(ctx) < 0:
OSError: [Errno 22] Invalid argument
 * 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.

>>> Failed to emerge app-editors/nano-2.3.2, Log file:

>>>  '/var/tmp/portage/app-editors/nano-2.3.2/temp/build.log'

 * Messages for package app-editors/nano-2.3.2:

 * 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.


http://bpaste.net/show/110602/

[Comment 1 Jeroen Roovers (RETIRED) 2013-07-01 14:54:35 UTC]

Please post your `emerge --info' output in a comment.