yeah... I commited today a fix to use new ocompletion instead the old one... and looks like metacello is refusing to find it... looking it...
On Jun 13, 2012, at 6:01 PM, Robert Shiplett wrote: > MetacelloCommonMCSpecLoader > > retryingResolvePackageSpecReferences: packageSpec gofer: gofer > > On 13 June 2012 12:59, Robert Shiplett <[email protected]> wrote: >> After my 'step' 3 ... >> >> Could not resolve OC for OB >> >> >> >> On 13 June 2012 12:55, Robert Shiplett <[email protected]> wrote: >>> I'll start from scratch to validate .. but >>> >>> On 1st pass transcript ended as >>> >>> Fetched -> OB-Refactory-GuillermoPolito.258 --- >>> http://www.squeaksource.com/PharoOB --- >>> http://www.squeaksource.com/PharoOB >>> Fetched -> OB-Regex-lr.30 --- http://www.squeaksource.com/PharoOB --- >>> http://www.squeaksource.com/PharoOB >>> ...RETRY-> OCForOB-EstebanLorenzano.6 >>> ...RETRY-> OCForOB-EstebanLorenzano.6 >>> ...FAILED-> OCForOB-EstebanLorenzano.6 >>> >>> >>> >>> On 13 June 2012 12:34, Esteban Lorenzano <[email protected]> wrote: >>>> fails with which error? >>>> >>>> On Jun 13, 2012, at 5:15 PM, Robert Shiplett wrote: >>>> >>>>> load of OmniBrowser 1.4.1 failed in release Pharo-1.4-14438-OneClick >>>>> newly installed on Win32 XP SP3 >>>>> >>>>> 3 steps: >>>>> >>>>> MetacelloConfigurationBrowser open. >>>>> >>>>> >>>>> 'Load configuration' popup menu option selected for Estaban .157 config >>>>> >>>>> "no sign of any side-effect visible to user " >>>>> >>>>> 'Load configuration and stable version' popup menu option selected for >>>>> Estaban .157 config >>>>> >>>>> " then fails after many stages of load and compile " >>>>> >>>> >>>> >
