Hello,
I'm getting curious to see the full history of changes so what I'm now trying to do is to update 3.8-6665-full image to 3.9 alpha. I did a little magic incantation to set the version, and doing updates. As 6675InstallPkgsWarning-dew.cs warns, it *really* takes long time... I'm on it for a few hours. It could be because of the slow network connection I have, but does anybody have an idea about how long should it take, in a ballpark figure, with a one-year old laptop computer? -- Yoshiki |
At Thu, 18 Sep 2008 13:04:56 -0700,
Yoshiki Ohshima wrote: > > Hello, > > I'm getting curious to see the full history of changes so what I'm > now trying to do is to update 3.8-6665-full image to 3.9 alpha. I did a > little magic incantation to set the version, and doing updates. > > As 6675InstallPkgsWarning-dew.cs warns, it *really* takes long > time... I'm on it for a few hours. It could be because of the slow > network connection I have, but does anybody have an idea about how > long should it take, in a ballpark figure, with a one-year old laptop > computer? 6675InstallPkgsWarning-dew.cs took about 6 hours with some dialog clicks here and there. And in parallel, I was doing from 3.9-7067 to 3.10.2 and it took about 5 hours. And, the first one is still at 6695loadScriptLoader19-stephaneducasse.cs. So my guesstimate is that it is going to take about 24 hours to 48 hours for going from 3.8-6665 to the latest. (From 3.8-6665 to the latest Etoys, it would be probably 30 minutes or such.) -- Yoshiki |
Yoshiki Ohshima wrote:
> At Thu, 18 Sep 2008 13:04:56 -0700, > Yoshiki Ohshima wrote: >> Hello, >> >> I'm getting curious to see the full history of changes so what I'm >> now trying to do is to update 3.8-6665-full image to 3.9 alpha. I did a >> little magic incantation to set the version, and doing updates. >> >> As 6675InstallPkgsWarning-dew.cs warns, it *really* takes long >> time... I'm on it for a few hours. It could be because of the slow >> network connection I have, but does anybody have an idea about how >> long should it take, in a ballpark figure, with a one-year old laptop >> computer? Maybe someone has a solution to the problem: at least from my Sophie building experience a large part is weak dictionary stuff when loading a large number of Monticello packages at once (e.g. through config maps). Michael |
At Fri, 19 Sep 2008 08:33:41 -0700,
Michael Rueger wrote: > > Yoshiki Ohshima wrote: > > At Thu, 18 Sep 2008 13:04:56 -0700, > > Yoshiki Ohshima wrote: > >> Hello, > >> > >> I'm getting curious to see the full history of changes so what I'm > >> now trying to do is to update 3.8-6665-full image to 3.9 alpha. I did a > >> little magic incantation to set the version, and doing updates. > >> > >> As 6675InstallPkgsWarning-dew.cs warns, it *really* takes long > >> time... I'm on it for a few hours. It could be because of the slow > >> network connection I have, but does anybody have an idea about how > >> long should it take, in a ballpark figure, with a one-year old laptop > >> computer? > > Maybe someone has a solution to the problem: > > at least from my Sophie building experience a large part is weak > dictionary stuff when loading a large number of Monticello packages at > once (e.g. through config maps). I ran it overnight and got errors. And realized that I should have started from 3.8-6665-basic, not 3.8-6665-full. -basic can pass 6675InstallPkgsWarning-dew in half an hour or so. And Squeak3.9b-7053.changes (right before the condensing for V39) is a "proper super .changes" of Squeak3.8-6665-basic.changes (of course not Squeak3.8-6665-full.changes; that is why I wanted to make my own .changes file with everything), so I really don't have to do the update. -- Yoshiki |
Free forum by Nabble | Edit this page |