[boost] Re: boost v 1.33 ?

From: Stefan Slapeta (stefan_at_[hidden])
Date: 2005-02-01 13:31:53

Caleb Epstein wrote:

[...]
> 
> I'm trying to test the change suggested in the first thread now, but
> regression.py is currently falling over on me:
> 
> # Getting sources (Tue, 01 Feb 2005 17:21:53 +0000)...
> # Downloading "http://www.meta-comm.com/engineering/boost/snapshot/boost-CVS-HEAD.tar.bz2"
> to "/home/nbde52d/src/boost-regression"...
> # Looking for old unpacked archives...
> # Unpacking boost tarball
> ("/home/nbde52d/src/boost-regression/boost-CVS-HEAD.tar.bz2")...
> #     Unpacked into directory
> "/home/nbde52d/src/boost-regression/boost-CVS-HEAD-05-02-01-1631"
> # Deleting "/home/nbde52d/src/boost-regression/boost" directory...
> # Renaming "/home/nbde52d/src/boost-regression/boost-CVS-HEAD-05-02-01-1631"
> into "/home/nbde52d/src/boost-regression/boost"
> Traceback (most recent call last):
>   File "./regression.py", line 837, in ?
>     commands[ command ]( **accept_args( args ) )
>   File "./regression.py", line 666, in regression
>     setup( comment, toolsets, bjam_toolset, pjl_toolset, monitored, proxy, [] )
>   File "./regression.py", line 396, in setup
>     import_utils()
>   File "./regression.py", line 365, in import_utils
>     import utils as utils_module
> ImportError: No module named utils
> 

This is a typical error that occurs after an incomplete tarball download 
(which happens quite frequently, and _when_ it happens, its 
reproducible, say, you can't download a complete tarball then for about 
an hour! I always thought this is a problem of our proxy.)
At least, this says that the utils directory isn't on your hard disk.
Just test the integrity of your tarball...

BTW, it's strange that the testing script continues even if the tarball 
isn't complete. Isn't there an error reported from the extraction routine??

Stefan