On 15 March 2013 11:19, Bob Arning <arning315 at comcast.net> wrote:
> Not sure what sort of failures you are seeing, but I tried to replicate
> anyway. I deleted the changes file, started the image, OK'd the warning and
> filed out a recently-added class. I got one walkback which I fixed with:
>
> 'From Squeak4.4 of 1 March 2013 [latest update: #12489] on 15 March 2013 at
> 7:14:23 am'!
>
> !BasicClassOrganizer methodsFor: 'fileIn/Out'!
> fileOutCommentOn: t1 moveSource: t2 toFile: t3
>     | t4 |
>     classComment
>         ifNotNil: [t1 cr.
>             t4 := RemoteString
>                         newString: (classComment text ifNil: '**missing
> comment**')
>                         onFileNumber: t3
>                         toFile: t1.
>             t2
>                 ifTrue: [classComment := t4]]! !
>
> Otherwise, the fileout seems fine.

OK, that looks like the same walkback I saw. To be clear, it looks
like you turned `classComment text` into `classComment text ifNil:
'**missing comment**'` ?

frank

> Cheers,
> Bob
>
> On 3/15/13 6:10 AM, Frank Shearar wrote:
>
> So I freely confess: I should not have deleted the directory from
> which I was running an image. When I saved the image, the image still
> worked, but of course its changes file was broken.
>
> I now have a few tens of hours of work in an image that I need to
> extract only the following techniques all fail:
> * filing out the class
> * making a new changeset and filing that out
> * saving the package through MC
> * deleting the corrupted changes file
>
> So one option that I don't particularly want to do is to open a new
> image and hand cut-n-paste (via emacs, because on Linux the line
> endings get messed up copying between Squeak images directly), method
> by method, the source.
>
> Is there an easier way of recovering from this mess?
>
> frank
>
>
>
>
>
>