collective.buildout

zope2zeoserver using "zeopack" directive discards defaults

Bug #273059 reported by Jens Vagelpohl
2
Affects Status Importance Assigned to Milestone
collective.buildout
Confirmed
Undecided
Unassigned

Bug Description

When using the zope2zeoserver recipe to generate a "zeopack" script the defaults like ZEO server hostname/port/socket path are generated and added into the script. However, when using the "zeopack" directive inside the buildout stanza to point to a different zeopack.py location all those nice defaults are discarded, and even the final invocation inside the zeopack script is a different one.

It makes no sense to treat those two cases differently. In both cases the generated script should look and behave the same.

Jens Vagelpohl (dataflake-deactivatedaccount-deactivatedaccount)
Changed in collective.buildout:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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