Here's the thing:

The change to initialize effects that it is called.
Hence, after updating _past_ MonticelloConfigurations-dtl.137,
the Updaters classvar of MCMcmUpdater will be nil, and hence
every following attempt to update will restart from 1 and,
inevitably, fail eventually.
(Evidence: all saved images from the CI since september 3)

What we can do:
- remove the last three .mcm's that reference MonticelloConfigurations-dtl.137
 - update-eem.333
 - update-eem.334
 - update-eem.335
- I don't know whether each of them is an important milestone for loading 
  individually.
  if so:
    - replace 333-335 with maps that refer to MonticelloConfigurations-topa.138
      to skip 137
  if not:
    - make a new 333 that merges the changes of the old 333-335 and
      refers to MonticelloConfigurations-topa.138, also to skip 137.

Thoughts?

Best regards
	-Tobias


On 24.09.2015, at 12:48, commits at source.squeak.org wrote:

> Tobias Pape uploaded a new version of MonticelloConfigurations to project The Trunk:
> http://source.squeak.org/trunk/MonticelloConfigurations-topa.138.mcz
> 
> ==================== Summary ====================
> 
> Name: MonticelloConfigurations-topa.138
> Author: topa
> Time: 24 September 2015, 2:48:24.846 pm
> UUID: 153b9666-3723-4eb0-b230-7bc75450b892
> Ancestors: MonticelloConfigurations-dtl.137
> 
> Do not nil out Updaters on initialize, beacuse this can screw the whole update process.
> 
> =============== Diff against MonticelloConfigurations-dtl.137 ===============
> 
> Item was changed: