ChangeLOG: ---------- --> update warning message: self inform: 'Updates after #10263 are for closure-enable Pharo. You need a 4.0 VM and continue updating from the #10262 closure image. Updating non-closure images will not work. Visit https://gforge.inria.fr/frs/?group_id=1299 for downloading the closure image'.! -- Marcus Denker -- [hidden email] http://www.marcusdenker.de _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Please also inform with a link to non-mac closure VM (or put some on
inria forge). Cheers 2009/4/2 Marcus Denker <[hidden email]>: > > ChangeLOG: > ---------- > > --> update warning message: > > self inform: 'Updates after #10263 are for closure-enable Pharo. You > need a 4.0 VM and continue updating from the #10262 closure image. > Updating non-closure images will not work. Visit https://gforge.inria.fr/frs/?group_id=1299 > for downloading the closure image'.! > > > > > -- > Marcus Denker -- [hidden email] > http://www.marcusdenker.de > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
On Thu, Apr 2, 2009 at 10:30 AM, Nicolas Cellier
<[hidden email]> wrote: > Please also inform with a link to non-mac closure VM (or put some on > inria forge). Everything is linked in the download page: http://code.google.com/p/pharo/wiki/Downloads?tm=2 -- Damien Cassou http://damiencassou.seasidehosting.st _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Thanks Damien,
that's certainly clear for U, not for me. Is it the same that main Pharo page http://www.pharo-project.org/download ? How do I know if http://www.pharo-project.org/download provides closure ready VM ? Why is there a mac VM on https://gforge.inria.fr/frs/?group_id=1299 and only a mac VM ? Sorry, all this looks messy to me (i'm not in Pharo bath for about 4 month). I see things like a newb: 1) Marcus information tells I need a closure VM but direct me to a page without unix VM. 2) main pharo download page does not tell whether VM are closure ready or not 3) I'm stuck... (pretend I don't want to scan mailing list archive to find your usefull link) That's why I ask information to be gathered in a single place. 1) complete Marcus warning message 2) update http://www.pharo-project.org/download Nicolas 2009/4/2 Damien Cassou <[hidden email]>: > On Thu, Apr 2, 2009 at 10:30 AM, Nicolas Cellier > <[hidden email]> wrote: >> Please also inform with a link to non-mac closure VM (or put some on >> inria forge). > > Everything is linked in the download page: > > http://code.google.com/p/pharo/wiki/Downloads?tm=2 > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Nicola, you are right, its a mess! ;)
We have three places: the web page, the wiki and the GForge. A piece of information or a file should be at one and only one location. - GForge is only for file downloads. All files should be linked directly from the wiki or web page (because its GUI is so terrible) - the wiki is for Pharo *developers* - the web page is for *end users* Hence, the links to the VMs have to live on http://www.pharo-project.org/download and http://code.google.com/p/pharo/wiki/Downloads should only link to the former page and have no other content. I'll try to clean this up soon. Adrian On Apr 2, 2009, at 10:49 , Nicolas Cellier wrote: > Thanks Damien, > that's certainly clear for U, not for me. > Is it the same that main Pharo page http://www.pharo-project.org/download > ? > How do I know if http://www.pharo-project.org/download provides > closure ready VM ? > Why is there a mac VM on https://gforge.inria.fr/frs/?group_id=1299 > and only a mac VM ? > Sorry, all this looks messy to me (i'm not in Pharo bath for about 4 > month). > > I see things like a newb: > 1) Marcus information tells I need a closure VM but direct me to a > page without unix VM. > 2) main pharo download page does not tell whether VM are closure > ready or not > 3) I'm stuck... (pretend I don't want to scan mailing list archive to > find your usefull link) > > That's why I ask information to be gathered in a single place. > 1) complete Marcus warning message > 2) update http://www.pharo-project.org/download > > Nicolas > > 2009/4/2 Damien Cassou <[hidden email]>: >> On Thu, Apr 2, 2009 at 10:30 AM, Nicolas Cellier >> <[hidden email]> wrote: >>> Please also inform with a link to non-mac closure VM (or put some on >>> inria forge). >> >> Everything is linked in the download page: >> >> http://code.google.com/p/pharo/wiki/Downloads?tm=2 >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
On Thu, Apr 2, 2009 at 11:11 AM, Adrian Lienhard <[hidden email]> wrote:
> Hence, the links to the VMs have to live on http://www.pharo-project.org/download > and http://code.google.com/p/pharo/wiki/Downloads should only link > to the former page and have no other content. > > I'll try to clean this up soon. The problem with this approach is that most people can't modify pharo-project.org. I update the wiki on code.google.com twice a month at least. -- Damien Cassou http://damiencassou.seasidehosting.st _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
We cannot open access to the web page for everybody. What we need is a
small group of people that is responsible for the web site contents. So if you like to help I'm happy to send you a login. But forking the content on the wiki is no option. Cheers, Adrian On Apr 2, 2009, at 11:44 , Damien Cassou wrote: > On Thu, Apr 2, 2009 at 11:11 AM, Adrian Lienhard <[hidden email]> > wrote: >> Hence, the links to the VMs have to live on http://www.pharo-project.org/download >> and http://code.google.com/p/pharo/wiki/Downloads should only link >> to the former page and have no other content. >> >> I'll try to clean this up soon. > > The problem with this approach is that most people can't modify > pharo-project.org. I update the wiki on code.google.com twice a month > at least. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
On Thu, Apr 2, 2009 at 12:00 PM, Adrian Lienhard <[hidden email]> wrote:
> So if you like to help I'm happy to send you a login. But forking the > content on the wiki is no option. I agree, please give me a login and I will move the content. -- Damien Cassou http://damiencassou.seasidehosting.st _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Nicolas Cellier
On Thu, Apr 2, 2009 at 10:49 AM, Nicolas Cellier
<[hidden email]> wrote: > update http://www.pharo-project.org/download What do you think now? -- Damien Cassou http://damiencassou.seasidehosting.st _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Thank, it is far better yet.
Maybe to make it a bit less cryptic: "all VMs have closure support required for latest images" ... a hard work maintaining up to date site for a project moving so fast... 2009/4/2 Damien Cassou <[hidden email]>: > On Thu, Apr 2, 2009 at 10:49 AM, Nicolas Cellier > <[hidden email]> wrote: >> update http://www.pharo-project.org/download > > What do you think now? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
On Thu, Apr 2, 2009 at 6:03 PM, Nicolas Cellier
<[hidden email]> wrote: > Maybe to make it a bit less cryptic: > > "all VMs have closure support required for latest images" done -- Damien Cassou http://damiencassou.seasidehosting.st _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Damien Cassou
At quick glance (sorry if I missed the obvious), I am glad to see us promoting Pharo-dev and providing alernate access to the core. Pharo-web is obscured??? If we plan treat that as Pharo-dev and then "run this script" that seems to work last I did it, then that's fine too. If Pharo-web is still to be featured, it deserves a place on the page too.
Bill -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Damien Cassou Sent: Thursday, April 02, 2009 10:54 AM To: [hidden email] Subject: Re: [Pharo-project] [update] #10263 On Thu, Apr 2, 2009 at 10:49 AM, Nicolas Cellier <[hidden email]> wrote: > update http://www.pharo-project.org/download What do you think now? -- Damien Cassou http://damiencassou.seasidehosting.st _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Marcus Denker-3
> self inform: 'Updates after #10263 are for closure-enable Pharo. You
> need a 4.0 VM and continue updating from the #10262 closure image. > Updating non-closure images will not work. Visit https://gforge.inria.fr/frs/?group_id=1299 > for downloading the closure image'.! Sorry, I'm a come-lately to this. How to I get to (and past) 10263? I downloaded Pharo0.1Core-10262cl from INRIA, but on the 4.0 vm I get 17 failures and 51 errors with all-tests. ../Dave _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
for the moment 10263 is the last update :)
for the tests I imagine that they are normal. but we need help to improve the tests and for example avoid to have test popping up menu. stef On Apr 2, 2009, at 11:42 PM, [hidden email] wrote: >> self inform: 'Updates after #10263 are for closure-enable Pharo. You >> need a 4.0 VM and continue updating from the #10262 closure image. >> Updating non-closure images will not work. Visit https://gforge.inria.fr/frs/?group_id=1299 >> for downloading the closure image'.! > > Sorry, I'm a come-lately to this. How to I get to (and past) 10263? > > I downloaded Pharo0.1Core-10262cl from INRIA, but on the 4.0 vm I > get 17 > failures and 51 errors with all-tests. > > ../Dave > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Nicolas Cellier
On 02.04.2009, at 10:49, Nicolas Cellier wrote: > Thanks Damien, > that's certainly clear for U, not for me. > Is it the same that main Pharo page http://www.pharo-project.org/download > ? > How do I know if http://www.pharo-project.org/download provides > closure ready VM ? > Why is there a mac VM on https://gforge.inria.fr/frs/?group_id=1299 > and only a mac VM ? > Sorry, all this looks messy to me (i'm not in Pharo bath for about 4 > month). > > I see things like a newb: > 1) Marcus information tells I need a closure VM but direct me to a > page without unix VM. > 2) main pharo download page does not tell whether VM are closure > ready or not > 3) I'm stuck... (pretend I don't want to scan mailing list archive to > find your usefull link) > > That's why I ask information to be gathered in a single place. > 1) complete Marcus warning message > 2) update http://www.pharo-project.org/download > I now changed it to: Updates after #10263 are for closure-enable Pharo. You need a current VM and continue updating from the #10262 closure image. Updating non- closure images will not work. Visit https://gforge.inria.fr/frs/?group_id=1299 for downloading the closure image, and http://pharo-project.org/download for the VM. I suggest we don't lose too much time with this... this is not a message for end-users, nor for developers, as everyone will load an image soon that is already updated... Marcus > Nicolas > > 2009/4/2 Damien Cassou <[hidden email]>: >> On Thu, Apr 2, 2009 at 10:30 AM, Nicolas Cellier >> <[hidden email]> wrote: >>> Please also inform with a link to non-mac closure VM (or put some on >>> inria forge). >> >> Everything is linked in the download page: >> >> http://code.google.com/p/pharo/wiki/Downloads?tm=2 >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- [hidden email] http://www.marcusdenker.de _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Stéphane Ducasse
On Apr 3, 2009, at 00:04 , Stéphane Ducasse wrote: > for the moment 10263 is the last update :) > for the tests I imagine that they are normal. Hm, seems not normal... without closures (10263): 2929 run, 2909 passes, 2 expected failures, 12 failures, 6 errors, 0 unexpected passes with closures (10262cl): 2970 run, 2900 passes, 2 expected failures, 17 failures, 51 errors, 0 unexpected passes Not sure though, if the 10262cl image I downloaded from GForge already has the fixes in http://code.google.com/p/pharo/issues/detail?id=685 ? (sorry, was a bit offline from Pharo the last week). A couple of errors exist simply because BlockClosure is expected to understand messages from BlockContext. Fixing the few obvious ones (I atteched a cs to isse #685) brings me down to: 2970 run, 2923 passes, 2 expected failures, 20 failures, 25 errors, 0 unexpected passes But still, not normal. A few couple other errors are from BlockContextTest. Shall this one be removed or are these tests still valuable if we adapt them? Another question: did somebody check the methods that the closure changeset modified for conflicts with fixes that we applied in Pharo? I mean, if the closures implementation touched one of these methods, our changes/fixes would be gone. Cheers, Adrian > > but we need help to improve the tests and for example avoid to have > test popping up menu. > > stef > > On Apr 2, 2009, at 11:42 PM, [hidden email] wrote: > >>> self inform: 'Updates after #10263 are for closure-enable Pharo. You >>> need a 4.0 VM and continue updating from the #10262 closure image. >>> Updating non-closure images will not work. Visit https://gforge.inria.fr/frs/?group_id=1299 >>> for downloading the closure image'.! >> >> Sorry, I'm a come-lately to this. How to I get to (and past) 10263? >> >> I downloaded Pharo0.1Core-10262cl from INRIA, but on the 4.0 vm I >> get 17 >> failures and 51 errors with all-tests. >> >> ../Dave >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
On Apr 3, 2009, at 6:39 PM, Adrian Lienhard wrote: > > On Apr 3, 2009, at 00:04 , Stéphane Ducasse wrote: > >> for the moment 10263 is the last update :) >> for the tests I imagine that they are normal. > > Hm, seems not normal... > > without closures (10263): 2929 run, 2909 passes, 2 expected failures, > 12 failures, 6 errors, 0 unexpected passes > with closures (10262cl): 2970 run, 2900 passes, 2 expected failures, > 17 failures, 51 errors, 0 unexpected passes > > Not sure though, if the 10262cl image I downloaded from GForge already > has the fixes in http://code.google.com/p/pharo/issues/detail?id=685 ? > (sorry, was a bit offline from Pharo the last week). No. None of them are in the release. > > > A couple of errors exist simply because BlockClosure is expected to > understand messages from BlockContext. Fixing the few obvious ones (I > atteched a cs to isse #685) brings me down to: > > 2970 run, 2923 passes, 2 expected failures, 20 failures, 25 errors, 0 > unexpected passes > > But still, not normal. > > A few couple other errors are from BlockContextTest. Shall this one be > removed or are these tests still valuable if we adapt them? > > Another question: did somebody check the methods that the closure > changeset modified for conflicts with fixes that we applied in Pharo? Somehow since this is difficult to know exactly. > > I mean, if the closures implementation touched one of these methods, > our changes/fixes would be gone. > > Cheers, > Adrian > >> >> but we need help to improve the tests and for example avoid to have >> test popping up menu. >> >> stef >> >> On Apr 2, 2009, at 11:42 PM, [hidden email] wrote: >> >>>> self inform: 'Updates after #10263 are for closure-enable Pharo. >>>> You >>>> need a 4.0 VM and continue updating from the #10262 closure image. >>>> Updating non-closure images will not work. Visit https://gforge.inria.fr/frs/?group_id=1299 >>>> for downloading the closure image'.! >>> >>> Sorry, I'm a come-lately to this. How to I get to (and past) 10263? >>> >>> I downloaded Pharo0.1Core-10262cl from INRIA, but on the 4.0 vm I >>> get 17 >>> failures and 51 errors with all-tests. >>> >>> ../Dave >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Free forum by Nabble | Edit this page |