[Setup] Re: version error during /bin/buildout

[Martin Aspeli]

Martin Aspeli wrote:
> Gary Koskenmaki wrote:
>> On Sat, 2008-03-15 at 10:59 +0000, Martin Aspeli wrote:
>>> Michael Hierweck wrote:
>>>> Gary Koskenmaki wrote:
>>>>> On Fri, 2008-03-14 at 18:36 +0100, Michael Hierweck wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Michael Hierweck wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> Gary Koskenmaki wrote:
>>>>>>>> On Thu, 2008-03-13 at 08:44 +0000, Martin Aspeli wrote:
>>>>>>>>> Gary Koskenmaki wrote:
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> I was building a plone3 install today when the following error popped up
>>>>>>>>>> when running /bin/buildout:
>>>>>>>>>>
>>>>>>>>>> While:
>>>>>>>>>>   Installing plone.
>>>>>>>>>> Error: There is a version conflict.
>>>>>>>>>> We already have: plone.portlets 1.1.0a1
>>>>>>>>>> but plone.app.portlets 1.1.0a1 requires 'plone.portlets>=1.1dev'.
>>>>>>>>>>
>>>>>> Gary wrote he used Debian tools to look for some files. I'm using Debian
>>>>>> (Etch), too.
>>>>>>
>>>>>> Since no one else whether here nor on IRC knew about this problem I
>>>>>> considerd there might be a causal relationship between that problem and
>>>>>> Debian.
>>>>>>
>>>>>   
>>>>> Just out of curiousity, since you ran into the same problem I did, were
>>>>> you able to find .installed.cfg on your system after the failed
>>>>> buildout?  It was not generated on my system, but has been generated on
>>>>> 3 other identical buildouts I did using Etch a few months back.  
>>>> It was possible for to create Plone 3.0 buildouts using Etch. I did this
>>>> about three weeks ago for the last time. Trying to create Plone 3.1
>>>> buildouts I received the above mentioned error message and the file
>>>> ".installed.cfg" was _not_ created. After downloading and compiling
>>>> Python 2.4 and installing Paste Script and ZopeSkel the error did not
>>>> appear any more. The error is still reproducable. It depends on the
>>>> python interpreter used (/usr/bin/python2.4 vs.
>>>> /opt/python/2.4.4/bin/python2.4) thought both are 2.4.4.
>>> That's worrysome. Can you paste the exact buildout.cfg that caused this 
>>> problem (even if it were generated, I'd like to see it), and the exact 
>>> error. Run buildout with the -vvv flag to get more output and paste the 
>>> whole command run.
>>>
>>> Thanks,
>>> Martin
>>>
>> Martin,
>>
>> Here's a link to the output from bin/buildout and a copy of buildout.cfg
>> from a failed fresh build.
>>
>> http://paste.plone.org/20164
> 
> Please don't use paste.plone.org to send things to the mailing lists. 
> The data there is non-permanent and may have disappeared by the time 
> someone answers your question. :)
> 
> I'll try to have a look later. I must admit I'm a bit confused, though. :-(

Here's the line that seems to be misbehaving:

Error: There is a version conflict.
We already have: plone.portlets 1.1.0a1
but plone.app.portlets 1.1.0a1 requires 'plone.portlets>=1.1dev'.

In plone.app.portlets, we have install_requires>=1.1dev, and indeed the 
plone.portlets egg is version 1.1.0a1. I wonder if your system-wide 
version of setuptools is failing to realise that "1.1.0a1" is >= "1.1dev".

Can you find out which version of setuptools you have in the global 
python install? There should be a setuptools-<version> directory/file in 
/usr/lib/python2.4/site-packages. Look for the specific version.

Martin

-- 
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book