Adding ZopeSkel in a Plone 3 buildout fails

4 messages Options
Embed this post
Permalink
Vincent Fretin

Adding ZopeSkel in a Plone 3 buildout fails

Reply Threaded More More options
Print post
Permalink
Hi,

It seems that every buildout including ZopeSkel, mainly the one
created with the UnifiedInstaller are broken.
The user will see the following traceback:
Updating zope2.
Updating fake eggs
Updating productdistros.
Installing instance.
The version, 1.7, is not consistent with the requirement, 'Markdown>=2.0.1'.
While:
  Installing instance.
Error: Bad version 1.7

It's because ZopeSkel depends of Cheetah>1.0
and Cheetah 2.2.2 now explicitly say it depends on Markdown >= 2.0.1
(I don't know why this specific version)
and we have Markdown 1.7 pinned in versions.cfg.

The current quick solution is to pin an old version of Cheetah in the
buildout.cfg
[versions]
Cheetah = 2.2.1
it works because this version don't declare the Markdown dependency.

or try to pin
Markdown = 2.0.1
but some people had problems with it. Is it always the case?

Or if we don't want people complains about broken buildout; we can
release a new ZopeSkel version
with the following requirement:
Cheetah>1.0,<2.2.2
I don't like this solution, it's silly to add a constraint like that
just to unbreak current buildout.

So what do we do?
pin
Cheetah = 2.2.1
or
Markdown = 2.0.1
?

Vincent Fretin
Ecreall
Site : http://vincentfretin.ecreall.com

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Gilles Lenfant

Re: Adding ZopeSkel in a Plone 3 buildout fails

Reply Threaded More More options
Print post
Permalink
Le 23 sept. 09 à 19:30, Vincent Fretin a écrit :

Hi,

To fix this, Mardown peole should add elementtree in the requirements  
when on python 2.4 and add a Markdown-x.y.z-py24.egg.

The setup.py could look like this:

import sys
...
install_requires = ['whatever', ...]
if sys.version_info < (2, 5):
     install_requires.append('elementtree')
...
def setup(
     ...
     install_requires = install_requires,
     ...)

But their tracker seems to be disabled.

> Hi,
>
> It seems that every buildout including ZopeSkel, mainly the one
> created with the UnifiedInstaller are broken.
> The user will see the following traceback:
> Updating zope2.
> Updating fake eggs
> Updating productdistros.
> Installing instance.
> The version, 1.7, is not consistent with the requirement,  
> 'Markdown>=2.0.1'.
> While:
>  Installing instance.
> Error: Bad version 1.7
>
> It's because ZopeSkel depends of Cheetah>1.0
> and Cheetah 2.2.2 now explicitly say it depends on Markdown >= 2.0.1
> (I don't know why this specific version)
> and we have Markdown 1.7 pinned in versions.cfg.
>
> The current quick solution is to pin an old version of Cheetah in the
> buildout.cfg
> [versions]
> Cheetah = 2.2.1
> it works because this version don't declare the Markdown dependency.
>
> or try to pin
> Markdown = 2.0.1
> but some people had problems with it. Is it always the case?
>
> Or if we don't want people complains about broken buildout; we can
> release a new ZopeSkel version
> with the following requirement:
> Cheetah>1.0,<2.2.2
> I don't like this solution, it's silly to add a constraint like that
> just to unbreak current buildout.
>
> So what do we do?
> pin
> Cheetah = 2.2.1
> or
> Markdown = 2.0.1
> ?
>
> Vincent Fretin
> Ecreall
> Site : http://vincentfretin.ecreall.com
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9-12, 2009. Register  
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Plone-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-developers


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Vincent Fretin

Re: Adding ZopeSkel in a Plone 3 buildout fails

Reply Threaded More More options
Print post
Permalink
Hi Gilles,

What you said fix another failure when installing ZopeSkel with
easy_install and python2.4, this one:
markdown.MarkdownException: Failed to import ElementTree
The problem I described is another problem, it's just a pinning
conflicts when installing ZopeSkel in a Plone buildout.

Vincent

On Thu, Sep 24, 2009 at 11:20 AM, Gilles Lenfant
<[hidden email]> wrote:

> Le 23 sept. 09 à 19:30, Vincent Fretin a écrit :
>
> Hi,
>
> To fix this, Mardown peole should add elementtree in the requirements when
> on python 2.4 and add a Markdown-x.y.z-py24.egg.
>
> The setup.py could look like this:
>
> import sys
> ...
> install_requires = ['whatever', ...]
> if sys.version_info < (2, 5):
>    install_requires.append('elementtree')
> ...
> def setup(
>    ...
>    install_requires = install_requires,
>    ...)
>
> But their tracker seems to be disabled.
>
>> Hi,
>>
>> It seems that every buildout including ZopeSkel, mainly the one
>> created with the UnifiedInstaller are broken.
>> The user will see the following traceback:
>> Updating zope2.
>> Updating fake eggs
>> Updating productdistros.
>> Installing instance.
>> The version, 1.7, is not consistent with the requirement,
>> 'Markdown>=2.0.1'.
>> While:
>>  Installing instance.
>> Error: Bad version 1.7
>>
>> It's because ZopeSkel depends of Cheetah>1.0
>> and Cheetah 2.2.2 now explicitly say it depends on Markdown >= 2.0.1
>> (I don't know why this specific version)
>> and we have Markdown 1.7 pinned in versions.cfg.
>>
>> The current quick solution is to pin an old version of Cheetah in the
>> buildout.cfg
>> [versions]
>> Cheetah = 2.2.1
>> it works because this version don't declare the Markdown dependency.
>>
>> or try to pin
>> Markdown = 2.0.1
>> but some people had problems with it. Is it always the case?
>>
>> Or if we don't want people complains about broken buildout; we can
>> release a new ZopeSkel version
>> with the following requirement:
>> Cheetah>1.0,<2.2.2
>> I don't like this solution, it's silly to add a constraint like that
>> just to unbreak current buildout.
>>
>> So what do we do?
>> pin
>> Cheetah = 2.2.1
>> or
>> Markdown = 2.0.1
>> ?
>>
>> Vincent Fretin
>> Ecreall
>> Site : http://vincentfretin.ecreall.com
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry® Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9-12, 2009. Register
>> now!
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Plone-developers mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/plone-developers
>
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Vincent Fretin

Re: Adding ZopeSkel in a Plone 3 buildout fails

Reply Threaded More More options
Print post
Permalink
I pinned Cheetah to 2.2.1 in plonenext/3.3 to fix this issue for Plone
3.3.2. The unified-installer synchronize its versions.cfg with the one
in plonenext/3.3.

Vincent

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers