Bug 2704 – OmniORB sandbox violation

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Jean-Michel Smith 2002-05-13 12:54:06 UTC]

Attempts to emerge net-misc/omniORB/omniORB-304-r6.ebuild result in the following:
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-omniORB-304-r6-6841.log"

open_wr:   /usr/omniORB
--------------------------------------------------------------------------------

[Comment 1 Matthias Sessler 2002-06-28 07:57:16 UTC]

Created attachment 1851 [details]
Corrected ebuild file

[Comment 2 Matthias Sessler 2002-06-28 07:58:35 UTC]

Created attachment 1852 [details]
updated mkomnistubs.py file

change python version from 2.1 to 2.2

[Comment 3 Ben Lutgens (RETIRED) 2002-07-06 14:12:47 UTC]

why is this assigned to me? I just reported it....

[Comment 4 Seemant Kulleen (RETIRED) 2002-07-06 17:59:09 UTC]

George, I think the omniORB folks actually have a 305 release out now, too.

[Comment 5 George Shapovalov (RETIRED) 2002-07-25 16:44:51 UTC]

Hi guys.

Sorry for taking quite some time to handle this. Back from some major portage
cleanups to bug-squashing.

3.0.5 is available and this is the one I committed. Seems to build and install
fine, no sandbox violations. However while emrge executes pkg_postinst I am
getting the following chain of complaints:

TimeBase
omniidl -bpython -C /usr/lib/python2.1/site-packages/ -I/usr/idl -I/usr/idl/COS
-DNOLONGLONG /usr/idl/COS/TimeBase.idl
omniidl: Could not import back-end `python'
omniidl: Maybe you need to use the -p option?
omniidl: (The error was `No module named python')

and such for every listed package. 
Matthias, I see you submitted mkomnistubs.py. Could you please check what's
happening?

I committed the ebuild, it is masked for now. Could you guys please test?
(and apparently mkomnistubs issue has to be taken care of before I'll unmask it).

Another thing:
in the present form this ebuild will only build on x86, even more strongly -
i586. This is due to hardwired arch specified in ebuild. If anybody feels
adventrous you are wellcome to add autodetection code to the ebuild. I am quite
unlikely to get back to this one in near future.

One more:
anybody knows whereabouts of berlin-base/omniORB-303?
(different category)

George

[Comment 6 George Shapovalov (RETIRED) 2002-07-25 22:32:30 UTC]

Sorry, my fault re: pkg_postinst procedure - mistyped omniORBpy path.
Now it gets installed and setup Ok.

Please test and let me know, so I could unmask the ebuild

George

[Comment 7 Jean-Michel Smith 2002-07-26 09:54:17 UTC]

It looks like the source URI may have some problems.  When trying to test the
masked omniORB ebuild, I got:

           => `/usr/portage/distfiles/omniORB_305.tar.gz'
Connecting to www.ibiblio.org[152.2.210.81]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
09:55:28 ERROR 404: Not Found.


>>> Downloading http://us.dl.sourceforge.net/omniORB/omniORB_305.tar.gz
--09:55:28--  http://us.dl.sourceforge.net/omniORB/omniORB_305.tar.gz
           => `/usr/portage/distfiles/omniORB_305.tar.gz'
Resolving us.dl.sourceforge.net... done.
Connecting to us.dl.sourceforge.net[152.2.210.121]:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://unc.dl.sourceforge.net/omniORB/omniORB_305.tar.gz [following]
--09:55:28--  http://unc.dl.sourceforge.net/omniORB/omniORB_305.tar.gz
           => `/usr/portage/distfiles/omniORB_305.tar.gz'
Resolving unc.dl.sourceforge.net... done.
Connecting to unc.dl.sourceforge.net[152.2.210.121]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
09:55:28 ERROR 404: Not Found.

!!! Couldn't download omniORB_305.tar.gz.  Aborting.
!!! emerge aborting on  /usr/portage/net-misc/omniORB/omniORB-305.ebuild .

[Comment 8 Jean-Michel Smith 2002-07-29 14:05:14 UTC]

I managed to get the ebuild to install (I suspect once the source tarball is
mirrored by gentoo that will no longer be a problem), BUT it looks like some of
the libraries that should be symbolic links are not.  After emerging OmniORB
3.05, ldconfig givs the following warning:

# ldconfig
ldconfig: /usr/lib/libtcpwrapGK.so.2 is not a symbolic link

ldconfig: /usr/lib/libomnithread.so.2 is not a symbolic link

ldconfig: /usr/lib/libomniORB3.so.0 is not a symbolic link

ldconfig: /usr/lib/libomniDynamic3.so.0 is not a symbolic link

ldconfig: /usr/lib/libCOSDynamic3.so.0 is not a symbolic link

ldconfig: /usr/lib/libCOSBOA3.so.0 is not a symbolic link

ldconfig: /usr/lib/libCOS3.so.0 is not a symbolic link

[Comment 9 George Shapovalov (RETIRED) 2002-08-09 17:21:09 UTC]

Ok, fixed ldconfig issue, please test.

Phoen][x: I confirmed that emerge -b issue, this is a portage and not omniORB's
problem. I submitted a bug report (#6266).

ebuild should be ready now for final testing and can be unmasked.

Jean-Michel, Matthias: thatnks for reports and involvment!

George

[Comment 10 George Shapovalov (RETIRED) 2002-09-01 12:58:50 UTC]

Ok, fixed emerge -b issue. Unmasking ebuild now, since old one causes trouble
for many people.

Thanks everybody for submissions and testing!

George