I'm puzzled. I try to install Seaside (& squeak :) on my freebsd-current box. The squeak port installs the 3.5 image and 3.4-1 machine. (This is the first time I installed squeak. My older experiences with smalltalk are well over 10 years old)
I choose open-package browser, the system installs SqueaqMap, the package loader pops up - everything fine sofar.
I can install Mcinstaller, sarinstaller for 3.4 (found out I seem to need this to install komhttpserver) but komhttpserver, while trying to install dvs. stops with:
Installation of package release failed, message follows:
named:
I can't get over this (installing DVS directly does not help)
Any ideas, hints, tips, pointers to documentation so I might understand the package system better. (I tried various different ways to install allready, no use)
Thanks, Mathias
My guess is that you are trying to install the new Comanche and it may well not work with a 3.5 image as I recall. You could try using kom5 instead, or (probably the better bet) move up to using a 3.6 image from www.squeak.org.
You should be able to just download the image and start using it - no need to install it with a package or anything.
Julian
Mathias Picker wrote:
I'm puzzled. I try to install Seaside (& squeak :) on my freebsd-current box. The squeak port installs the 3.5 image and 3.4-1 machine. (This is the first time I installed squeak. My older experiences with smalltalk are well over 10 years old)
I choose open-package browser, the system installs SqueaqMap, the package loader pops up - everything fine sofar.
I can install Mcinstaller, sarinstaller for 3.4 (found out I seem to need this to install komhttpserver) but komhttpserver, while trying to install dvs. stops with:
Installation of package release failed, message follows:
named:
I can't get over this (installing DVS directly does not help)
Any ideas, hints, tips, pointers to documentation so I might understand the package system better. (I tried various different ways to install allready, no use)
Thanks, Mathias
On Feb 10, 2004, at 2:32 PM, Mathias Picker wrote:
I'm puzzled. I try to install Seaside (& squeak :) on my freebsd-current box. The squeak port installs the 3.5 image and 3.4-1 machine. (This is the first time I installed squeak. My older experiences with smalltalk are well over 10 years old)
3.5 is a relatively old image version: 3.6 is the last stable release, 3.7 is the development release. So it doesn't entirely surprise me that you're having trouble - can you try with a 3.6 or 3.7 image and report back?
Yes, thanks!!
Avi Bryant wrote:
On Feb 10, 2004, at 2:32 PM, Mathias Picker wrote:
I'm puzzled. I try to install Seaside (& squeak :) on my freebsd-current box. The squeak port installs the 3.5 image and 3.4-1 machine. (This is the first time I installed squeak. My older experiences with smalltalk are well over 10 years old)
3.5 is a relatively old image version: 3.6 is the last stable release, 3.7 is the development release. So it doesn't entirely surprise me that you're having trouble - can you try with a 3.6 or 3.7 image and report back?
Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/listinfo/seaside
i got an error 'Attempt to evaluate a block that is already being evaluated.' ... BlockContext(Object)>>error: BlockContext>>valueWithArguments: BlockContext>>value WAActionCallback>>trigger WACallbackStore>>processRequest: ...
this was an email from my production server so i don't know any details and i can't reproduce it on my computer either. any ideas where/how/why this could be happening? i'm using seaside 102
thanks, rado
On Feb 13, 2004, at 11:22 AM, radoslav hodnicak wrote:
i got an error 'Attempt to evaluate a block that is already being evaluated.' ... BlockContext(Object)>>error: BlockContext>>valueWithArguments: BlockContext>>value WAActionCallback>>trigger WACallbackStore>>processRequest: ...
this was an email from my production server so i don't know any details and i can't reproduce it on my computer either. any ideas where/how/why this could be happening? i'm using seaside 102
Hm. I've never seen that happen on a callback before. What it means is that you got partway through evaluating that block at some point and then had some very abnormal termination so that the stack didn't get cleaned up. Then when you try to evaluate the same block again (must be from backtracking) the system is unhappy. But exactly what that abnormal termination could have been I don't know - I usually only run into this in the bowels of exception handling code. The workaround I use there is to use a MessageSend instead of a block.
At one point I think it might have been possible to get this error if you did a #call: from inside the handler block of #on:do:. I know I fixed that but I'm not sure by what version (I would think 102 would have the fix). Do you ever do that?
You don't have any more stack info (like, that would show you what the home method of that BlockContext is)?
On Fri, 13 Feb 2004, Avi Bryant wrote:
At one point I think it might have been possible to get this error if you did a #call: from inside the handler block of #on:do:. I know I fixed that but I'm not sure by what version (I would think 102 would have the fix). Do you ever do that?
no i don't do that
You don't have any more stack info (like, that would show you what the home method of that BlockContext is)?
sadly, no. there are several action blocks in the home method (think renderActionsOn: from the SM example) so i don't know which one was it. well let's hope it never happens again. i swear this one user corrupts reality - all errors i've seen so far in my system were caused by him :-)
rado
seaside@lists.squeakfoundation.org