Bob,

>>    Did I try 'Smalltalk condenseChanges' somewhere along ?

> I don't know. Did you? Is it possible that the file got truncated somehow?
Could you have condensed the > changes and then quit the image without
saving?

    Yes, I recall it now. You are correct. I did condense the changes and
did choose to quit WITHOUT saving and ending up with a bad system.

    I like to submit this as a bug in Squeak (not my fault ;-)

>>    BTW, how did you know ;-)

> Umm.. know what?

    The problem is in the change file.

> BTW - did you browse the methods in TextPropertiesMorph? How many of them
were messed up?

    I didn't go through all of them, but the first 3 were bad.

> I don't have an updated 3.1 image ...

    You don't mean you are not on the bleeding edge ?

> that uses v3sources, ...

    and your latest greatest updated 3.1 image uses v4sources ;-)

    Cheers,

    PhiHo


----- Original Message -----
From: "Bob Arning" <arning at charm.net>
To: <phiho.hoang at home.com>; <squeak-dev at lists.squeakfoundation.org>
Sent: Thursday, August 23, 2001 10:35 PM
Subject: Re: [updates] 21 more for 3.1 alpha


On Thu, 23 Aug 2001 22:20:16 -0400 "PhiHo Hoang" <phiho.hoang at home.com>
wrote:
>    I said I was updating from a virgin image (latest update #4216)
>
>> It sounds as if your changes file has gotten out of sync with the image.
>Possibilities are:
>> - the changes file was downloaded/uncompressed with some tool that
>replaced <cr> with <crlf>
>> - the changes file went over 32 meg
>> - the changes file belongs to another image
>
>    None of the above, but the change file was not so virgin.
>
>    Did I try 'Smalltalk condenseChanges' somewhere along ?

I don't know. Did you? Is it possible that the file got truncated somehow?
Could you have condensed the changes and then quit the image without saving?

>The change file
>is now only 4,303KB. It should be above 10MB.

Should be? Why? I don't have an updated 3.1 image that uses v3sources, so
I'm not real sure what the likely size of the changes file is. Maybe it's 4
meg, maybe it's 10.

>    Is there anything like 'Smalltalk undoCondenseChanges' or 'Smalltalk
>expandChanges' ?

No. Unless you have a backup somewhere from before the condense.

>    BTW, how did you know ;-)

Umm.. know what?

>    And what is the use of  'Smalltalk condenseChanges' ?  I congratulated
>myself for saving 6MB of disk space for each set of image/change :-(

Two uses:
- it saves some disk space (clearly less important these days)
- it keeps the changes file usable as there is a limit of 32M each for
changes and sources.

BTW - did you browse the methods in TextPropertiesMorph? How many of them
were messed up?

Cheers,
Bob