Hi guys

Clément asked us a while ago to update Fuel for Spur support and we did 
(https://pharo.fogbugz.com/f/cases/14688/Change-CompiledMethod-header-serialization-to-use-signed-integer
 
<https://pharo.fogbugz.com/f/cases/14688/Change-CompiledMethod-header-serialization-to-use-signed-integer>).
 The problem now: Fuel is an integral part of the integration process and the 
change to the Fuel version number means that the automatic integration will not 
work. Here’s why:

This slice can't be automatically integrated because I changed the Fuel version 
number. Now, when the image worker reads the result from the validation, Fuel 
raises an exception because of the different version numbers in the parent and 
child image.

We should probably add a mechanism that ensures that the original Fuel version 
is reloaded after the validation, such that the Fuel file is written by the 
same version that then reads it in the  parent.

Can someone please manually integrate or (which would be way cooler) adapt the 
integration process such that future updates to Fuel can be automatically 
integrated?

Cheers,
Max

Reply via email to