[Pharo-project] Problem in Pharo 1.1 (Igor?) : You have reached the size limit of the changes file.

Mariano Martinez Peck marianopeck at gmail.com
Thu May 13 19:09:33 EDT 2010


On Thu, May 13, 2010 at 8:26 PM, Stéphane Ducasse <stephane.ducasse at inria.fr
> wrote:

> mariano
>
> i just released a fix could you stress the system?
>

wiiiiiii

My .changes is now 36MB. It seems to work ok.



>
> Stef
>
> On May 13, 2010, at 2:31 PM, Mariano Martinez Peck wrote:
>
> >
> >
> > On Thu, May 13, 2010 at 1:17 PM, David T. Lewis <lewis at mail.msen.com>
> wrote:
> > On Thu, May 13, 2010 at 10:56:17AM +0300, Igor Stasenko wrote:
> > > On 13 May 2010 10:33, St??phane Ducasse <stephane.ducasse at inria.fr>
> wrote:
> > > > oops
> > > > Igor do you have more information?
> > > > how do we do that?
> > > >
> > > just replace CompiledMethod>>checkOKToAdd:at:, or take it from trunk.
> > >
> > > As far as i can tell, everything else should work fine after that.
> > > This is not my contribution , so i don't know all nuances, sorry.
> > >
> > > I just made things which allow source pointers > 32Mb to be stored in
> > > method trailers, while others put this in use in various places :)
> >
> > That is probably all that is needed, yes. But be sure to test it.
> > When I did this for trunk, I tested by loading some big Monticello
> > package endlessly in a loop until I got the changes file up to
> > a couple hundred megabytes. You should be able to do this, save
> > and restart the image, browse all old methods is the sources file
> > and so forth. Then modify some method and make sure your change
> > appears at the end of the huge changes file, and that you can
> > revert your most recent change. And of course you should get no
> > warning dialog about the changes file size.
> >
> > Somebody with a fast computer should volunteer to test this. I
> > recall that it took a long time on my slow laptop computer with
> > slow disk drive ;)
> >
> >
> >
> > Thanks Dave. In my case, I accidently did something similar: I installed
> Seaside 3.0 a couple of times:
> >
> > Gofer new
> >     squeaksource: 'MetacelloRepository';
> >     package: 'ConfigurationOfSeaside';
> >     load.
> >
> > And then evaluate:
> >
> > ConfigurationOfSeaside project latestVersion load: #( 'Seaside 3.0'
> 'Magritte2' 'Pier2' 'Pier2 AddOns' ).
> >
> >
> > There will be some errors and deprecated...just proceed them as this is
> only to increase the .changes
> >
> > Cheers
> >
> > Mariano
> >
> > Dave
> >
> >
> > _______________________________________________
> > Pharo-project mailing list
> > Pharo-project at lists.gforge.inria.fr
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >
> > _______________________________________________
> > Pharo-project mailing list
> > Pharo-project at lists.gforge.inria.fr
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20100514/d42aab60/attachment-0001.html>


More information about the Pharo-dev mailing list