Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 44121 - dev-python/pykde-3.7.4-r2 sandbox violation
Summary: dev-python/pykde-3.7.4-r2 sandbox violation
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High major
Assignee: Python Gentoo Team
URL:
Whiteboard:
Keywords:
: 44176 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-03-09 04:21 UTC by Hans-Christian Armingeon
Modified: 2004-05-25 05:16 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
pykde-3.7.4-r2.ebuild (pykde-3.7.4-r2.ebuild,2.17 KB, text/plain)
2004-04-15 13:11 UTC, Rob Cakebread (RETIRED)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hans-Christian Armingeon 2004-03-09 04:21:32 UTC
# emerge -u dev-python/pykde
Calculating dependencies ...done!
>>> emerge (1 of 1) dev-python/pykde-3.7.4-r2 to /
>>> md5 src_uri ;-) PyKDE-3.7-4.tar.gz
>>> Unpacking source...
>>> Unpacking PyKDE-3.7-4.tar.gz to /var/tmp/portage/pykde-3.7.4-r2/work
>>> Source unpacked.
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-dev-python_-_pykde-3.7.4-r2-2258.log"

open_wr:   /usr/qt/3/etc/settings/.qtrc.lock
--------------------------------------------------------------------------------


Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Uranus 2004-03-22 12:34:53 UTC
same here
Comment 2 Rob Cakebread (RETIRED) gentoo-dev 2004-04-15 13:11:45 UTC
Created attachment 29361 [details]
pykde-3.7.4-r2.ebuild

Simply uses this as a suggested fix:

31a32,34
>	mkdir -p ${QTDIR}/etc/settings
>	addwrite "${QTDIR}/etc/settings"
>

I can't reproduce the error so can Hans-Christian and Uranus try this ebuild
and
let us know if it works? I'm not sure its an acceptable solution, but its
done in a few other ebuilds.
Comment 3 Jan van Dijk 2004-04-30 16:28:49 UTC
Rob, your fix works, thanks. 
Comment 4 Stuart Marks 2004-05-05 13:25:14 UTC
Ok, plain old "#emerge pykde" does not work for me either because of this sandbox violation.  I tried "#FEATURES=-sandbox emerge pykde" but it exited with the following errors (lots of them):

/usr/kde/3.2/include/kprocctrl.h: In constructor `
   sipKProcessController::sipKProcessController()':
/usr/kde/3.2/include/kprocctrl.h:139: error: `
   KProcessController::KProcessController()' is private
sipkdecoreKProcess.cpp:2001: error: within this context
/usr/kde/3.2/include/kprocctrl.h:140: error: `
   KProcessController::~KProcessController()' is private
sipkdecoreKProcess.cpp:2001: error: within this context
/usr/kde/3.2/include/kprocctrl.h: In destructor `virtual
   sipKProcessController::~sipKProcessController()':
/usr/kde/3.2/include/kprocctrl.h:140: error: `
   KProcessController::~KProcessController()' is private
sipkdecoreKProcess.cpp:2006: error: within this context
/usr/kde/3.2/include/kprocctrl.h: In function `PyObject*
   sipDo_KProcessController_setupHandlers(PyObject*, PyObject*)':
/usr/kde/3.2/include/kprocctrl.h:131: error: `static void
   KProcessController::setupHandlers()' is private
sipkdecoreKProcessController.cpp:339: error: within this context
/usr/kde/3.2/include/kprocctrl.h: In function `PyObject*
   sipDo_KProcessController_resetHandlers(PyObject*, PyObject*)':
/usr/kde/3.2/include/kprocctrl.h:132: error: `static void
   KProcessController::resetHandlers()' is private
sipkdecoreKProcessController.cpp:362: error: within this context
sipkdecoreKProcessController.cpp: In function `PyObject*
   sipDo_KProcessController_slotDoHousekeeping(PyObject*, PyObject*)':
sipkdecoreKProcessController.cpp:467: error: no matching function for call to `
   KProcessController::slotDoHousekeeping(int&)'
/usr/kde/3.2/include/kprocctrl.h:120: error: candidates are: void
   KProcessController::slotDoHousekeeping()
/usr/kde/3.2/include/kprocctrl.h: In function `void
   sipDealloc_KProcessController(sipThisType*)':
/usr/kde/3.2/include/kprocctrl.h:140: error: `virtual
   KProcessController::~KProcessController()' is private
sipkdecoreKProcessController.cpp:511: error: within this context
/usr/kde/3.2/include/kprocctrl.h: In function `PyObject*
   sipNew_KProcessController(PyObject*, PyObject*)':
/usr/kde/3.2/include/kprocctrl.h:140: error: `virtual
   KProcessController::~KProcessController()' is private
sipkdecoreKProcessController.cpp:564: error: within this context
sipkdecoreKApplication.cpp: In function `PyObject*
   sipDo_KApplication_xioErrhandler(PyObject*, PyObject*)':
sipkdecoreKApplication.cpp:2620: error: no matching function for call to `
   KApplication::xioErrhandler()'
/usr/kde/3.2/include/kapplication.h:1140: error: candidates are: int
   KApplication::xioErrhandler(Display*)
make[1]: *** [kdecorehuge0.o] Error 1
make[1]: Leaving directory `/var/tmp/portage/pykde-3.7.4-r2/work/PyKDE-3.7-4/kdecore'
make: *** [sub-kdecore] Error 2

!!! ERROR: dev-python/pykde-3.7.4-r2 failed.
!!! Function src_compile, Line 70, Exitcode 2
!!! (no error message)
Comment 5 Michael Holcomb 2004-05-07 22:31:58 UTC
I had this issue as well, and used rob's fix and was able to work around it.
Comment 6 Carsten Lohrke (RETIRED) gentoo-dev 2004-05-25 04:42:51 UTC
*** Bug 44176 has been marked as a duplicate of this bug. ***
Comment 7 Carsten Lohrke (RETIRED) gentoo-dev 2004-05-25 05:16:01 UTC
fixed this, a new, kde 3.2 compatible, pykde version will be out in a week together with kde 3.2.3