Hi Stef
Yesterday evening I did another update and it worked fine...
It looks like the counter was increased twice in your case. This can
happen if the image is not fresh (the counter was set already) or the
#prepareNewUpdate is executed twice. To prevent this in the future I
changed how the counter is computed (now it does not lazily increase
it anymore but it looks at the latest updateXXX number). The previous
implementation of updateXXX number + 1 does not work anymore because
the new process supports to get back to apply changes another time
after the verification step and hence you do not know if the updateXXX
method was already created or not.
I did a small update (10135) to check and it worked. So I'm curious if
it works reliably for you too now.
Adrian
On Nov 7, 2008, at 16:12 , Stéphane Ducasse wrote:
adrian
could you have a look at the scriptloader because it gets
desynchronised (I had to change the number by hand this morning
again and I followed exactly the process). May be my image counter
was not correct. I think that this counter is
brittle. I would just do what we did before taking the lastest
updateXXX number + 1
Stef
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
