Oh, well... here is it. http://code.google.com/p/pharo/issues/detail?id=4143 Cheers El dom, 01-05-2011 a las 20:31 +0200, Mariano Martinez Peck escribió:

jejejejej I know an issue that is waiting for you Miguel ;)

On Sun, May 1, 2011 at 7:52 PM, Miguel Cobá <miguel.coba@gmail.com> wrote: Hi Marco,

this is a problem caused by running the update process on a Pharo image. The update process is enabled only on PharoCore image precisely to avoid this problem, that is, that the update process break some package installed (or some overriden method from some package) by updating the method with an uncompatible version.

The problem here is that the class SHParserST80 isn't anymore in the image and is used by OContext of the package OCompetion. You can open a ticket with this problem in the issue tracker in order to not forget it.

Cheers

El dom, 01-05-2011 a las 10:31 -0400, Marco A. Gonzalez escribió: > First, Thank you Miguel and Chris for working to get Magma working with Pharo. > > I ran into the following problem while attempting to get Magma installed into Pharo. After updating the image to version 12351, and I try to type anything into the Workspace window, I get a dialog with the following message: > MessageNotUnderstood: AnObsoleteSHParserST80>>rangesIn:classOrMetaClass:workspace:environment: > > I don't know where to go from there. I'm stuck. What's the best way to report this? Who do I report it to? Is there another one-click that I can use Magma with? > > Here's what to do to reproduce the problem. > > 1. Download Pharo 1.2.1 one-click image (standard VM) from http://www.pharo-project.org/pharo-download/ > NOTE: I wanted to use the one-click because I know how to deploy it on my web host and I don't know how to deploy a non-one-click image. > > 2. In a Workspace window, I evaluated the following: > SystemVersion newVersion: 'Pharo1.2.2a'. >

> (this didn't appear to do anything) > > 3. From the World menu, choose System > Software Update > It took a few minutes, less than 5 minutes I think. Then a dialog window titled "Information" displayed with "6 new update file(s) processed." in the content area. > > 4. Then when I went to install Magma by typing into the Workspace window, the error message appeared. > > > - Marco A.

> > On Apr 27, 2011, at 12:35 PM, Miguel Cobá wrote: > > > Hi all, > > > > I'm glad to announce a new version of ConfigurationOfMagma with support > > for Magma 1.2. This configuration has been tested on > > > > PharoCore 1.1.x > > PharoCore 1.2.x > > > > Thank you very much to Chris Muller who, as always, is working hard to > > keep Magma running on Squeak and Pharo. I used the same versions of > > packages he used in his scripts for Squeak in order to update the > > configuration. > > > > You must download the latest PharoCore image or update a existing one > > before installing Magma, as Magma needs some changes that were applied > > to Pharo post-release and are available in the update stream. > > > > > > Pharo 1.1.x > > ------------ > > > > Download PharoCore 1.1.2 from: > > > > https://gforge.inria.fr/frs/download.php/28341/PharoCore-1.1.2.zip > > > > Update it if necessary and save it. > > > > > > Pharo 1.2.x > > ------------ > > > > You have two options: > > > > 1. Take a released 1.2.1 from: > > > > http://www.pharo-project.org/pharo-download/stable-core > > > > This is actually image update 12345. Evaluate: > > > > SystemVersion newVersion: 'Pharo1.2.2a'. > > > > update the image (it will update to 12350, at this time) and save it. > > > > 2. Take a snapshot of the upcoming 1.2.2 release of Pharo 1.2.x line > > from: > > > > https://gforge.inria.fr/frs/download.php/28436/PharoCore-1.2.2a-12345.zip > > > > update the image (it will update to 12350, at this time) and save it. > > > > > > Install Magma > > -------------- > > > > Ok, now you have an updated image. Load the configuration by evaluating: > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfMagma'; > > load. > > > > And depending on which of client, server or the full suite of Magma do > > you want, evaluate: > > > > - Magma client > > > > ((Smalltalk at: #ConfigurationOfMagma) > > project version: #stable) load: 'Client'. > > > > > > - Magma server > > > > ((Smalltalk at: #ConfigurationOfMagma) > > project version: #stable) load: 'Server'. > > > > - Magma tester > > > > ((Smalltalk at: #ConfigurationOfMagma) > > project version: #stable) load: 'Tester'. > > > > For example, to load the full magma suite evaluate: > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfMagma'; > > load. > > ((Smalltalk at: #ConfigurationOfMagma) > > project version: #stable) load: 'Tester'. > > > > This will load client, server and test of Magma. > > > > > > Running tests > > ------------- > > To run the tests evaluate: > > > > MagmaTestCase allowWriteBarrier: false. > > MagmaTestCase fullSuite maDebug. > > > > > > Stable versions > > --------------- > > > > This release of ConfigurationOfMagma includes support for Metacello's > > symbolic versions. Currently the #stable version of Magma is configured > > like this: > > > > Pharo version #stable version > > ------------- --------------- > > Pharo 1.1.x 1.2 > > Pharo 1.2.x 1.2 > > Pharo 1.3.x 1.2 > > > > That is, Magma 1.2 is the #stable version for Pharo 1.1, Pharo 1.2 and > > Pharo 1.3. > > > > Known issues > > -------------- > > > > Magma 1.2 loads correctly and appears to work for the basic things > > (create a repo, add data, commit, etc) in PharoCore 1.3 and Pharo 1.3, > > but the full suite hasn't ran correctly in the current unstable Pharo. > > So use Magma 1.2 on Pharo 1.3 on your own risk and not for production > > yet. When the issues (including the Transcript revert that should happen > > in Pharo soon) are addressed, a new announce will be made for Magma on > > Pharo 1.3 > > > > Any feedback welcome. > > > > Enjoy. > > -- > > Miguel Cobá > > http://twitter.com/MiguelCobaMtz > > http://miguel.leugim.com.mx > > > > > > > > > > > > _______________________________________________ > > Magma mailing list > > Magma@lists.squeakfoundation.org > > http://lists.squeakfoundation.org/mailman/listinfo/magma > > > > >

-- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

_______________________________________________ Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma

-- Mariano http://marianopeck.wordpress.com

-- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

oh! I'll give it a try tomorrow night :) Cheers El dom, 01-05-2011 a las 21:08 +0200, Mariano Martinez Peck escribió:

You are not that lucky ;) hehehe I was talking about this one: http://code.google.com/p/pharo/issues/detail?id=4103 :)

Thanks anyway

On Sun, May 1, 2011 at 9:03 PM, Miguel Cobá <miguel.coba@gmail.com> wrote: Oh, well... here is it.

http://code.google.com/p/pharo/issues/detail?id=4143

Cheers

El dom, 01-05-2011 a las 20:31 +0200, Mariano Martinez Peck escribió:

> jejejejej I know an issue that is waiting for you Miguel ;) > > On Sun, May 1, 2011 at 7:52 PM, Miguel Cobá <miguel.coba@gmail.com> > wrote: > Hi Marco, > > this is a problem caused by running the update process on a > Pharo image. > The update process is enabled only on PharoCore image > precisely to avoid > this problem, that is, that the update process break some > package > installed (or some overriden method from some package) by > updating the > method with an uncompatible version. > > The problem here is that the class SHParserST80 isn't anymore > in the > image and is used by OContext of the package OCompetion. You > can open a > ticket with this problem in the issue tracker in order to not > forget it. > > > Cheers > > El dom, 01-05-2011 a las 10:31 -0400, Marco A. Gonzalez > escribió: > > First, Thank you Miguel and Chris for working to get Magma > working with Pharo. > > > > I ran into the following problem while attempting to get > Magma installed into Pharo. After updating the image to > version 12351, and I try to type anything into the Workspace > window, I get a dialog with the following message: > > MessageNotUnderstood: > AnObsoleteSHParserST80>>rangesIn:classOrMetaClass:workspace:environment: > > > > I don't know where to go from there. I'm stuck. What's the > best way to report this? Who do I report it to? Is there > another one-click that I can use Magma with? > > > > Here's what to do to reproduce the problem. > > > > 1. Download Pharo 1.2.1 one-click image (standard VM) from > http://www.pharo-project.org/pharo-download/ > > NOTE: I wanted to use the one-click because I know how to > deploy it on my web host and I don't know how to deploy a > non-one-click image. > > > > 2. In a Workspace window, I evaluated the following: > > SystemVersion newVersion: 'Pharo1.2.2a'. > > > > > (this didn't appear to do anything) > > > > 3. From the World menu, choose System > Software Update > > It took a few minutes, less than 5 minutes I think. > Then a dialog window titled "Information" displayed with "6 > new update file(s) processed." in the content area. > > > > 4. Then when I went to install Magma by typing into the > Workspace window, the error message appeared. > > > > > > - Marco A. > > > > > On Apr 27, 2011, at 12:35 PM, Miguel Cobá wrote: > > > > > Hi all, > > > > > > I'm glad to announce a new version of ConfigurationOfMagma > with support > > > for Magma 1.2. This configuration has been tested on > > > > > > PharoCore 1.1.x > > > PharoCore 1.2.x > > > > > > Thank you very much to Chris Muller who, as always, is > working hard to > > > keep Magma running on Squeak and Pharo. I used the same > versions of > > > packages he used in his scripts for Squeak in order to > update the > > > configuration. > > > > > > You must download the latest PharoCore image or update a > existing one > > > before installing Magma, as Magma needs some changes that > were applied > > > to Pharo post-release and are available in the update > stream. > > > > > > > > > Pharo 1.1.x > > > ------------ > > > > > > Download PharoCore 1.1.2 from: > > > > > > > https://gforge.inria.fr/frs/download.php/28341/PharoCore-1.1.2.zip > > > > > > Update it if necessary and save it. > > > > > > > > > Pharo 1.2.x > > > ------------ > > > > > > You have two options: > > > > > > 1. Take a released 1.2.1 from: > > > > > > http://www.pharo-project.org/pharo-download/stable-core > > > > > > This is actually image update 12345. Evaluate: > > > > > > SystemVersion newVersion: 'Pharo1.2.2a'. > > > > > > update the image (it will update to 12350, at this time) > and save it. > > > > > > 2. Take a snapshot of the upcoming 1.2.2 release of Pharo > 1.2.x line > > > from: > > > > > > > https://gforge.inria.fr/frs/download.php/28436/PharoCore-1.2.2a-12345.zip > > > > > > update the image (it will update to 12350, at this time) > and save it. > > > > > > > > > Install Magma > > > -------------- > > > > > > Ok, now you have an updated image. Load the configuration > by evaluating: > > > > > > Gofer new > > > squeaksource: 'MetacelloRepository'; > > > package: 'ConfigurationOfMagma'; > > > load. > > > > > > And depending on which of client, server or the full suite > of Magma do > > > you want, evaluate: > > > > > > - Magma client > > > > > > ((Smalltalk at: #ConfigurationOfMagma) > > > project version: #stable) load: 'Client'. > > > > > > > > > - Magma server > > > > > > ((Smalltalk at: #ConfigurationOfMagma) > > > project version: #stable) load: 'Server'. > > > > > > - Magma tester > > > > > > ((Smalltalk at: #ConfigurationOfMagma) > > > project version: #stable) load: 'Tester'. > > > > > > For example, to load the full magma suite evaluate: > > > > > > Gofer new > > > squeaksource: 'MetacelloRepository'; > > > package: 'ConfigurationOfMagma'; > > > load. > > > ((Smalltalk at: #ConfigurationOfMagma) > > > project version: #stable) load: 'Tester'. > > > > > > This will load client, server and test of Magma. > > > > > > > > > Running tests > > > ------------- > > > To run the tests evaluate: > > > > > > MagmaTestCase allowWriteBarrier: false. > > > MagmaTestCase fullSuite maDebug. > > > > > > > > > Stable versions > > > --------------- > > > > > > This release of ConfigurationOfMagma includes support for > Metacello's > > > symbolic versions. Currently the #stable version of Magma > is configured > > > like this: > > > > > > Pharo version #stable version > > > ------------- --------------- > > > Pharo 1.1.x 1.2 > > > Pharo 1.2.x 1.2 > > > Pharo 1.3.x 1.2 > > > > > > That is, Magma 1.2 is the #stable version for Pharo 1.1, > Pharo 1.2 and > > > Pharo 1.3. > > > > > > Known issues > > > -------------- > > > > > > Magma 1.2 loads correctly and appears to work for the > basic things > > > (create a repo, add data, commit, etc) in PharoCore 1.3 > and Pharo 1.3, > > > but the full suite hasn't ran correctly in the current > unstable Pharo. > > > So use Magma 1.2 on Pharo 1.3 on your own risk and not for > production > > > yet. When the issues (including the Transcript revert that > should happen > > > in Pharo soon) are addressed, a new announce will be made > for Magma on > > > Pharo 1.3 > > > > > > Any feedback welcome. > > > > > > Enjoy. > > > -- > > > Miguel Cobá > > > http://twitter.com/MiguelCobaMtz > > > http://miguel.leugim.com.mx > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Magma mailing list > > > Magma@lists.squeakfoundation.org > > > http://lists.squeakfoundation.org/mailman/listinfo/magma > > > > > > > > > > > > -- > Miguel Cobá > http://twitter.com/MiguelCobaMtz > http://miguel.leugim.com.mx > > > > _______________________________________________ > Magma mailing list > Magma@lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/magma > > > > > -- > Mariano > http://marianopeck.wordpress.com >

--

Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

-- Mariano http://marianopeck.wordpress.com

-- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx