Comment

Above in this comment thread: Hotfix 2005-10-09 Alert »

Comment

Zope2.7.0(+?) issues

Posted by: d2m at 2005-10-10

there are some minor issues with at least Zope2.7.0 (please add your findings with higher versions of zope2.7.x too):

  - ensure you create a copy of the  
    lib/python/docutils|reStructuredText|Products/ZRest folders 
    before you install the update
  - docutils now expects 2 config directives that are not available 
    through zope.conf (initial-header-level and default-language-code)
    - you eventually need to edit lib/python/reStructuredText/__init__.py changing:
      - initial_header_level = getConfiguration().rest_header_level or default_level
      - default_language_code = getConfiguration().rest_language_code or default_language
    **to** 
      - initial_header_level = default_level
      - default_language_code = default_lang
  - some file-permissions need to be changed (lib/python/Products/ZRest/zrest.gif)
  - owner and users settings of the 3 packages might be adjusted 
    (depending on your permissions)

I found no problems with hotfixing Zope2.8.1

Comment

Hotfix kills zope 2.7.5, fails to start up

Posted by: jschinnerer at 2005-10-12

I applied this hotfix to my zope 2.7.5 and it was then DOA at attempted restart. Boot-time script message indicates that it starts, but once booted there is no zope process actually running. I would guess that the startup failure is due to some/all of the issues mentioned above - expected but missing config items, perms issues, etc.

So if applying to 2.7.5 expect trouble. I don't know what will fix it in place; I am ditching the hotfix and putting back the previous file versions as I don't have time to play with it.

John S.

Comment

Breaks 2.7.5 - Info on backing out for Debian

Posted by: jschinnerer at 2005-10-13

Applying this hotfix to my zope 2.7.5 install (Debian sarge, using zope2.7 package) resulted in a broken install that would not start up completely.

Here's what I found while backing out the hotfix:

The hotfix-installed files are set to an owner, group and perms that do not work with an existing install (zope fails to start up completely/correctly). I don't know if there are other problems also, but that was the relevant issue for me. To back out, be aware that the owner, group and perms for the Products folder is altered to the same settings!

Simplest way to back out in Debain seemed to be a reinstall of the zope2.7 debian package to get the pre-hotfix files back. Trying the package install, I got some explicit errors on the hotfix-installed files that pointed me to the owner/group/perms problems with those.

Then the debian package appeared to install, but zope still failed to actually start.

Final problem was the owner/group/perms on the Products folder itself, changed to the same non-functional settings, blocking correct/complete reinstall of the original files (unfortunately the package install didn't raise any errors on that - I noticed it while angrily poking about looking for clues...).

Once I fixed the messed-up owner/group/perms on the Products folder and did the package install again, all was well.

John S.

Comment

fix for Debian in progress

Posted by: mennucc at 2005-10-17

I have started working on a fix for Debian; more info and links are in http://lists.alioth.debian.org/pipermail/pkg-zope-developers/2005-October/001081.html

Comment

change permissions

Posted by: bagt at 2005-11-20

Zope version 2.7.2

in the zope/lib/python directory

$ tar -zxvf Hotfix_2005-10-09.tar.gz

$ chmod -R 644 docutils reStructuredText Products/ZReST

$ chmod -R +X docutils reStructuredText Products/ZReST

restart Zope