On Mon, Oct 11, 2010 at 10:50, Andreas Jung li...@zopyx.com wrote:
Hi there,
Hi Andreas !
Second: how to fix this finally?
I know it's not you want hear but build an internal infrastructure
was a great improvement for us. Here, all is internal (debian mirror,
zope mirror, pypi mirror,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sebastien Douche wrote:
On Mon, Oct 11, 2010 at 10:50, Andreas Jung li...@zopyx.com wrote:
Hi there,
Hi Andreas !
Second: how to fix this finally?
I know it's not you want hear but build an internal infrastructure
was a great improvement
On Tue, Oct 12, 2010 at 5:01 PM, Andreas Jung li...@zopyx.com wrote:
sorry - wrong answer. This is a stupid misbehavior of setuptools
or zc.buildout. The zc.buildout package are hosted on PyPI and PyPI
was available. There is no reason for whatever component
to connect to buildout.org and fail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
On Tue, Oct 12, 2010 at 5:01 PM, Andreas Jung li...@zopyx.com wrote:
sorry - wrong answer. This is a stupid misbehavior of setuptools
or zc.buildout. The zc.buildout package are hosted on PyPI and PyPI
was available. There
Am 12.10.2010, 17:12 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu:
Are you sure you used the latest distribute release? I hadn't had any
problem at all during that whole time.
I had it here with the CMF buildout and also got it in a report from a
customer.
Charlie
--
Charlie Clark
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
buildout.org is currently down and any existing buildout
is trying to phone home to buildout.org (likely because
buildout.org is configured in the package metadata as 'url').
Even releasing zc.buildout 1.5.2 with 'url' set to
