- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Voyage cannot be load

by Esteban Lorenzano

adding: ConfigurationOfGrease>>#stable: spec <symbolicVersion: #'stable'> spec for: #'common' version: '1.1.6'. spec for: #'pharo2.x' version: '1.1.5' makes voyage *and* seaside load fine in pharo2.0. Esteban On 21 Mar 2014, at 13:37, Johan Brichau <johan(a)inceptive.be> wrote: > > >>> If both configurations reference the same Grease version, there will not be a problem. >>> >> Can you do that? I donât have commit rights for those repos. > > No, I am not an author of either projects.... I guess it's best if Magritte references Grease #stable. Though I concur with your remark regarding symbolic versions, it also becomes hell if different projects reference different versions of Grease, just because those were the stable versions when they were created (which is actually the problem here). > > I'm on iPad only right now, so can't help you any further before tonight. > >>> However, this is a more fundamental problem. Metacello first loads 1.1.5 and then loads 1.1.6, which has moved classes between packages, leading to a temporary (i.e. during load) dirty package, leading to the Monticello warning. >>> >>> You can also try to change the metacello loadType to #atomic instead of #linear. >>> Finally, you can also wrap an exception handler around the load statement. >>> >> Yeah, I wanted to do that. But then I changed my workflow to use zero conf scripts and that whole problem handling you loose by using the âmodernâ workflow. > > I also wonder if the Metacello scripting API has a handler for this situation (i.e. suppressing errors) > > >> >> Norbert >> >>> Johan >>> >>> Sent from my iPad >>> >>>> On 21 Mar 2014, at 09:20, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> >>>> What should be changed in order to solve it? >>>> >>>> Norbert >>>> >>>>> Am 20.03.2014 um 17:09 schrieb Johan Brichau <johan(a)inceptive.be>: >>>>> >>>>> Found it: >>>>> >>>>> Magritte3 references Grease1.1.5 explicitly >>>>> MongoTalk references Grease #stable >>>>> >>>>> Looks more like a Metacello bug to me... there clearly is a load conflict and Metacello should decide on a version rather than load them both sequentially. >>>>> But I have not looked any deeper.... >>>>> >>>>> Johan >>>>> >>>>>> On 20 Mar 2014, at 17:02, Johan Brichau <johan(a)inceptive.be> wrote: >>>>>> >>>>>> I can reproduce the problem. >>>>>> For some strange reason, first Grease 1.1.5 is loaded and then 1.1.6 is loaded (in the same metacello load of VoyageMongo). >>>>>> >>>>>> The package becomes dirty because some classes changed from the Pharo20 package in 1.1.5 to the Core package in 1.1.6. >>>>>> Because Metacello first loads the Core package, the Pharo20 package becomes dirty. When the new version of the Pharo20 package is loaded, Monticello raises the warning. >>>>>> >>>>>> I have noticed a similar issue when upgrading versions of Zinc in Pharo1.4 because significant package refactorings occurred. >>>>>> So, this is nothing specific to Grease / Magritte / Seaside / ... >>>>>> >>>>>> I wonder if this can be simply fixed by changing the load type to #atomic. At least, that is how I fix those issues when loading Yesplan in Gemstone. >>>>>> But clean builds work perfectly. And I would want to know why first version 1.1.5 is loaded in this load process. >>>>>> >>>>>> Johan >>>>>> >>>>>>> On 20 Mar 2014, at 16:39, Johan Brichau <johan(a)inceptive.be> wrote: >>>>>>> >>>>>>> Norbert, >>>>>>> >>>>>>> From your screenshot, I see that the Grease package you have loaded in your image is dirty. It is also the package version that gets loaded with Grease 1.1.5. >>>>>>> My first question is: why is it dirty? Can you check that? >>>>>>> >>>>>>> The package version you are loading is the one that is referenced by Grease 1.1.6 >>>>>>> >>>>>>> I just tagged Grease 1.1.6 as #stable yesterday. So that probably triggers this. >>>>>>> >>>>>>> Though I cannot see any reason why this occurs and Seaside 3.1 is loading well here. >>>>>>> >>>>>>> Johan >>>>>>> >>>>>>>> On 20 Mar 2014, at 15:47, Norbert Hartl <norbert(a)hartl.name> wrote: >>>>>>>> >>>>>>>> I encountered a strange problem while loading voyage. It seems the configuration for magritte or grease is strange. If I load voyage from the configuration browser I get the following screen >>>>>>>> >>>>>>>> <Bildschirmfoto 2014-03-20 um 15.43.56.png> >>>>>>>> >>>>>>>> Any ideas? >>>>>>>> >>>>>>>> Norbert >>>> >>>> >>> >> >> >

March 21, 2014

Re: [Pharo-dev] Voyage cannot be load

by Johan Brichau

>> If both configurations reference the same Grease version, there will not be a problem. >> > Can you do that? I donât have commit rights for those repos. No, I am not an author of either projects.... I guess it's best if Magritte references Grease #stable. Though I concur with your remark regarding symbolic versions, it also becomes hell if different projects reference different versions of Grease, just because those were the stable versions when they were created (which is actually the problem here). I'm on iPad only right now, so can't help you any further before tonight. >> However, this is a more fundamental problem. Metacello first loads 1.1.5 and then loads 1.1.6, which has moved classes between packages, leading to a temporary (i.e. during load) dirty package, leading to the Monticello warning. >> >> You can also try to change the metacello loadType to #atomic instead of #linear. >> Finally, you can also wrap an exception handler around the load statement. >> > Yeah, I wanted to do that. But then I changed my workflow to use zero conf scripts and that whole problem handling you loose by using the âmodernâ workflow. I also wonder if the Metacello scripting API has a handler for this situation (i.e. suppressing errors) > > Norbert > >> Johan >> >> Sent from my iPad >> >>> On 21 Mar 2014, at 09:20, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> What should be changed in order to solve it? >>> >>> Norbert >>> >>>> Am 20.03.2014 um 17:09 schrieb Johan Brichau <johan(a)inceptive.be>: >>>> >>>> Found it: >>>> >>>> Magritte3 references Grease1.1.5 explicitly >>>> MongoTalk references Grease #stable >>>> >>>> Looks more like a Metacello bug to me... there clearly is a load conflict and Metacello should decide on a version rather than load them both sequentially. >>>> But I have not looked any deeper.... >>>> >>>> Johan >>>> >>>>> On 20 Mar 2014, at 17:02, Johan Brichau <johan(a)inceptive.be> wrote: >>>>> >>>>> I can reproduce the problem. >>>>> For some strange reason, first Grease 1.1.5 is loaded and then 1.1.6 is loaded (in the same metacello load of VoyageMongo). >>>>> >>>>> The package becomes dirty because some classes changed from the Pharo20 package in 1.1.5 to the Core package in 1.1.6. >>>>> Because Metacello first loads the Core package, the Pharo20 package becomes dirty. When the new version of the Pharo20 package is loaded, Monticello raises the warning. >>>>> >>>>> I have noticed a similar issue when upgrading versions of Zinc in Pharo1.4 because significant package refactorings occurred. >>>>> So, this is nothing specific to Grease / Magritte / Seaside / ... >>>>> >>>>> I wonder if this can be simply fixed by changing the load type to #atomic. At least, that is how I fix those issues when loading Yesplan in Gemstone. >>>>> But clean builds work perfectly. And I would want to know why first version 1.1.5 is loaded in this load process. >>>>> >>>>> Johan >>>>> >>>>>> On 20 Mar 2014, at 16:39, Johan Brichau <johan(a)inceptive.be> wrote: >>>>>> >>>>>> Norbert, >>>>>> >>>>>> From your screenshot, I see that the Grease package you have loaded in your image is dirty. It is also the package version that gets loaded with Grease 1.1.5. >>>>>> My first question is: why is it dirty? Can you check that? >>>>>> >>>>>> The package version you are loading is the one that is referenced by Grease 1.1.6 >>>>>> >>>>>> I just tagged Grease 1.1.6 as #stable yesterday. So that probably triggers this. >>>>>> >>>>>> Though I cannot see any reason why this occurs and Seaside 3.1 is loading well here. >>>>>> >>>>>> Johan >>>>>> >>>>>>> On 20 Mar 2014, at 15:47, Norbert Hartl <norbert(a)hartl.name> wrote: >>>>>>> >>>>>>> I encountered a strange problem while loading voyage. It seems the configuration for magritte or grease is strange. If I load voyage from the configuration browser I get the following screen >>>>>>> >>>>>>> <Bildschirmfoto 2014-03-20 um 15.43.56.png> >>>>>>> >>>>>>> Any ideas? >>>>>>> >>>>>>> Norbert >>> >>> >> > >

March 21, 2014

Re: [Pharo-dev] Voyage cannot be load

by Norbert Hartl

Am 21.03.2014 um 13:07 schrieb Johan Brichau <johan(a)inceptive.be>: > If both configurations reference the same Grease version, there will not be a problem. > Can you do that? I donât have commit rights for those repos. > However, this is a more fundamental problem. Metacello first loads 1.1.5 and then loads 1.1.6, which has moved classes between packages, leading to a temporary (i.e. during load) dirty package, leading to the Monticello warning. > > You can also try to change the metacello loadType to #atomic instead of #linear. > Finally, you can also wrap an exception handler around the load statement. > Yeah, I wanted to do that. But then I changed my workflow to use zero conf scripts and that whole problem handling you loose by using the âmodernâ workflow. Norbert > Johan > > Sent from my iPad > >> On 21 Mar 2014, at 09:20, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> What should be changed in order to solve it? >> >> Norbert >> >>> Am 20.03.2014 um 17:09 schrieb Johan Brichau <johan(a)inceptive.be>: >>> >>> Found it: >>> >>> Magritte3 references Grease1.1.5 explicitly >>> MongoTalk references Grease #stable >>> >>> Looks more like a Metacello bug to me... there clearly is a load conflict and Metacello should decide on a version rather than load them both sequentially. >>> But I have not looked any deeper.... >>> >>> Johan >>> >>>> On 20 Mar 2014, at 17:02, Johan Brichau <johan(a)inceptive.be> wrote: >>>> >>>> I can reproduce the problem. >>>> For some strange reason, first Grease 1.1.5 is loaded and then 1.1.6 is loaded (in the same metacello load of VoyageMongo). >>>> >>>> The package becomes dirty because some classes changed from the Pharo20 package in 1.1.5 to the Core package in 1.1.6. >>>> Because Metacello first loads the Core package, the Pharo20 package becomes dirty. When the new version of the Pharo20 package is loaded, Monticello raises the warning. >>>> >>>> I have noticed a similar issue when upgrading versions of Zinc in Pharo1.4 because significant package refactorings occurred. >>>> So, this is nothing specific to Grease / Magritte / Seaside / ... >>>> >>>> I wonder if this can be simply fixed by changing the load type to #atomic. At least, that is how I fix those issues when loading Yesplan in Gemstone. >>>> But clean builds work perfectly. And I would want to know why first version 1.1.5 is loaded in this load process. >>>> >>>> Johan >>>> >>>>> On 20 Mar 2014, at 16:39, Johan Brichau <johan(a)inceptive.be> wrote: >>>>> >>>>> Norbert, >>>>> >>>>> From your screenshot, I see that the Grease package you have loaded in your image is dirty. It is also the package version that gets loaded with Grease 1.1.5. >>>>> My first question is: why is it dirty? Can you check that? >>>>> >>>>> The package version you are loading is the one that is referenced by Grease 1.1.6 >>>>> >>>>> I just tagged Grease 1.1.6 as #stable yesterday. So that probably triggers this. >>>>> >>>>> Though I cannot see any reason why this occurs and Seaside 3.1 is loading well here. >>>>> >>>>> Johan >>>>> >>>>>> On 20 Mar 2014, at 15:47, Norbert Hartl <norbert(a)hartl.name> wrote: >>>>>> >>>>>> I encountered a strange problem while loading voyage. It seems the configuration for magritte or grease is strange. If I load voyage from the configuration browser I get the following screen >>>>>> >>>>>> <Bildschirmfoto 2014-03-20 um 15.43.56.png> >>>>>> >>>>>> Any ideas? >>>>>> >>>>>> Norbert >> >> >

March 21, 2014

Re: [Pharo-dev] Voyage cannot be load

by Johan Brichau

If both configurations reference the same Grease version, there will not be a problem. However, this is a more fundamental problem. Metacello first loads 1.1.5 and then loads 1.1.6, which has moved classes between packages, leading to a temporary (i.e. during load) dirty package, leading to the Monticello warning. You can also try to change the metacello loadType to #atomic instead of #linear. Finally, you can also wrap an exception handler around the load statement. Johan Sent from my iPad > On 21 Mar 2014, at 09:20, Norbert Hartl <norbert(a)hartl.name> wrote: > > What should be changed in order to solve it? > > Norbert > >> Am 20.03.2014 um 17:09 schrieb Johan Brichau <johan(a)inceptive.be>: >> >> Found it: >> >> Magritte3 references Grease1.1.5 explicitly >> MongoTalk references Grease #stable >> >> Looks more like a Metacello bug to me... there clearly is a load conflict and Metacello should decide on a version rather than load them both sequentially. >> But I have not looked any deeper.... >> >> Johan >> >>> On 20 Mar 2014, at 17:02, Johan Brichau <johan(a)inceptive.be> wrote: >>> >>> I can reproduce the problem. >>> For some strange reason, first Grease 1.1.5 is loaded and then 1.1.6 is loaded (in the same metacello load of VoyageMongo). >>> >>> The package becomes dirty because some classes changed from the Pharo20 package in 1.1.5 to the Core package in 1.1.6. >>> Because Metacello first loads the Core package, the Pharo20 package becomes dirty. When the new version of the Pharo20 package is loaded, Monticello raises the warning. >>> >>> I have noticed a similar issue when upgrading versions of Zinc in Pharo1.4 because significant package refactorings occurred. >>> So, this is nothing specific to Grease / Magritte / Seaside / ... >>> >>> I wonder if this can be simply fixed by changing the load type to #atomic. At least, that is how I fix those issues when loading Yesplan in Gemstone. >>> But clean builds work perfectly. And I would want to know why first version 1.1.5 is loaded in this load process. >>> >>> Johan >>> >>>> On 20 Mar 2014, at 16:39, Johan Brichau <johan(a)inceptive.be> wrote: >>>> >>>> Norbert, >>>> >>>> From your screenshot, I see that the Grease package you have loaded in your image is dirty. It is also the package version that gets loaded with Grease 1.1.5. >>>> My first question is: why is it dirty? Can you check that? >>>> >>>> The package version you are loading is the one that is referenced by Grease 1.1.6 >>>> >>>> I just tagged Grease 1.1.6 as #stable yesterday. So that probably triggers this. >>>> >>>> Though I cannot see any reason why this occurs and Seaside 3.1 is loading well here. >>>> >>>> Johan >>>> >>>>> On 20 Mar 2014, at 15:47, Norbert Hartl <norbert(a)hartl.name> wrote: >>>>> >>>>> I encountered a strange problem while loading voyage. It seems the configuration for magritte or grease is strange. If I load voyage from the configuration browser I get the following screen >>>>> >>>>> <Bildschirmfoto 2014-03-20 um 15.43.56.png> >>>>> >>>>> Any ideas? >>>>> >>>>> Norbert > >

March 21, 2014

Re: [Pharo-dev] Nautilus keyboard behavior

by Ben Coman

March 21, 2014

Re: [Pharo-dev] SmalllineManifestCheckerTest class >> DoIt

by Ben Coman

March 21, 2014

Re: [Pharo-dev] Voyage cannot be load

by Norbert Hartl

What should be changed in order to solve it? Norbert Am 20.03.2014 um 17:09 schrieb Johan Brichau <johan(a)inceptive.be>: > Found it: > > Magritte3 references Grease1.1.5 explicitly > MongoTalk references Grease #stable > > Looks more like a Metacello bug to me... there clearly is a load conflict and Metacello should decide on a version rather than load them both sequentially. > But I have not looked any deeper.... > > Johan > > On 20 Mar 2014, at 17:02, Johan Brichau <johan(a)inceptive.be> wrote: > >> I can reproduce the problem. >> For some strange reason, first Grease 1.1.5 is loaded and then 1.1.6 is loaded (in the same metacello load of VoyageMongo). >> >> The package becomes dirty because some classes changed from the Pharo20 package in 1.1.5 to the Core package in 1.1.6. >> Because Metacello first loads the Core package, the Pharo20 package becomes dirty. When the new version of the Pharo20 package is loaded, Monticello raises the warning. >> >> I have noticed a similar issue when upgrading versions of Zinc in Pharo1.4 because significant package refactorings occurred. >> So, this is nothing specific to Grease / Magritte / Seaside / ... >> >> I wonder if this can be simply fixed by changing the load type to #atomic. At least, that is how I fix those issues when loading Yesplan in Gemstone. >> But clean builds work perfectly. And I would want to know why first version 1.1.5 is loaded in this load process. >> >> Johan >> >> On 20 Mar 2014, at 16:39, Johan Brichau <johan(a)inceptive.be> wrote: >> >>> Norbert, >>> >>> From your screenshot, I see that the Grease package you have loaded in your image is dirty. It is also the package version that gets loaded with Grease 1.1.5. >>> My first question is: why is it dirty? Can you check that? >>> >>> The package version you are loading is the one that is referenced by Grease 1.1.6 >>> >>> I just tagged Grease 1.1.6 as #stable yesterday. So that probably triggers this. >>> >>> Though I cannot see any reason why this occurs and Seaside 3.1 is loading well here. >>> >>> Johan >>> >>> On 20 Mar 2014, at 15:47, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> I encountered a strange problem while loading voyage. It seems the configuration for magritte or grease is strange. If I load voyage from the configuration browser I get the following screen >>>> >>>> <Bildschirmfoto 2014-03-20 um 15.43.56.png> >>>> >>>> Any ideas? >>>> >>>> Norbert >>>> >>> >> > >

March 21, 2014

pharo on Debian

by Ralph Boland

On Debian I can install Squeak vis-a-vis apt-get install squeak. But I cannot do this for Pharo with Debian 7.0. Would it be a good idea to get this to work for Debian 8.0? Ralph Boland

March 21, 2014

Re: [Pharo-dev] Pharo on Debian 7

by phil＠highoctane.be

On my blog http://philippeback.be Works with some tweaks. Le 20 mars 2014 21:49, "jannik laval" <jannik.laval(a)gmail.com> a Ã©crit : > Hi, > > I tried to load Pharo portable on a Debian. It seems to not work. > Anyone can confirm that this is not my config that is broken ? > > Cheers, > > -- > > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://car.mines-douai.fr/ >

March 20, 2014

Re: [Pharo-dev] Pharo on Debian 7

by Sergi Reyner

2014-03-20 21:16 GMT+00:00 jannik laval <jannik.laval(a)gmail.com>: > Ok, any solution ? or deb package ? > > Cheers, > Jannik > I can think of a number of ugly workarounds that defeat the purpose of having a portable package in the first place. Debian was my first choice for my VPS, but I ended up shoving Ubuntu into it after going through the list of available distros and being left with Ubuntu and Gentoo as the only choices with a new enough glibc. I have Gentoo on my desktop but I donÂ´t feel like maintaining it on the server. In the end the real solutions are either: 1- build the Pharo vm against an older glibc (though IÂ´m not sure how, IIUC you need to be able to run Pharo in order to build Pharo), or 2- build a statically linked vm, if possible, in another distro capable of running Pharo (again not sure :D) Cheers, Sergi

March 20, 2014