hello Martin, This is becacuse metacello finds another version already registered. Usually you can avoid that adding:
onConflict: [ :e | e useLoaded ] and/or onUpgrade: [ :e | e useLoaded ] both messages act in different contexts: onConflict: between what is in disk and what is in image. onUpgrade: between what is in your local repo and what is asked to be cloned. and take note that many baselines may have cyclic references (that metacello solves, at the end), this is not because you *actually* have already the project loaded/cloned. cheers, Esteban > On 2 Jun 2018, at 04:42, Martin McClure <[email protected]> wrote: > > On a Pharo7, Linux, from yesterday: > Build information: > Pharo-7.0+alpha.build.994.sha.6b52ae62b755d8778fa0b5a4ac53b39b6c107dc9 > (32 Bit) > > During an Iceberg load of a Metacello baseline, I get a dialog > > Duplicated project! > There is already a project "OSSubprocess" in this installation. > > It's true that I do have a Git clone of OSSubprocess in my > pharo-local/iceberg directory, since this is the second image I've > loaded into, but before it's always just used the already-cloned repo > rather than trying to create a new one. > > Any ideas on what the correct behavior currently is (for the system, and > for me) at this point? > > Thanks, > -Martin >
