I was having an awful time getting a sucessful login into the zope management console after installing Zope and Plone. It took me a while to work around it but this is what I did. Basically the "inituser" file from the gentoo ebuild ends up in $(ZOPE_HOME) and needs to end up in $(INSTANCE_HOME) prior to executing zope for the first time. This would be a nice comment to check for the presense of inituser in $(INSTANCE_HOME) at the end of the ebuild. I agree with Jean Jordaan that zope-config is too cryptic for novice use http://bugs.gentoo.org/show_bug.cgi?id=33227. I was confused because I saw the ebuild create an inituser file in the /var/tmp/portage directory so I didn't think zope-config should be run. Once you screw up, I couldn't figure out how to recover a password on an existing zope DB and unmerge doesn't touch the databases as you would expect, so blow it away is what I did. The section on "zope initial manager" was essential for me get going http://zope.org/Documentation/Books/ZopeBook/2_6Edition/InstallingZope.stx/Security.stx WARNING - This deletes your ZOPE Database!!!! Only okay for fresh installs!!! #! RECREATE ZOPE DB with new Initial manager/admin account # /etc/init.d/zope-2_6_4 stop # cd /var/lib/zope/zope-2_6_4/var # rm * # cd /usr/share/zope/zope-2.6.4-r1 # python zpasswd.py inituser Username: admin Password: Verify password: Please choose a format from: SHA - SHA-1 hashed password CRYPT - UNIX-style crypt password CLEARTEXT - no protection. Encoding: SHA Domain restrictions: #! HERE IS THE IMPORTANT PART # cp inituser /var/lib/zope/zope-2_6_4 # /etc/init.d/zope-2_6_4 start #! DONE, log into zope at http://localhost:8080 Here is my confuration... root # cat /etc/conf.d/zope-2_6_4 #-- startup options ZOPE_OPTS="-u zope" INSTANCE_HOME=//var/lib/zope//zope-2_6_4 SOFTWARE_HOME=//usr/share/zope//zope-2.6.4-r1//lib/python ZOPE_HOME=//usr/share/zope//zope-2.6.4-r1/ On my system I'm using the latest stuff from Zope/Plone Using ebuild: net-zope/zope-2.6.4-r1 root # cat /etc/portage/package.keywords # # Subversion stuff # dev-util/subversion ~x86 net-misc/neon ~x86 # # Using mod_perl for smokeping, mod_perl for apache2 is new # dev-perl/mod_perl ~x86 # # Plone 2 is just out! # net-zope/plone ~x86 net-zope/groupuserfolder ~x86 net-zope/epoz ~x86 net-zope/ploneerrorreporting ~x86 net-zope/cmfquickinstallertool ~x86 net-zope/plonetranslations ~x86 net-zope/placelesstranslationservice-fork ~x86 net-zope/formulator ~x86 net-zope/cmf ~x86 net-zope/cmfformcontroller ~x86 net-zope/externaleditor ~x86 net-zope/btreefolder2 ~x86 net-zope/archetypes ~x86 net-zope/portaltransforms ~x86 app-text/xlhtml ~x86 app-text/pdftohtml ~x86 net-zope/cmfactionicons ~x86
you might want to try zope-config --zpasswd :) it's much easier does zope-config solve your problem?
I remember reading http://mail.zope.org/pipermail/zope/2003-September/140591.html and tried the zope-config --zpasswd a few times, didn't work. The hard way did. Guess it goes back to the zope-config documentation issue (zope.org) and documenting the differences between source install of zope and the ebuild install of zope (gentoo.org). http://mail.zope.org/pipermail/zope/2003-September/140597.html. Both issues are confusing. My intent here is to capture an example user problem and getting that experience into future ebuilds which try to get the install more bombproof...
