#25 — Broken zopeskel/templates/plone_hosting/base.cfg_tmpl

by Jean Jordaan — last modified Aug 24, 2011 03:18 PM

State	Postponed
Version:	—
Area	General
Issue type	Bug
Severity	Low
Submitted by	Jean Jordaan
Submitted on	Jan 28, 2010
Responsible	—
Target release:	—

Return to tracker

Found in version 2.15 but this is absent here and thus I cannot log an issue against it.

This template:
./lib/python2.4/site-packages/ZopeSkel-2.15-py2.4.egg/zopeskel/templates/plone_hosting/base.cfg_tmpl

contains this line:

recipe = plone.recipe.zope2instance >=2.0

Which triggers this issue:

http://plone.org/[…]/repair-a-plone-3.1-buildout

Steps to reproduce:: Run './bin/zopeskel plone_hosting' and try to run the generated buildout.

Added by Cris Ewing on Jan 28, 2010 07:25 PM

Issue state: Unconfirmed → Confirmed

Severity: Medium → Low

This is absolutely the case. I'll commit a fix for it, which will be in 2.16 when it comes out. Unfortunately this will continue to make this template less and less compatible with versions of Plone >= 3.2, as the fix for the 3.1 buildout problem is not compatible with later versions of Plone.

As a result, I'm also going to add some information to the descriptions of this template that indicate it is unsuitable for recent plone versions.

Anyone want to work on an update to the template to improve that situation?

Added by Jean Jordaan on Jan 29, 2010 03:13 AM

First prize would be one template that works for all versions, but I think that a splitting off a plone_pre3_hosting template for older Plone versions would be fine also, together with the necessary motivation in the docs.

Added by Cris Ewing on Mar 04, 2010 02:39 AM

Issue state: Confirmed → Resolved

Responsible manager: (UNASSIGNED) → cewing

resolved in r:112264 (http://dev.plone.org/collective/changeset/112264/ZopeSkel)

this issue isn't really closed, as the template remains fundamentally incompatible with recent versions of plone. Anyone who wants to take it further by truly repairing the template to work with recent plone versions is welcome to it.

Added by Jean Jordaan on Mar 04, 2010 04:14 AM

Issue state: Resolved → Confirmed

Added by Jean Jordaan on Mar 04, 2010 04:19 AM

Sorry, wanted to change state from Resolved to Rejected, but seems I can't.

I can't see that marking it as Resolved is helpful. If someone finds this issue, it will be because they've encountered the same problem. If they see it's now Resolved, they would expect to find a fix in svn or a newer release. If they see it's Rejected, they will read further to see why, and perhaps truly repair the template.

Added by Cris Ewing on Mar 04, 2010 04:24 AM

Issue state: Confirmed → Postponed

Responsible manager: cewing → (UNASSIGNED)

I agree with Jean's assessment above, but have changed it to postponed rather than rejected (much like issue #19). Both are a problem, but given the specialized nature of the template (and the fact that I don't use it), I'm unwilling to hold up a release for it.

I would gladly accept anyone else's work on fixing this in a really appropriate way.

Added by Jean Jordaan on Aug 24, 2011 03:18 PM

Hmm, I see we still don't have a template for recent ZEO clusters.

Does this mean that no one is using ZopeSkel to prime their clusters?

Perhaps everyone has a buildout.cfg which works for them.

I'll see if I can figure out a fix tomorrow.

No responses can be added.