Thanks Doug, Ned,

This in fact works great until the crash of CS 5501. Time to build a new
VM.

Thanks again guys.

Michael

Doug Way <dway at riskmetrics.com> wrote:
> Ned Konz wrote:
> 
> >On Friday 21 November 2003 5:28 am, michael.cole at nimiq.net wrote:
> >  
> >
> >>Hi,
> >>
> >>I have an image that has been marked as version 3.6  and want to now
> >>allow it to advance to 3.7a. Changing the version reported in
> >>SystemVersion doesn't seem to do the trick. Any hints?
> >>    
> >>
> >
> >The magic is in the CS 5429advanceTo37-dew.cs:
> >
> >"delete the four gamma updates because they will be re-loaded anyway, so we 
> >avoid popup messages"
> >			ChangeSorter removeChangeSetsNamedSuchThat:
> >					[:name | (name beginsWith: '542') &
> >							(name beginsWith: '5420') not &
> >							(name beginsWith: '5429') not].
> >			SystemVersion newVersion: 'Squeak3.7alpha'.
> >			SystemVersion current date: '11 September 2003'.
> >			self inform: 'You may now save this Version 3.7alpha image
> >and retrieve updates again for 3.7alpha and beyond.'
> >
> 
> You must have found this poking around on the updates ftp site... it 
> wasn't actually included in the update stream. :-)
> 
> I wrote this up a little while ago and was going to add it to the update 
> stream for 3.6 as a convenience for people to optionally upgrade to 
> 3.7alpha.  But I also wanted it to reset the update stream back to 5424 
> if you said "no" to the prompt, so that you could upgrade again later if 
> desired.  I could easily get the update stream resetting to work, so 
> then I gave up on it.
> 
> However, resetting the update stream (if you say "no") isn't really 
> *that* important, so I just decided to add the 5429 update to the stream 
> anyway.  (The only minor downside is that if you update from 3.6, and 
> decline the offer to move to 3.7alpha, then save your image, you won't 
> get a second chance to upgrade to 3.7alpha.  Not really a big deal.  You 
> could always open the 5429 changeset in the change sorter and execute 
> the postscript, anyway.)
> 
> This update does a few extra nice things such as deleting updates 
> 5421-5424 so that you won't get the annoying "already loaded" dialogs 
> when it tries to overwrite them.
> 
> (I purposely left a small gap between 5424 and 5429 for any post-3.6 
> patches.  Actually that's not even strictly necessary, but it's nice to 
> have different numbers for different updates.)
> 
> So Michael, to answer your question, all you have to do now to update 
> from 3.6 to 3.7alpha is go to "help"/"update code from server" !  
> However, note that updating past 5501 will slow down quite a bit, until 
> I fix that. (see my [BUG] post from a few minutes ago)
> 
> - Doug