Bug 3162 – Sandbox Violation: screen-3.9.11-r2

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Troy Dack 2002-05-29 07:04:46 UTC]

Sanbox violation when building screen:

>>> Install screen-3.9.11-r2 into /var/tmp/portage/screen-3.9.11-r2/image/
category app-misc
info:
strip:
/var/tmp/portage/screen-3.9.11-r2/image/usr/bin/screen
>>> Completed installing into /var/tmp/portage/screen-3.9.11-r2/image/

--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-screen-3.9.11-r2-5966.log"

chmod:     /dev/pty/s0
--------------------------------------------------------------------------------
!!! emerge aborting on  /usr/portage/app-misc/screen/screen-3.9.11-r2.ebuild .

xabbu build-info # cat /tmp/sandbox-screen-3.9.11-r2-5966.log
chmod:     /dev/pty/s0


xabbu build-info # pwd
/var/tmp/portage/screen-3.9.11-r2/build-info

xabbu build-info # cat USE
apm berkdb crypt cups gdbm gif gpm java jpeg libwww mmx ncurses pam pdflib png
python readline slang spell ssl tcpd truetype xml2 mysql perl tiff maildir imap
fbcon snmp ldap samba zlib

xabbu build-info # cat C[FHX]*
-march=i586 -O3 -pipe
i586-pc-linux-gnu
-march=i586 -O3 -pipe

[Comment 1 Michael M Nazaroff (RETIRED) 2002-06-03 16:18:08 UTC]

What version of portage do you have?, If you don't mind me asking.

Naz

[Comment 2 Troy Dack 2002-06-03 23:45:45 UTC]

xabbu root # emerge -V
Portage 1.9.13

Troy.

[Comment 3 Troy Dack 2002-06-04 00:06:52 UTC]

OK,
  A bit more info:

* I was running emerge in an ssh session
* the "computer" that emerge was being run on is actually a VMWare VM
* I got similar errors emerging vim as well

By logging on at the console of the VM and issueing the emerge command
everything worked as advertised and both screen and vim built and merged happily.

I'll leave it up to you guys if you want to close the bug.  I'm happy I got
screen and vim emerge'd :), but you might want to investigate further -- let me
know how I can help.

Troy.

[Comment 4 Michael M Nazaroff (RETIRED) 2002-06-09 04:07:21 UTC]

R3 should take care of this issue in the screen ebuild.. it's kinda obscure
option on gentoo.. so please test

[Comment 5 Troy Dack 2002-06-11 08:41:19 UTC]

Nope :)

-r3 doesn't like being emerge'd over an SSH session.

Works fine from the console though.

(Use flags as per previous comment).

>>> Install screen-3.9.11-r3 into /var/tmp/portage/screen-3.9.11-r3/image/
category app-misc
info:
strip:
/var/tmp/portage/screen-3.9.11-r3/image/usr/bin/screen
>>> Completed installing into /var/tmp/portage/screen-3.9.11-r3/image/

--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-screen-3.9.11-r3-4254.log"

chmod:     /dev/pty/s0
--------------------------------------------------------------------------------
!!! emerge aborting on  /usr/portage/app-misc/screen/screen-3.9.11-r3.ebuild .

[Comment 6 Michael M Nazaroff (RETIRED) 2002-06-17 13:02:37 UTC]

OK added another small fix.. let me know..  I'm still not getting this problem
locally and and tried it logged in via ssh.  So Please test and take look at the
ebuild and see what I'm doing and maybe try and experiment :o)

Naz

[Comment 7 Aniruddha Shankar 2002-06-18 08:19:31 UTC]

 app-misc/screen-3.9.11-r3 Installed fine on a machine update with teh portage 
tree at around 12:PM UTC on 06-18-02

[Comment 8 Michael M Nazaroff (RETIRED) 2002-07-06 13:29:57 UTC]

I think this bug should be fixed with the addpredict line added into the ebuild.