I've updated the issue with an error report and comments posted to the mailing list.
Adrian On Mar 1, 2010, at 13:26 , Schwab,Wilhelm K wrote: > Do the comments in the tracker reflect "everything" that has been tried and > not worked? That would seem to be an important list. I'll take a look at it > later today. I saw mention that all is well in the core; is that true? > > When I last looked into this, there were still paths to ipv6 primitives not > protected by a check on #useOldNetwork - given how the old network flag was > set at the time, that was a sure sign of trouble. Gotta run. > > Bill > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Adrian > Lienhard > Sent: Monday, March 01, 2010 7:22 AM > To: Pharo-project Development > Subject: [Pharo-project] Call for fixing the network problem > > To release Pharo 1.0, we need to fix the network problem: > > http://code.google.com/p/pharo/issues/detail?id=1884 > > Anyone volunteers to help? I can allocate some time but would welcome if > somebody would team up to get rid of this issue. > > Cheers, > Adrian > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > 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 _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
