Collective zc.buildout recipes

collective.recipe.zope2install needs better diagnostics when dealing with bad Zope tarball

Reported by nutjob on 2010-03-25
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
collective.buildout
Undecided
Unassigned

Bug Description

If there's a transient error or an interruption of the execution of the collective.recipe.zope2install recipe, it's possible to have a truncated Zope-*.tgz tarball left in your downloads cache.

Restarting the buildout results in the recipe discovering the partial tarball, which then attempts to extract it, resulting in a stack trace:

----
An internal error occurred due to a bug in either zc.buildout or in a recipe being used
Traceback (most recent call last):
...
File: "/usr/lib64/python2.4/gzip.py", line 309, in _read_eof
raise IOError, "CRC check failed"
IOError: CRC check failed
----

Users, unaware of any issue, may repeatedly re-try the buildout to no avail. Deleting the partial tarball is the only way to make progress, but Buildout newbies may not realize there is even a "downloads" directory or a download cache specified elsewhere by a particular buildout or user default.cfg file.

Better diagnostics would certainly help. And we could provide excellent diagnostics by including an md5sum as an option to the recipe: it could flag a bad or partial tarball instantly.

Chris Mattmann (chris-mattmann) wrote :

I've seen this too, even in the case where I rm -rf'ed the original buildout checkout dir, and then reran python bootstrap.py -d and then ../bin/buildout. It looks like b/c of the transient nature of the d/l, it can keep getting back *.tar.gz files for Zope.

I was running this on Cent OS 5, with python 2.4.

Florian Tobé (zotcybercase) wrote :

Hi ! I'm trying to install erp5 buildout release following the instructions overthere http://www.erp5.org/HowToUseBuildout
And that (bug) is happening to me ! I found that thread so I deleted the tz file in the .buildout directory I've created with no help. So I've deleted both donwload and eggs content in both .buildout an buildout directory like to restart from scratch and I have now another "assertion error"

While:
  Installing zope2.

An internal error occured due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
  File "/tmp/tmpLnQTqM/zc.buildout-1.4.3-py2.4.egg/zc/buildout/buildout.py", line 1660, in main
  File "/tmp/tmpLnQTqM/zc.buildout-1.4.3-py2.4.egg/zc/buildout/buildout.py", line 532, in install
  File "/tmp/tmpLnQTqM/zc.buildout-1.4.3-py2.4.egg/zc/buildout/buildout.py", line 1204, in _call
  File "/home/florian/.buildout/eggs/erp5.recipe.zope2install-1.0-py2.4.egg/erp5/recipe/zope2install/__init__.py", line 97, in install
    'build_ext', '-i',
AssertionError

this directory /tmp/tmpLnQTqM/ does not exist !

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers