Buildout for 4.3.8 needs tweeking - work in progress - OS Microsoft

Building from the corrected 4.3.7 Buildout, I am now working through 4.3.8 Buildout

Setuptools version conflict was solved by remarking out base.cfg and versions.cfg
extends =

base.cfg

versions.cfg

  http://dist.plone.org/release/4.3.8/versions.cfg

The next glitch was that instance_base not found
This was fixed by remarking out <=instance_base

[instance]

<= instance_base

recipe = plone.recipe.zope2instance
http-address = 8080

I'm now working on
Error: Couldn't install: Acquisition 2.13.9

If anyone has a suggestion on this ... TIA

This is where I am stuck at the moment - Any suggestions - TIA

creating build\temp.win-amd64-2.6\Release\src\Acquisition
C:\Users\IntranetGWT\AppData\Local\Programs\Common\Microsoft\Visual C++ for Pyth
on\9.0\VC\Bin\amd64\cl.exe /c /nologo /Ox /MD /W3 /GS- /DNDEBUG -Iinclude -Isrc
-IC:\Plone43\python\include -IC:\Plone43\python\PC /Tcsrc\Acquisition_Acquisiti
on.c /Fobuild\temp.win-amd64-2.6\Release\src\Acquisition_Acquisition.obj
_Acquisition.c
include\ExtensionClass/ExtensionClass.h(83) : fatal error C1083: Cannot open inc
lude file: 'Python.h': No such file or directory
error: Setup script exited with error: command '"C:\Users\IntranetGWT\AppData\Lo
cal\Programs\Common\Microsoft\Visual C++ for Python\9.0\VC\Bin\amd64\cl.exe"' fa
iled with exit status 2
An error occurred when trying to install Acquisition 2.13.9. Look above this mes
sage for any errors that were output by easy_install.
Could't load zc.buildout entry point default
from plone.recipe.zope2instance:
Couldn't install: Acquisition 2.13.9.
While:
Installing.
Getting section instance.
Initializing section instance.
Installing recipe plone.recipe.zope2instance.
Getting distribution for 'Acquisition==2.13.9'.
Error: Couldn't install: Acquisition 2.13.9

C:\Plone43>

Install the python-dev(el) package which is necessary for any Plone installation since 15 years.

-aj

Putting Python-dev didn't seem to work

Reflected on ol' stackoverflow I once played with

Amended it for Acquisition 2.13.9 as follows

  1. Install Python 2.6 on Drive C:\
  2. C:\Plone43>c:\plone43\bin\easy_install-2.6 c:\python26\lib\site-packages\acquisi
    tion-2.13.9.tar.gz
  3. Create a new folder called acquisition-2.13.9-py2.6.egg in C:\Plone43\eggs\
  4. Copy C:\Python26\lib\site-packages\acquisition-2.13.9-py2.6.egg-info to C:\Plone43\eggs\acquisition-2.13.9-py26.egg and rename to EGG-INFO
  5. Also copy the Acquisition folder in C:\Python26\lib\site-packages\ to C:\Plone43\eggs\acquisition-2.13.9-py2.6.egg
  6. Next copy: folder: C:\Python26\lib\site-packages\acquisition-2.13.9-py2.6.egg-info
    folder: C:\Python27\lib\site-packages\acquisition to C:\Plone43\python\Lib\site-packages
  7. Start commandbox and run bin\buildout

Buildout continues to repozo and stops

Getting required 'Acquisition==2.13.9'
We have the distribution that satisfies 'Acquisition==2.13.9'.
......
While:
Installing.
Getting section repozo.
Error: The referenced section, 'repozo', was not defined.

C:\Plone43>

Maybe the repozo section is defined in your base.cfg you removed earlier?

The recommended version Python is Python 2.7 for Plone 4.3 (just as a remark).

-aj

Thx Thomas, It seems taking out base.cfg earlier got me past a couple of hurdles -
I have now restored base.cfg BUT remarked out buildout.dumppickedversions in extensions =
I have also now unremarked <=instance_base in [instance]

Running buildout give me an error at lxml = 2.3.6
I'll manually install as per previous example

Hi AJ
The MS application of Plone @ 4.3.1 started off with Python 2.6
As there are apparently not enough MS users the incremental upgrades through 4.3.6 stayed with Python 2.6 - My efforts with 4.3.7 and 4.3.8 is just a work-up from the original 4.3.1

Upgrading to 4.3.8 from 4.3.6 has been successfully done

In trying to do the upgrades I maintained a truly 'vanilla' build with no add-ons.

Plone upgraded successfully to 4.3.7 by correcting the buildout.cfg with
plone.app.dexterity to 2.0.16
Upgrade originally given from 2.0.13 to 2.0.15 in the documentation

4.3.8

  1. Taking my previous trial and error I manually pre-installed acquisition-2.13.9-py2.6-win-amd64.egg
    in the eggs directory
  2. In base.cfg remark out buildout.dumppickedversions due to the conflict with setuptools
  3. Pinned Zope2 = 2.13.24 to [versions]

Version Overview
Plone 4.3.8 (4312)
CMF 2.2.9
Zope 2.13.24
Python 2.6 (r26:66721, Oct 2 2008, 11:06:43) [MSC v.1500 64 bit (AMD64)]
PIL 2.7.0 (Pillow)

I will try this several more times to try and refine what I have done here.

Happy to post my .cfg files if that is useful to the Plone users using Microsoft.
I did it using Win7

4.3.8 - Production Version (offline using a backup build)

  1. Taking my previous trial and error I manually pre-installed acquisition-2.13.9-py2.6-win-amd64.egg
    in the eggs directory

  2. In base.cfg remark out buildout.dumppickedversions due to the conflict with setuptools

  3. Pinned Zope2 = 2.13.24 to [versions]

  4. Ran Buildout

  5. Still had conflict with setuptools
    5a. remarked out versions.cfg
    5b. Used http://dist.plone.org/release/4.3.8/versions.cfg
    5c. This got me past the conflict with setuptools, but gave me a lxml problem
    5d. Don't know what I did to get past this
    5e. Then I found my own typo's in the 4.3.8 buildout.cfg file

  6. Ran the buildout for my production model and have successfully attained 4.3.8

Version Overview
Plone 4.3.8 (4312)
CMF 2.2.9
Zope 2.13.24
Python 2.6 (r26:66721, Oct 2 2008, 11:06:43) [MSC v.1500 64 bit (AMD64)]
PIL 2.7.0 (Pillow)