Your message dated Mon, 18 Dec 2006 17:43:26 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402347: zope-common: dzhandle zopectl stop fails on zope3
instance
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: zope-common
Version: 0.5.27
Severity: normal
# dzhandle -z 3 zopectl upj stop
Traceback (most recent call last):
File "/var/lib/zope3/instance/upj/bin/zopectl", line 43, in ?
run()
File "/var/lib/zope3/instance/upj/bin/zopectl", line 37, in run
import zope.app.server.controller
ImportError: No module named controller
The instance was created some time ago, and it may be a plone site. I
don't know if the problem is something specific to this one
installation, to zope 3, or something else.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages zope-common depends on:
ii adduser 3.100 Add and remove users and groups
ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy
ii python2.4 2.4.4-1 An interactive high-level object-o
zope-common recommends no packages.
-- debconf information:
zope-common/remove-instance-without-data: abort
zope-common/admin-automatic-password:
* shared/zope/restart: end
zope-common/instance-http-port:
zope-common/admin-user: admin
zope-common/keep-data-on-purge: true
--- End Message ---
--- Begin Message ---
Hi Ross,
* 2006-12-09 18:30, Ross Boylan wrote:
> Package: zope-common
> Version: 0.5.27
> Severity: normal
>
> # dzhandle -z 3 zopectl upj stop
> Traceback (most recent call last):
> File "/var/lib/zope3/instance/upj/bin/zopectl", line 43, in ?
> run()
> File "/var/lib/zope3/instance/upj/bin/zopectl", line 37, in run
> import zope.app.server.controller
> ImportError: No module named controller
This is not a bug in dzhandle: the instance was created with zope 3.2 and now
it is incompatible with zope3. This is not dzhandle's fault, and every call to
zopectl will raise ImportError exception as manual editing of instance's
zopectl is required.
I'm closing the bug report because there is nothing wrong in dzhandle
behaviour: this is the "normal" breakage after a major zope3 upstream release.
All in all, it is a development framework which is still in development, and we
do not have zope3 in a stable release yet.
Thanks,
--
Fabio Tranchitella http://www.kobold.it
Free Software Developer and Consultant http://www.tranchitella.it
_____________________________________________________________________
1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564
signature.asc
Description: Digital signature
--- End Message ---
