[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: apt-get install zope fails



Hi Stephen,

I've followed your suggestion, and got reportbug - it is really useful.
Meanwhile, I've been struggling with my zope install and managed to fix a few gotchas (I'll send them as adittional info to the package maintainer). At this point, I have default instance data in place, but zope does not start properly yet. So I used export Z_DEBUG_MODE=1 to get some adittional info, and got the messages below:

debian-hp:/usr/lib/zope/lib/python# zopectl start Starting Zope instance default...
   ------
   2004-01-16T10:07:18 PANIC(300) z2 Startup exception
   Traceback (innermost last):
     File /usr/lib/zope/z2.py, line 593, in ?
     File /usr/lib/zope/lib/python/Zope/__init__.py, line 45, in startup
     File /usr/lib/zope/lib/python/Zope/App/startup.py, line 16, in ?
     File /usr/lib/zope/lib/python/AccessControl/__init__.py, line 16, in ?
     File /usr/lib/zope/lib/python/AccessControl/DTML.py, line 18, in ?
     File /usr/lib/zope/lib/python/DocumentTemplate/__init__.py, line
   21, in ?
   ImportError: /usr/lib/zope/lib/python/ExtensionClass.so: undefined
   symbol: PyType_IsSubtype
    Waiting instances in late:default: timeout: 30
   debian-hp:/usr/lib/zope/lib/python#


Now I am really puzzled - it seems that there's something broken in zope code itself. What do you think about it?

Thanks a lot,
Joao


Stephen wrote:

On Wed, Jan 14, 2004 at 09:44:20AM -0200 or thereabouts, Roscoe Joao wrote:
Hi, Stephen,

Thanks for your help.

I gave it a try:

  ...
  ...
  debian-hp:/usr/bin# zopectl -a default
  Setting up initial user for default...sh: /usr/lib/zope/zpasswd.py:
  /usr/bin/env: bad interpreter: Permission denied
   failed: system(lib/zope/instance/default/access...) exited with
  status(32256)
  default: access: system(lib/zope/instance/default/access...) exited
  with status(32256)
  ...
  ...
  debian-hp:/usr/bin# ls -l /usr/bin/pyth*
  lrwxrwxrwx    1 root     root           18 Jan 14 09:28
  /usr/bin/python -> /usr/bin/python2.2
  -rwxr-xr-x    1 root     root       637472 Apr 20  2002
  /usr/bin/python2.1
  -rwxr-xr-x    1 root     root       976508 Nov 18 00:59
  /usr/bin/python2.2
  -rwxr-xr-x    1 root     root      1118972 Jan  5 01:57
  /usr/bin/python2.3
  ...
  ...

Duh! Wrong python version? So I tried removing the link and recreating it pointing to python2.1 and to python2.3, but got exactly the same error that way too. Sigh! Any clue?

Not really, I don't understand on a vanilla Woody, why you have two
Python versions. Sorry -- why not purge all your zope/python stuff and
start over? When I was having my problems with the upgrade from Stable
to Testing, I used aptitude to 'aptitude purge zope', then did a find
for zope leftovers, removed them manually and then installed everything
again. After doing the manual creation of the default instance again, it
ran for "moi".

I wish you luck. One thing that was suggested to me recently by a Debian
maintainer, is the use of the Debian package 'reportbug'. I suggest that
you download and install it. It's great for reporting a bug with a
package. All one needs to do is issue the command 'reportbug', follow
the prompts to file the information. The app will forward via e-mail the
relevant information.




Reply to: