[Zope] Zope won't start

[Tom Cameron]

I am glad to see someone else with a similar problem. I am using FreeBSD4.0
Stable and Zope 2.3.2 and python1.5.2.

I did not use the ports because they are out of date. The zope port is old
and the python port did not have the "new" module installed. So I have
compiled both from source.

I am still getting the PyMethod_Type problem and I would like to use the
latest version of Zope. I am continuing to try other things to see if I can
get it working. I already have zope working on a similar environment on
another machine so I know it can be done. I just need help isolating this
problem.

Tom

=> -----Original Message-----
=> From: Leonard Sitongia [mailto:sitongia@qwest.net]
=> Sent: Monday, 28 May 2001 12:31 PM
=> To: Tom Cameron; Phil Harris; zope@zope.org
=> Subject: Re: [Zope] Zope won't start
=>
=>
=> I found a fix to the "no module new" from searching the web: comment
=> out the Python Modules/Setup configuration of "new newmodule.c".
=>
=> I couldn't get around the PyMethod_Type problem, so I built Python
=> and Zope (2.2.2) from the ports.  Now I have Zope running, but
=> I can't use the manage interface because the zopemaster password
=> doesn't work, even when I reset it with post-install instructions of
=>
=> python zpasswd.py -u <username> -p <passwd> -e CLEARTEXT access
=>
=> Did my attempts at source-install with it's "admin" account password
=> corrupt the acl for the ports-install?  Something wrong with cleartext
=> authentication?  This authentication stuff is a hurdle.  I think
=> I understand
=> that using zpasswd creates and "emergency" account, which can't do
=> everything.  Why do different "distrubutions" have different management
=> passwords?  Is there a concept of a "root" account that has authority to
=> do everything?  Does it have a unique name?  Is this different from the
=> emergency account?  Whew!
=>
=> ==Leonard
=>