[Distutils] Buildout release news

[Maurits van Rees]

Op 24-08-10 17:47, Gary Poster schreef:
> On Aug 24, 2010, at 10:29 AM, Maurits van Rees wrote:
>> Op 24-08-10 13:33, Reinout van Rees schreef:
>>> On 08/20/2010 05:22 PM, Gary Poster wrote:
>>>> I intend to release zc.buildout 1.5.0 Monday, August 23.
>>>
>>> I used http://pypi.python.org/pypi/osc.recipe.sysegg/ to reliably grab
>>> specific system python packages (PIL, matplotlib, etc). That one is
>>> broken with 1.5.0, as it cannot find PIL and friends anymore.
>>>
>>> Using the
>>> http://svn.zope.org/repos/main/zc.buildout/branches/1.4/bootstrap/bootstrap.py
>>> helps getting everything working (at least temporary).
>>>
>>> osc.recipe.sysegg's problem is that a pkg_resources.require(egg) call
>>> doesn't find any of the system eggs anymore. Am I correct that that's
>>> one of buildout's changes? That the recipes are really totally isolated?
(...)
>> $ bin/buildout
>> While:
>>   Installing.
>>   Loading extensions.
>> Error: There is a version conflict.
>> We already have: zc.buildout 1.5.0
>>
>> With more debugging:
>>
>> $ bin/buildout -vvvvvvvvvvvvvvvvvvvvD
>> Installing 'buildout-versions'.
>> We have the distribution that satisfies 'buildout-versions==1.3'.
>> While:
>>   Installing.
>>   Loading extensions.
>> Traceback (most recent call last):
>>   File ".../zc.buildout-1.5.0-py2.4.egg/zc/buildout/buildout.py", line 1784, in main
>>   File ".../zc.buildout-1.5.0-py2.4.egg/zc/buildout/buildout.py", line 410, in install
>>   File ".../zc.buildout-1.5.0-py2.4.egg/zc/buildout/buildout.py", line 960, in _load_extensions
>>   File ".../zc.buildout-1.5.0-py2.4.egg/zc/buildout/easy_install.py", line 1085, in install
>>   File ".../zc.buildout-1.5.0-py2.4.egg/zc/buildout/easy_install.py", line 942, in install
>> VersionConflict: There is a version conflict.
>> We already have: zc.buildout 1.5.0
>> Starting pdb:
>>> .../zc.buildout-1.5.0-py2.4.egg/zc/buildout/easy_install.py(942)install()
>> (Pdb) a
>> self =<zc.buildout.easy_install.Installer instance at 0x101e1e320>
>> specs = ['buildout-versions']
>> working_set =<pkg_resources.WorkingSet object at 0x10040e810>
>>
>>
>> The workaround is of course to remove bin/buildout, do python2.4 bootstrap.py and run bin/buildout again.  So probably no big deal, but a bit unexpected anyway.
>
> OK, fair enough.  Thanks for the report.
>
> I'm inclined to agree with you that it is not a big deal.  It sounds like you need a resolution to the osc.recipe.sysegg problem more?

Ah, you confuse me with my evil twin brother Reinout. :-)  Well, okay, 
he is not evil and no twin, but he is my brother.  The first part of the 
mail (about osc.recipe.sysegg) was from him, and I reacted to that in 
the second half with my own little problems.

To me it sounds like osc.recipe.sysegg should not be necessary anymore 
when using zc.buildout 1.5.0 and zc.recipe.egg 1.3.2.

-- 
Maurits van Rees
Programmer, Zest Software