Collecting Zope==4.1.2
Using cached https://files.pythonhosted.org/packages/66/77/471673eebdcc904eaafaa4b97a01b97b8aa73aed84054248c5f258a00d92/Zope-4.1.2-py2.py3-none-any.whl
but I can't find the announced ZMI History tab.
In the Control Panel, I've got: Zope Version (4.1, python 3.7.3, linux)
so I'm not 100% sure... do I need to enable History?
Basic mistake: Wishing to use plone.recipe.zope2instance I copied the minimal buildout.cfg from the instructions that referenced 4.1 not 4.1.2
Then my buildout install got stuck at: Getting distribution for 'zope.container==4.2.2'.
So I reverted to installing Zope with pip and the wrong things happened.
This time, when buildout failed at zope.container, I installed zope.container using pip install zope.container and the buildout install was able to complete.
I also tried the buildout way with plone.recipe.zope2instance and it worked out well - I changed the Zope version to 4.1.2.
python3.7 -m venv zope
cd zope/
bin/pip install -U pip zc.buildout
vim buildout.cfg # with the content from the installation documentation / section plone.recipe.zope2instance
bin/buildout
I did the same (except that I have python3.6) but I got the error below. I ran bin/buildout a second time because sometimes that works After I installed zope.container separately it worked. Why?
Getting distribution for 'zope.container==4.2.2'.
unable to execute 'x86_64-linux-gnu-gcc': No such file or directory
error: Setup script exited with error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
An error occurred when trying to install /tmp/tmp7_j75m0qget_dist/zope.container-4.2.2.tar.gz. Look above this message for any errors that were output by easy_install.
While:
Installing.
Getting section zopeinstance.
Initializing section zopeinstance.
Installing recipe plone.recipe.zope2instance.
Getting distribution for 'zope.container==4.2.2'.
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
File "/root/Zope-4.1.2/zope/lib/python3.6/site-packages/zc/buildout/buildout.py", line 2174, in main
getattr(buildout, command)(args)
File "/root/Zope-4.1.2/zope/lib/python3.6/site-packages/zc/buildout/buildout.py", line 701, in install
[self[part]['recipe'] for part in install_parts]
File "/root/Zope-4.1.2/zope/lib/python3.6/site-packages/zc/buildout/buildout.py", line 701, in <listcomp>
[self[part]['recipe'] for part in install_parts]
File "/root/Zope-4.1.2/zope/lib/python3.6/site-packages/zc/buildout/buildout.py", line 1324, in __getitem__
options._initialize()
File "/root/Zope-4.1.2/zope/lib/python3.6/site-packages/zc/buildout/buildout.py", line 1432, in _initialize
self.initialize()
File "/root/Zope-4.1.2/zope/lib/python3.6/site-packages/zc/buildout/buildout.py", line 1438, in initialize
recipe_class = _install_and_load(reqs, 'zc.buildout', entry, buildout)
File "/root/Zope-4.1.2/zope/lib/python3.6/site-packages/zc/buildout/buildout.py", line 1388, in _install_and_load
allow_hosts=buildout._allow_hosts
File "/root/Zope-4.1.2/zope/lib/python3.6/site-packages/zc/buildout/easy_install.py", line 957, in install
return installer.install(specs, working_set)
File "/root/Zope-4.1.2/zope/lib/python3.6/site-packages/zc/buildout/easy_install.py", line 730, in install
for dist in self._get_dist(req, ws):
File "/root/Zope-4.1.2/zope/lib/python3.6/site-packages/zc/buildout/easy_install.py", line 574, in _get_dist
dists = [_move_to_eggs_dir_and_compile(dist, self._dest)]
File "/root/Zope-4.1.2/zope/lib/python3.6/site-packages/zc/buildout/easy_install.py", line 1745, in _move_to_eggs_dir_and_compile
[tmp_loc] = glob.glob(os.path.join(tmp_dest, '*'))
ValueError: not enough values to unpack (expected 1, got 0)
Works for me without a problem - also on Python 3.6
Maybe maybe maybe... buildout tried to compile zope.container and failed because you lack the gcc compiler? And pip installs the already compiled wheel?
But this is just guess work - somebody else has to take a look at this.
I think you're right - the error says I am missing gcc. And as you suggest, installing zope.container seems to take care of that. Thanks, @jugmac00, I was working a bit too fast...
Try to meet the prerequisites - otherwise with the next buildout run maybe it will brake again - well, at least when there is a new zope.container version or similar.
Thanks Jürgen. I included this new issue as a postscript to my buildout install adventure of a month ago.
So, 4.1.3 hadn't yet been released and the fixes, which were already made in October were not automatically picked up by buildout. Got it.
I just checked the source of 4.1.3 and VirtualHostMonster.py does incorporate both changes. Those are important changes - VHM is something cool. All is well.
So, 4.1.3 hadn't yet been released and the fixes, which were already made in October were not automatically picked up by buildout. Got it.
One of the reasons to use buildout is especially that the versions get pinned and do not change unintentionally.
Image you do an buildout locally, develop for two weeks and all works well. Then you deploy it on a server - and meanwhile a new release of Zope was made - then on your production server something different gets deployed compared to what you developed on (and maybe is broken).
I just checked the source of 4.1.3 and VirtualHostMonster.py does incorporate both changes. Those are important changes - VHM is something cool. All is well.
After I installed zope.container separately it worked. Why?
