Now recently, I get this error when running the bootstrap script on Karmic :
rm -f autoproj_bootstrap wget http://rock-robotics.org/autoproj_bootstrap --2011-05-27 00:24:13-- http://rock-robotics.org/autoproj_bootstrap Resolving rock-robotics.org... 80.67.28.127 Connecting to rock-robotics.org|80.67.28.127|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 55203 (54K) [text/plain] Saving to: `autoproj_bootstrap' 0K .......... .......... .......... .......... .......... 92% 452K 0s 50K ... 100% 4.76M=0.1s 2011-05-27 00:24:13 (484 KB/s) - `autoproj_bootstrap' saved [55203/55203] ruby autoproj_bootstrap git /home/virtual/hudson/workspace/bootstrap-toolchain/CORBA_IMPL/TAO/TARGET/gnulinux/arch/amd64/branch/toolchain-2.4/buildconf branch=toolchain-2.4 autodetecting the operating system autoproj: installing a proper Ruby environment (this can take a long time) autoproj: installing autoproj and its dependencies (this can take a long time) installing/updating RubyGems dependencies: autobuild, rdoc ERROR: While executing gem ... (TypeError) incompatible marshal file format (can't be read) format version 4.8 required; 227.160 given ERROR: failed to run gem1.8 install autobuild rdoc ERROR: command output is:
That's it. Any clues ?
Peter
Issues with autoproj_bootstrap
On 05/27/2011 12:28 AM, Peter Soetens wrote:
> 2011-05-27 00:24:13 (484 KB/s) - `autoproj_bootstrap' saved [55203/55203]
>
> ruby autoproj_bootstrap git
> /home/virtual/hudson/workspace/bootstrap-toolchain/CORBA_IMPL/TAO/TARGET/gnulinux/arch/amd64/branch/toolchain-2.4/buildconf
> branch=toolchain-2.4
> autodetecting the operating system
> autoproj: installing a proper Ruby environment (this can take a long time)
> autoproj: installing autoproj and its dependencies (this can take a long time)
> installing/updating RubyGems dependencies: autobuild, rdoc
> ERROR: While executing gem ... (TypeError)
> incompatible marshal file format (can't be read)
> format version 4.8 required; 227.160 given
> ERROR: failed to run gem1.8 install autobuild rdoc
> ERROR: command output is:
>
>
> That's it. Any clues ?
Is it transient or permanent ? I know it happens sometimes when the
connection between the rubygems server and client breaks for whatever
reason ...
Sylvain