Currently download.zope.org seems to be down. When running a buildout installing Plone this is a problem since the Plone version configs extend from download.zope.org.
Buildout throws an exception because it cannot download the version pinnings:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Buildout Extends Cache
Configuring an extends cache can help in such situations, although it
is wise to do that before something goes down.
The cache will normally try to update the extends. If the update fails
it will then take the cached version of the config file. This also
allows to run buildout in offline mode (
bin/buildout -o) which will
not update the cached extends.
You can easily set this up for your machine by creating a
~/.buildout/default.cfg file which will be loaded for every buildout
configuration run by this user:
You also need to create the specified directory:
When running buildout it will automatically store the downloaded extends in the configuration with a hashed name.
The hash can easily be generated using python:
1 2 3
I’ve uploaded the caches for download.zope.org used when using buildout for Plone 4.2:
buildout.org, which is required for bootstrapping, is on the
same host as
download.zope.org it is down too.
You can work around bootstrapping issues by doing an offline
bootstrap. For this you need to have another buildout already
installed which has the same python and
You can use the other buildout for bootstrapping like this:
This bootstraps the buildout in your working directory with the python
/ buildout versions of the other buildout. Using the
-o flag runs
the bootstrap in offline mode.
Contact me if you have questions or need
other caches for