Problem with zopeskel version after running bin/buildout -n after fresh plone 3.3.1 install

[ahoms]

Hi

I've installed plone 3.3.1 in a fresh debian lenny install (xen DomU). After install things worked fine, stopped instance and added some products to buildout.cfg

Running bin/buildout -n gives me this error:

The version, 1.7, is not consistent with the requirement, 'Markdown>=2.0.1'.
While:
  Installing zopeskel.
Error: Bad version 1.7

The error appeared in the first attempt after cheetah install

The products I've added:
    Products.LinguaPlone
    Products.PloneFormGen
    Products.QuillsEnabled
    Products.PloneSurvey
    Products.Maps
    Products.Scrawl

Any hints? Is this a bug?

[Jeff Doolittle]

ahoms wrote:

Hi

I've installed plone 3.3.1 in a fresh debian lenny install (xen DomU). After install things worked fine, stopped instance and added some products to buildout.cfg

Running bin/buildout -n gives me this error:

The version, 1.7, is not consistent with the requirement, 'Markdown>=2.0.1'.
While:
  Installing zopeskel.
Error: Bad version 1.7

The error appeared in the first attempt after cheetah install

The products I've added:
    Products.LinguaPlone
    Products.PloneFormGen
    Products.QuillsEnabled
    Products.PloneSurvey
    Products.Maps
    Products.Scrawl

Any hints? Is this a bug?

I'll just say I have the exact same problem moving from a recent 3.3 install to 3.3.1 using the "bin/buildout -n" process.

----------
Updating zopepy.
Installing zopeskel.
The version, 1.7, is not consistent with the requirement, 'Markdown>=2.0.1'.
While:
  Installing zopeskel.
Error: Bad version 1.7
----------

Products installed:
        Products.CacheSetup
        Products.Scrawl

Jeff

[tixxit]

The problem seems to come from the latest release of Cheetah (2.2.2 - released a couple of days ago), which requries Markdown >= 2.0.1, where as the version specified in the versions.cfg is Markdown = 1.7. This would seem to be a bug in the current Plone 3.3 versions.cfg file. Just add

Cheetah = 2.2.1

to your local versions.cfg file and run buildout again.

[ahoms]

Thanks, it worked!!
Should I open a ticket for that? (it will be the first one for me :) )

2009/9/17 tixxit (via Nabble) <[hidden email]>

The problem seems to come from the latest release of Cheetah (2.2.2 - released a couple of days ago), which requries Markdown >= 2.0.1, where as the version specified in the versions.cfg is Markdown = 1.7. This would seem to be a bug in the current Plone 3.3 versions.cfg file. Just add

Cheetah = 2.2.1

to your local versions.cfg file and run buildout again.

[whijok]

Hi there,

I've tried the Cheetah = 2.2.1 approach, no luck, buildout still complains about Markdown...

I may just ignore it!

[TonyR]

whijok wrote:

I've tried the Cheetah = 2.2.1 approach, no luck, buildout still complains about Markdown...

That's probably because your buildout.cfg is pointing at a different versions.cfg file.

I upgraded to version 3.3.1 by changing the buildout script to point to http://dist.plone.ord/release/3.3.1/versions.cfg and had this issue.

To get around the problem I went to the URL above and copied the whole text into my local versions.cfg file, I then added the Cheetah = 2.2.1 line, re-ran ./bin/biuldout -n and it worked a treat.

[whijok]

TonyR wrote:

whijok wrote:

I've tried the Cheetah = 2.2.1 approach, no luck, buildout still complains about Markdown...

That's probably because your buildout.cfg is pointing at a different versions.cfg file.

I upgraded to version 3.3.1 by changing the buildout script to point to http://dist.plone.ord/release/3.3.1/versions.cfg and had this issue.

To get around the problem I went to the URL above and copied the whole text into my local versions.cfg file, I then added the Cheetah = 2.2.1 line, re-ran ./bin/biuldout -n and it worked a treat.

Thanks Tony(R),

I don't want to waste anyone's valuable tme on this, but that sensible suggestion is what I'd already tried: set the url in buildout.cfg to http://dist.plone.org/release/3.3.1/versions.cfg;  used that url in a browser to grab the contents of the file to replace my existing versions.cfg; then edit the contents in my updated versions.cfg to add our friend the Cheetah, as follows:

# External dependencies
Cheetah = 2.2.1
Markdown = 1.7
PIL = 1.1.6
elementtree = 1.2.7-20070827-preview
feedparser = 4.1
python-openid = 2.2.4
simplejson = 2.0.9

Am I a lemon or is it just one of those things!

[Maurits van Rees-3]

whijok, on 2009-09-23:

> I don't want to waste anyone's valuable tme on this, but that sensible
> suggestion is what I'd already tried: set the url in buildout.cfg to
> http://dist.plone.org/release/3.3.1/versions.cfg;  used that url in a
> browser to grab the contents of the file to replace my existing
> versions.cfg; then edit the contents in my updated versions.cfg to add our
> friend the Cheetah, as follows:
>
> # External dependencies
> Cheetah = 2.2.1
> Markdown = 1.7
> PIL = 1.1.6
> elementtree = 1.2.7-20070827-preview
> feedparser = 4.1
> python-openid = 2.2.4
> simplejson = 2.0.9
>
> Am I a lemon or is it just one of those things!

Make sure you are running buildout in newest mode with 'buildout -n'.
And to get more info, add some 'v's to let buildout be ever more
verbose, like 'buildout -nvvv'.

The versions above look good.  Are you sure these are the versions
that are used?  They are not overridden in some other parts of your
buildout.cfg?  And you do have a versions=versions line in your
buildout.cfg so the versions block is actually used?

--
Maurits van Rees | http://maurits.vanrees.org/
            Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]


_______________________________________________
Setup mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/setup