Summary: | net-zope/zope-2.9.7 fails to start normally. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marius van Wyk <marius> |
Component: | New packages | Assignee: | net-zope (OBSOLETE) <net-zope+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | anders |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 176478 | ||
Bug Blocks: |
Description
Marius van Wyk
2007-04-12 00:09:25 UTC
During creation of zope instance with zope-config tool, a script in /etc/init.d/ should be created (matching name of instance). Could you please try: /etc/init.d/SCRIPTNAME start # where scriptname is name of created instance? I usually use /etc/init.d/zope-instance start This has the same effect. Just to rule out possible problems in the init script is why I reported the bug with: /var/lib/zope/zope-instance/bin/zopectl (In reply to comment #1) > During creation of zope instance with zope-config tool, a script in > /etc/init.d/ should be created (matching name of instance). > > Could you please try: > /etc/init.d/SCRIPTNAME start # where scriptname is name of created instance? > This problem was identified by Andreas Jung and the 2.9.7 + 2.10.3 releases were retracted as can be seen here: http://www.gossamer-threads.com/lists/zope/dev/207371. Shortly there after new tarballs for the same releases were issued. Notice that the version numbers did not change! Grabbing the new source from zope.org and digesting the ebuild should fix the problem. 2.9.7-r1 and 2.10.3-r1 should be created with the updated md5sums for the newer tarballs and the defective sources should be purged from the gentoo mirrors. If that is possible. Cool, thanks for the link! (Yea, I was also harping about version numbers not changing... *mumble*) (In reply to comment #3) > This problem was identified by Andreas Jung and the 2.9.7 + 2.10.3 releases > were retracted as can be seen here: > http://www.gossamer-threads.com/lists/zope/dev/207371. Shortly there after new > tarballs for the same releases were issued. Notice that the version numbers > did not change! So this means to quickly fix it one can always do: vi /usr/lib/zope-2.9.7/lib/python/App/ApplicationManager.py and change line: def manage_restart(self, URL1): to: def manage_restart(self, URL1, REQUEST=None): This did the trick for me! Remember to re-do this fix if you ever re-emerge unless you get an updated tarball and rebuild the ebuild. FINAlly fixed :) Thank you to all parties for patience and perseverence :) Please give 4h to 24h for mirror://gentoo to fetch proper files. up to then, md5 check will fail. |