Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
View Bug Activity | Format For Printing | XML | Clone This Bug
When I "zprod-manager add" and select enable coreblog2-0.90b, and then restart the zope/plone instance ("/etc/init.d/zope-plone restart" on my system), the restart appears to work, but a "ps -A" straight afterwards tells me that the daemon has already died. It leaves on log entries in /var/log/zope. When I deselect coreblog2-0.90b, the zope-plone starts up properly and I can browse my plone installation. I am using zope-2.7.8 and plone-2.0.5-r2. I have dev-lang/python-2.3.5-r2 and dev-lang/python-2.4.2 installed. It may or may not be relevant that archetypes-1.2.5_rc5 emerged with the following error messages: * >>> Installing archetypes-1.2.5_rc5 into the "zope-plone" zinstance ... cp: cannot stat `//usr/share/zproduct/archetypes-1.2.5_rc5/ArchExample': No such file or directory cp: cannot stat `//usr/share/zproduct/archetypes-1.2.5_rc5/ArchGenXML': No such file or directory chown: cannot access `/var/lib/zope//zope-plone/Products/ArchExample': No such file or directory chmod: cannot access `/var/lib/zope//zope-plone/Products/ArchExample': No such file or directory chown: cannot access `/var/lib/zope//zope-plone/Products/ArchGenXML': No such file or directory chmod: cannot access `/var/lib/zope//zope-plone/Products/ArchGenXML': No such file or directory >>> Regenerating /etc/ld.so.cache... >>> net-zope/archetypes-1.2.5_rc5 merged. I shall now try upgrading to a more recent version of coreblog2 and post a comment here if I don't have the same problem as with this version.
Just realised I can't upgrade, but a downgrade to coreblog2-0.81b did not fix the problem.
Looks like You have to upgrade to plone-2.1 (at least this should work correctly with coreblog). This is defiency in zprod-manager that it doesn not check dependencies during installation of packages (they're only check on emerge time). coreblog2 is for plone-2.1+ Of course there were missing deps for plone-2.1 in coreblog2 ebuilds (fixed this). Another thing is that you should look for errors in zope log (/var/log/zope/xxx/*.log). Feel free to provide more info about the problem if upgrading wont help.