zope3 mkzopeinstance does not keep user id

Bug #24173 reported by Tim Penhey
6
Affects Status Importance Assigned to Milestone
zope3 (Ubuntu)
Won't Fix
Medium
Matthias Klose

Bug Description

Running
  /usr/lib/zope3/bin/mkzopeinstance -u tim:password -d zope-instance
in home directory should create a directory called zope-instance owned by logged
in user.

However creation script tries to change ownership to user "zope", so execution
fails.

Revision history for this message
Alek Kowalczyk (thealx) wrote :

I confirm that. This bug prevents easy creating own zope3 instance in my homedir and developing own zope applications.

Changed in zope3:
status: Unconfirmed → Confirmed
Revision history for this message
Jonathan Knowles (jsk) wrote :

Just wondering, is there was any progress on fixing this bug? :)
It's still reproducible in Feisty.

Revision history for this message
Tim Penhey (thumper) wrote :

It seems that mkzopeinstance now has the following command line option:

  --service-user=USER:GROUP
                        system user to be used to run the instance (default is zope:zope)

I'm not sure if this existed when I first reported the bug.

Revision history for this message
Beowulf (s-highlander) wrote :

I confirm that this bug exists in Gutsy

Revision history for this message
Christian González (droetker) wrote :

I can confirm this bug in hardy as well.
Zope3 seems to be broken.

Revision history for this message
Matthias Klose (doko) wrote :

the monolithic zope3 packages was removed in karmic.

Changed in zope3 (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.