I've just published our first 4.3 alpha image at:
http://ftp.squeak.org/4.3/ This image includes the new Monticello upgrades, providing a base foundation which can handle trunk-updates going forward without having to manually load packages first. I wish it could be as simple as a renamed method, but actually the API's including the types of objects that are passed between MC and MC-Configs have changed. It _might_ be possible to get it to fly through all the way from a 4.2, but working forward from this new baseline is much easier. If you want to get back onto the trunk from an existing 4.2-based image, just load the following (or newer) packages manually from the "trunk" repository, via Monticello: - Collections-cmm.431 - Monticello-cmm.438 - MonticelloConfigurations-cmm.89 Once these versions are loaded, that image can now update from the trunk normally (via "update Squeak" menu option). - Chris On Wed, Mar 16, 2011 at 6:46 AM, Bert Freudenberg <[hidden email]> wrote: > Just publish the addition of the new method and the removal of the old one as two separate packages, with a config map "between" the two forcing the load of the first one. > > - Bert - > > On 16.03.2011, at 03:38, Chris Muller wrote: > >> Unfortunately, I don't think the config can be fixed. It's >> chicken-egg problem; and both parts are the running parts involved in >> the update process itself. >> >> On Tue, Mar 15, 2011 at 9:22 PM, Chris Muller <[hidden email]> wrote: >>> Yikes, my apologies. I will see if I can fix the configurations. >>> >>> In the meantime, if you just want to move forward with trunk again, >>> just load the latest Monticello manually from the trunk, then >>> MonticelloConfigurations. You can then update from the trunk >>> normally. >>> >>> - Chris >>> >>> >>> On Tue, Mar 15, 2011 at 5:31 PM, Levente Uzonyi <[hidden email]> wrote: >>>> On Tue, 15 Mar 2011, Eliot Miranda wrote: >>>> >>>>> Hi Levente, >>>>> >>>>> just when I wanted to update to trunk ;) Is there a work-around, e.g. >>>>> where one can prevent a particular set of packages from being updated? >>>> >>>> There are some workarounds, like commenting the following two lines at the >>>> end of MCMcmUpdater class >> #updateFromRepositories: >>>> >>>> config updateFromRepositories. >>>> config upgrade. >>>> >>>> Or disabling the update of Monticello and MonticelloConfigurations by >>>> evaluating the following before updating: >>>> >>>> #('Monticello' 'MonticelloConfigurations') do: [ :each | >>>> MCMcmUpdater disableUpdatesOfPackage: each ]. >>>> >>>> >>>> Levente >>>> >>>>> >>>>> On Tue, Mar 15, 2011 at 12:56 PM, Levente Uzonyi <[hidden email]> wrote: >>>>> >>>>>> The update process is broken, because Monticello is updated before >>>>>> MonticelloConfigurations. When Monticello-cmm.438 is loaded, >>>>>> MonticelloConfigurations is still at ul.84. >>>>>> MCConfiguration >> #versionNamed:for:from: tries to send >>>>>> #versionFromFileNamed: to an MCHttpRepository, but that method is not >>>>>> there >>>>>> anymore. >>>>>> >>>>>> >>>>>> Levente >>>>>> >>>>>> snip >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> > > > |
Free forum by Nabble | Edit this page |