issue 794

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

issue 794

SeanTAllen
Using 64 bit debian lenny, I'm experiencing issue 794.

The issue was closed but there doesn't seem to be any definitive how it was resolved for others.
Can someone give me an idea of what the fix is?

I see one where upgrading to an unstable version of debian worked but I'm try to avoid that.


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: issue 794

Damien Cassou
2009/12/7 Sean Allen <[hidden email]>:
> Using 64 bit debian lenny, I'm experiencing issue 794.
>
> The issue was closed but there doesn't seem to be any definitive how it was resolved for others.
> Can someone give me an idea of what the fix is?
>
> I see one where upgrading to an unstable version of debian worked but I'm try to avoid that.

I confirm that upgrading works but I don't know the other solutions.

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: issue 794

Miguel Cobá
In reply to this post by SeanTAllen
El lun, 07-12-2009 a las 01:34 -0500, Sean Allen escribió:
> Using 64 bit debian lenny, I'm experiencing issue 794.
>
> The issue was closed but there doesn't seem to be any definitive how
> it was resolved for others.
> Can someone give me an idea of what the fix is?
>
> I see one where upgrading to an unstable version of debian worked but
> I'm try to avoid that.

I appears to me that the issue was never solved on Debian stable (lenny
at the time) only worked for me after upgrading to squeeze.
In my case I don't have any 64 bit server with lenny in production, only
32 bit servers, so the network issue doesn't affected me.
Hopefully when I use 64 bit servers in production I will use Squeeze
(that should be stable by then) and the problem will never hit me.

Anyway, as I said, the problem was never correctly addressed or even the
main cause discovered. Potentially, when the Pharo 1.0 get released, it
will hit several users using Lenny 64 bit.
Maybe this should be confirmed and the tickets opened again.

Cheers
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
Miguel Cobá
http://miguel.leugim.com.mx


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project