Summary: | PyCoCuMa (New package) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Frederik 'Freso' S. Olesen <bugs.gentoo.org> |
Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | python |
Priority: | High | Keywords: | EBUILD |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://srcco.de/pycocuma/ | ||
Whiteboard: | sunrise suggested | ||
Package list: | Runtime testing required: | --- | |
Attachments: |
Non-working ebuild for PyCoCuMa 0.4.5-6
Ebuild for PyCoCuMa 0.4.5-6 |
Description
Frederik 'Freso' S. Olesen
2006-03-09 15:28:09 UTC
Created attachment 81814 [details] Non-working ebuild for PyCoCuMa 0.4.5-6 Where I've gotten so far tonight with this ebuild. Doesn't work yet though. I've copied stuff from dev-python/pmv and net-news/charm (both of which has some outdated stuff which I will probably poke at soonishly) as well as from the Gentoo Developer Handbook and http://dev.gentoo.org/~plasmaroo/devmanual/. nayru ~ # emerge -v pycocuma Calculating dependencies... done! >>> Emerging (1 of 1) app-misc/pycocuma-0.4.5_p6 to / >>> checksums files ;-) .pycocuma-0.4.5_p6.ebuild.swp >>> checksums files ;-) pycocuma-0.4.5_p6.ebuild >>> checksums files ;-) files/digest-pycocuma-0.4.5_p6 >>> checksums src_uri ;-) PyCoCuMa-0.4.5-6.tar.gz >>> Unpacking source... >>> Unpacking PyCoCuMa-0.4.5-6.tar.gz to /var/tmp/portage/pycocuma-0.4.5_p6/work >>> Source unpacked. >>> Compiling source in /var/tmp/portage/pycocuma-0.4.5_p6 ... >>> Source compiled. >>> Test phase [not enabled]: app-misc/pycocuma-0.4.5_p6 >>> Install pycocuma-0.4.5_p6 into /var/tmp/portage/pycocuma-0.4.5_p6/image/ category app-misc python: can't open file 'setup.py': [Errno 2] No such file or directory !!! ERROR: app-misc/pycocuma-0.4.5_p6 failed. Call stack: ebuild.sh, line 1933: Called dyn_install ebuild.sh, line 1067: Called src_install pycocuma-0.4.5_p6.ebuild, line 33: Called distutils_src_install !!! (no error message) !!! If you need support, post the topmost build error, and the call stack if relevant. nayru ~ # Created attachment 81815 [details]
Ebuild for PyCoCuMa 0.4.5-6
This ebuild at least installs the application. It still needs a MY_P/MY_PV instead of the hardcoded version. I might also want to add Tkinter versions to DEPENDS. It also fails when trying to run it:
freso@nayru ~> pycocuma
broker.UnRegister(): failed to unregister provider for 'Connection Type'
broker.UnRegister(): failed to unregister provider for 'Connection String'
Could not set TopLevel window icon
Traceback (most recent call last):
File "/usr/bin/pycocuma", line 17, in ?
pycocumalib.pycocuma.run()
File "/usr/lib64/python2.4/site-packages/pycocumalib/pycocuma.py", line 23, in run
mainctrl = MainController()
File "/usr/lib64/python2.4/site-packages/pycocumalib/MainController.py", line 78, in __init__
self.view = view = MainView(__version__, self.model, tkroot)
File "/usr/lib64/python2.4/site-packages/pycocumalib/MainView.py", line 50, in __init__
self.createWidgets()
File "/usr/lib64/python2.4/site-packages/pycocumalib/MainView.py", line 304, in createWidgets
self._notebook.setnaturalsize()
File "/usr/lib64/python2.4/site-packages/Pmw/Pmw_1_2/lib/PmwNoteBook.py", line 355, in setnaturalsize
self.configure(hull_width = width, hull_height = height)
File "/usr/lib64/python2.4/site-packages/Pmw/Pmw_1_2/lib/PmwBase.py", line 722, in configure
((),) * len(indirectOptions), indirectOptions.values())
File "/usr/lib/python2.4/lib-tk/Tkinter.py", line 1139, in configure
return self._configure('configure', cnf, kw)
File "/usr/lib/python2.4/lib-tk/Tkinter.py", line 1130, in _configure
self.tk.call(_flatten((self._w, cmd)) + self._options(cnf))
_tkinter.TclError: bad screen distance "457.0"
freso@nayru ~>
(this is an automated message based on filtering criteria that matched this bug) 'EBUILD' is in the KEYWORDS which should mean that there is a ebuild attached to this bug. This bug is assigned to maintainer-wanted which means that it is not in the main tree. Heuristics show that no Gentoo developer has commented on your ebuild. Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Because this is a mass message, we are also asking you to be patient with us. We anticipate a large number of requests in a short time. Thanks, On behalf of the Gentoo Sunrise Team, Jeremy. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq Dead upstream homepage, no new versions since 2006. |