Hi there,
I am trying to include the Zinc project on Github in our Metacello configuration. However, I'm getting errors probably because I'm not sure how to include a project reference to github inside my metacello conf. For example: spec project: 'ZincHTTP' with:: [ spec loads: 'Core'; version: #stable; file: 'BaselineOfZinc'; repository: 'github://glassdb/zinc:gemstone2.4/repository']. Are there existing configurations that I can take a look at to know how to reference a project on github? thanks Johan
-- You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
I managed to get a little further and maybe the problem is more related to the fact that I need a different project spec for Pharo and Gemstone.
In the Pharo section, I can use the 'traditional' project spec: spec project: 'ZincHTTP' overrides: [ spec className: 'ConfigurationOfZincHTTPComponents'; versionString: '1.7'; file: 'ConfigurationOfZincHTTPComponents'; loads: 'Core'; repository: 'http://www.squeaksource.com/ZincHTTPComponents']. In the Gemstone section, I now include the following project spec to load the one from github: "Zinc HTTP" spec baseline: 'ZincHTTP' with: [ spec className: 'BaselineOfZinc'; loads: 'Core'; repository: 'github://glassdb/zinc:gemstone2.4/repository']. ] In the common section, I merely mention: spec project: 'ZincHTTP'. Because otherwise, I get a 'name not found' when trying to load. However, this also leads to an error trying to load: No method was found for the selector #'ensureLoadUsing:' when sent to nil with arguments contained in anArray( aMetacelloFetchingMCSpecLoader(linea r load : explicit load : 1.7.1-baseline [ConfigurationOfNextPlan] explicit load : 1.7.1-baseline [ConfigurationOfNextPlan] explicit load : 1.7.1-baseline [ConfigurationOfNextPlan] explicit load : 1.7.1-baseline [ConfigurationOfNextPlan])). Furthermore, if I include the complete project spec for Pharo in the common section, Metacello tries to load that version in gemstone in spite of the specific Gemstone section. Any ideas what I might be doing wrong? thanks Johan On Wednesday, February 20, 2013 5:57:06 PM UTC+1, Johan Brichau wrote: Hi there, You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
Johan,
I am suspicious about your use of overrides in the pharo section ... is it the pharo load that is causing your error? Otherwise things look correct... I'd like to know the receiver in MetacelloMCProjectSpec>>ensureLoadUsing:, where the ensureLoadUsing is probably coming from ... The ensureLoadUsing: error looks like it might be related to an out of date cache. You might try: MetacelloProjectRegistration primeRegistryFromImage or MetacelloProjectRegistration resetRegistry; primeRegistryFromImage ... if one of those two works, let me know. Dale ----- Original Message ----- | From: "Johan Brichau" <[hidden email]> | To: [hidden email] | Sent: Wednesday, February 20, 2013 1:11:36 PM | Subject: [Metacello] Re: Sample metacello configuration referencing a github project? | | I managed to get a little further and maybe the problem is more related to | the fact that I need a different project spec for Pharo and Gemstone. | In the Pharo section, I can use the 'traditional' project spec: | | spec | project: 'ZincHTTP' | overrides: | [ spec | className: 'ConfigurationOfZincHTTPComponents'; | versionString: '1.7'; | file: 'ConfigurationOfZincHTTPComponents'; | loads: 'Core'; | repository: 'http://www.squeaksource.com/ZincHTTPComponents']. | | In the Gemstone section, I now include the following project spec to load | the one from github: | | "Zinc HTTP" | spec | baseline: 'ZincHTTP' | with: | [ spec | className: 'BaselineOfZinc'; | loads: 'Core'; | repository: 'github://glassdb/zinc:gemstone2.4/repository']. | ] | | In the common section, I merely mention: | | spec project: 'ZincHTTP'. | | Because otherwise, I get a 'name not found' when trying to load. However, | this also leads to an error trying to load: | | No method was found for the selector #'ensureLoadUsing:' when sent | to nil with arguments contained in anArray( | aMetacelloFetchingMCSpecLoader(linea | r load : | explicit load : 1.7.1-baseline [ConfigurationOfNextPlan] | explicit load : 1.7.1-baseline [ConfigurationOfNextPlan] | explicit load : 1.7.1-baseline [ConfigurationOfNextPlan] | explicit load : 1.7.1-baseline [ConfigurationOfNextPlan])). | | Furthermore, if I include the complete project spec for Pharo in the common | section, Metacello tries to load that version in gemstone in spite of the | specific Gemstone section. | | Any ideas what I might be doing wrong? | | thanks | Johan | | On Wednesday, February 20, 2013 5:57:06 PM UTC+1, Johan Brichau wrote: | > | > Hi there, | > | > I am trying to include the Zinc project on Github in our Metacello | > configuration. | > However, I'm getting errors probably because I'm not sure how to include a | > project reference to github inside my metacello conf. | > | > For example: | > | > spec | > project: 'ZincHTTP' | > with:: | > [ spec | > loads: 'Core'; | > version: #stable; | > file: 'BaselineOfZinc'; | > repository: 'github://glassdb/zinc:gemstone2.4/repository']. | > | > Are there existing configurations that I can take a look at to know how to | > reference a project on github? | > | > thanks | > Johan | > | | -- | You received this message because you are subscribed to the Google Groups | "Metacello" group. | To unsubscribe from this group and stop receiving emails from it, send an | email to [hidden email]. | For more options, visit https://groups.google.com/groups/opt_out. | | | -- You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
In reply to this post by Johan Brichau-3
I guess I'm using this mailinglist as my rubber duck [1] :-)
First off, it seems the load problem was because I was using #'gs2.4' instead of #'gs2.4.x' to identify the Gemstone section. Once I corrected that, the load proceeded. Unfortunately, the load is not (yet) correct. Some Zinc packages of the Gemstone version mentioned in the ConfigurationOfZincHTTPComponents configuration (for Zinc 1.1) are still getting loaded. They are: Zinc-GemStone and Zinc-GemStonePreliminaries. The Zinc-HTTP package is getting loaded from github correctly. These packages were also loaded before the load but I unloaded them before loading the new Zinc version. [1] http://en.wikipedia.org/wiki/Rubber_duck_debugging On Wednesday, February 20, 2013 10:11:36 PM UTC+1, Johan Brichau wrote: I managed to get a little further and maybe the problem is more related to the fact that I need a different project spec for Pharo and Gemstone. You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
In reply to this post by Dale Henrichs
Hi Dale,
I managed to get a little further in the meantime but now I'm stuck. See my other email: I am still getting packages loaded for an older gemstone version referenced by the ConfigurationOfZincHTTPcomponents that is now only referenced in the pharo section of the metacello conf. Here are the relevant parts of my configuration: spec for: #common do: [ spec project: 'ZincHTTP'. ]. spec for: #pharo do: [ "Zinc HTTP" spec project: 'ZincHTTP' overrides: [ spec className: 'ConfigurationOfZincHTTPComponents'; versionString: '1.7'; file: 'ConfigurationOfZincHTTPComponents'; loads: 'Core'; repository: 'http://www.squeaksource.com/ZincHTTPComponents']. ]. spec for: #gemstone do: [ ]. spec for: #'gs2.4.x' do:[ "Zinc HTTP" spec removeProject: 'ZincHTTP'. spec baseline: 'ZincHTTP' with: [ spec className: 'BaselineOfZinc'; loads: 'Core'; repository: 'github://glassdb/zinc:gemstone2.4/repository']. ] On Wednesday, February 20, 2013 10:45:24 PM UTC+1, Dale wrote: Johan, You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
I found the problem: I include another project that load version 1.1 of Zinc...
I know how to solve that one with the scripting API :-) Sorry for the noise... but hey, it proves rubber duck debugging works :-)
-- On Wednesday, February 20, 2013 11:06:38 PM UTC+1, Johan Brichau wrote: Hi Dale, You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
Johan,
I'm glad that you were able to get things going ... I often find that the same technique works for me ... usually I grab a human victim to listne to my story ... perhaps I should get a duck for my desk? Dale ----- Original Message ----- | From: "Johan Brichau" <[hidden email]> | To: [hidden email] | Sent: Wednesday, February 20, 2013 2:21:44 PM | Subject: Re: [Metacello] Re: Sample metacello configuration referencing a github project? | | I found the problem: I include another project that load version 1.1 of | Zinc... | | I know how to solve that one with the scripting API :-) | | Sorry for the noise... but hey, it proves rubber duck debugging works :-) | | On Wednesday, February 20, 2013 11:06:38 PM UTC+1, Johan Brichau wrote: | > | > Hi Dale, | > | > I managed to get a little further in the meantime but now I'm stuck. | > See my other email: I am still getting packages loaded for an older | > gemstone version referenced by the ConfigurationOfZincHTTPcomponents that | > is now only referenced in the pharo section of the metacello conf. | > | > Here are the relevant parts of my configuration: | > | > spec | > for: #common | > do: | > [ | > spec project: 'ZincHTTP'. | > ]. | > spec | > for: #pharo | > do: [ | > | > "Zinc HTTP" | > spec | > project: 'ZincHTTP' | > overrides: | > [ spec | > className: 'ConfigurationOfZincHTTPComponents'; | > versionString: '1.7'; | > file: 'ConfigurationOfZincHTTPComponents'; | > loads: 'Core'; | > repository: 'http://www.squeaksource.com/ZincHTTPComponents']. | > ]. | > | > spec | > for: #gemstone | > do: [ | > ]. | > spec | > for: #'gs2.4.x' | > do:[ | > "Zinc HTTP" | > spec removeProject: 'ZincHTTP'. | > spec | > baseline: 'ZincHTTP' | > with: | > [ spec | > className: 'BaselineOfZinc'; | > loads: 'Core'; | > repository: 'github://glassdb/zinc:gemstone2.4/repository']. | > ] | > | > On Wednesday, February 20, 2013 10:45:24 PM UTC+1, Dale wrote: | >> | >> Johan, | >> | >> I am suspicious about your use of overrides in the pharo section ... is | >> it the pharo load that is causing your error? Otherwise things look | >> correct... | >> | >> I'd like to know the receiver in | >> MetacelloMCProjectSpec>>ensureLoadUsing:, where the ensureLoadUsing is | >> probably coming from ... | >> | >> | >> The ensureLoadUsing: error looks like it might be related to an out of | >> date cache. You might try: | >> | >> MetacelloProjectRegistration primeRegistryFromImage | >> | >> or | >> | >> MetacelloProjectRegistration | >> resetRegistry; | >> primeRegistryFromImage | >> | >> ... if one of those two works, let me know. | >> | >> Dale | >> | >> ----- Original Message ----- | >> | From: "Johan Brichau" <[hidden email]> | >> | To: [hidden email] | >> | Sent: Wednesday, February 20, 2013 1:11:36 PM | >> | Subject: [Metacello] Re: Sample metacello configuration referencing a | >> github project? | >> | | >> | I managed to get a little further and maybe the problem is more related | >> to | >> | the fact that I need a different project spec for Pharo and Gemstone. | >> | In the Pharo section, I can use the 'traditional' project spec: | >> | | >> | spec | >> | project: 'ZincHTTP' | >> | overrides: | >> | [ spec | >> | className: 'ConfigurationOfZincHTTPComponents'; | >> | versionString: '1.7'; | >> | file: 'ConfigurationOfZincHTTPComponents'; | >> | loads: 'Core'; | >> | repository: 'http://www.squeaksource.com/ZincHTTPComponents']. | >> | | >> | In the Gemstone section, I now include the following project spec to | >> load | >> | the one from github: | >> | | >> | "Zinc HTTP" | >> | spec | >> | baseline: 'ZincHTTP' | >> | with: | >> | [ spec | >> | className: 'BaselineOfZinc'; | >> | loads: 'Core'; | >> | repository: 'github://glassdb/zinc:gemstone2.4/repository']. | >> | ] | >> | | >> | In the common section, I merely mention: | >> | | >> | spec project: 'ZincHTTP'. | >> | | >> | Because otherwise, I get a 'name not found' when trying to load. | >> However, | >> | this also leads to an error trying to load: | >> | | >> | No method was found for the selector #'ensureLoadUsing:' when sent | >> | to nil with arguments contained in anArray( | >> | aMetacelloFetchingMCSpecLoader(linea | >> | r load : | >> | explicit load : 1.7.1-baseline [ConfigurationOfNextPlan] | >> | explicit load : 1.7.1-baseline [ConfigurationOfNextPlan] | >> | explicit load : 1.7.1-baseline [ConfigurationOfNextPlan] | >> | explicit load : 1.7.1-baseline [ConfigurationOfNextPlan])). | >> | | >> | Furthermore, if I include the complete project spec for Pharo in the | >> common | >> | section, Metacello tries to load that version in gemstone in spite of | >> the | >> | specific Gemstone section. | >> | | >> | Any ideas what I might be doing wrong? | >> | | >> | thanks | >> | Johan | >> | | >> | On Wednesday, February 20, 2013 5:57:06 PM UTC+1, Johan Brichau wrote: | >> | > | >> | > Hi there, | >> | > | >> | > I am trying to include the Zinc project on Github in our Metacello | >> | > configuration. | >> | > However, I'm getting errors probably because I'm not sure how to | >> include a | >> | > project reference to github inside my metacello conf. | >> | > | >> | > For example: | >> | > | >> | > spec | >> | > project: 'ZincHTTP' | >> | > with:: | >> | > [ spec | >> | > loads: 'Core'; | >> | > version: #stable; | >> | > file: 'BaselineOfZinc'; | >> | > repository: 'github://glassdb/zinc:gemstone2.4/repository']. | >> | > | >> | > Are there existing configurations that I can take a look at to know | >> how to | >> | > reference a project on github? | >> | > | >> | > thanks | >> | > Johan | >> | > | >> | | >> | -- | >> | You received this message because you are subscribed to the Google | >> Groups | >> | "Metacello" group. | >> | To unsubscribe from this group and stop receiving emails from it, send | >> an | >> | email to [hidden email]. | >> | For more options, visit https://groups.google.com/groups/opt_out. | >> | | >> | | >> | | >> | > | | -- | You received this message because you are subscribed to the Google Groups | "Metacello" group. | To unsubscribe from this group and stop receiving emails from it, send an | email to [hidden email]. | For more options, visit https://groups.google.com/groups/opt_out. | | | -- You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
Hi Dale,
It seems my optimism on dealing with that issue via the scripting API was a bit premature... The problem I am facing is that Metacello is not seeing the Zinc project on github as a 'new version' of the project on monticello. The result is that both projects are always loaded. The github-based version because I am including it and the monticello-based version because it's included in referenced metacello configuration. I used to be able to deal with those issues if the project's were detected to be the same. But how can I tell Metacello that the github version of Zinc is actually the same project as the one on Monticello? Or can I intervene with the load somehow using the scripting api to explicitly prohibit the load of a certain project? Hope that I'm making my problem clear... Johan On Wednesday, February 20, 2013 11:33:20 PM UTC+1, Dale wrote: Johan, You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
Johan,
I'm not sure I understand the problem ... I guess I need to see some configuration snippets to understand what's going wrong ... Dale ----- Original Message ----- | From: "Johan Brichau" <[hidden email]> | To: [hidden email] | Sent: Thursday, February 21, 2013 11:19:47 AM | Subject: Re: [Metacello] Re: Sample metacello configuration referencing a github project? | | Hi Dale, | | It seems my optimism on dealing with that issue via the scripting API was a | bit premature... | | The problem I am facing is that Metacello is not seeing the Zinc project on | github as a 'new version' of the project on monticello. The result is that | both projects are always loaded. The github-based version because I am | including it and the monticello-based version because it's included in | referenced metacello configuration. | | I used to be able to deal with those issues if the project's were detected | to be the same. But how can I tell Metacello that the github version of | Zinc is actually the same project as the one on Monticello? Or can I | intervene with the load somehow using the scripting api to explicitly | prohibit the load of a certain project? | | Hope that I'm making my problem clear... | | Johan | | On Wednesday, February 20, 2013 11:33:20 PM UTC+1, Dale wrote: | > | > Johan, | > | > I'm glad that you were able to get things going ... I often find that the | > same technique works for me ... usually I grab a human victim to listne to | > my story ... perhaps I should get a duck for my desk? | > | > Dale | > | > ----- Original Message ----- | > | From: "Johan Brichau" <[hidden email] <javascript:>> | > | To: [hidden email] <javascript:> | > | Sent: Wednesday, February 20, 2013 2:21:44 PM | > | Subject: Re: [Metacello] Re: Sample metacello configuration referencing | > a github project? | > | | > | I found the problem: I include another project that load version 1.1 of | > | Zinc... | > | | > | I know how to solve that one with the scripting API :-) | > | | > | Sorry for the noise... but hey, it proves rubber duck debugging works | > :-) | > | | > | On Wednesday, February 20, 2013 11:06:38 PM UTC+1, Johan Brichau wrote: | > | > | > | > Hi Dale, | > | > | > | > I managed to get a little further in the meantime but now I'm stuck. | > | > See my other email: I am still getting packages loaded for an older | > | > gemstone version referenced by the ConfigurationOfZincHTTPcomponents | > that | > | > is now only referenced in the pharo section of the metacello conf. | > | > | > | > Here are the relevant parts of my configuration: | > | > | > | > spec | > | > for: #common | > | > do: | > | > [ | > | > spec project: 'ZincHTTP'. | > | > ]. | > | > spec | > | > for: #pharo | > | > do: [ | > | > | > | > "Zinc HTTP" | > | > spec | > | > project: 'ZincHTTP' | > | > overrides: | > | > [ spec | > | > className: 'ConfigurationOfZincHTTPComponents'; | > | > versionString: '1.7'; | > | > file: 'ConfigurationOfZincHTTPComponents'; | > | > loads: 'Core'; | > | > repository: 'http://www.squeaksource.com/ZincHTTPComponents']. | > | > ]. | > | > | > | > spec | > | > for: #gemstone | > | > do: [ | > | > ]. | > | > spec | > | > for: #'gs2.4.x' | > | > do:[ | > | > "Zinc HTTP" | > | > spec removeProject: 'ZincHTTP'. | > | > spec | > | > baseline: 'ZincHTTP' | > | > with: | > | > [ spec | > | > className: 'BaselineOfZinc'; | > | > loads: 'Core'; | > | > repository: 'github://glassdb/zinc:gemstone2.4/repository']. | > | > ] | > | > | > | > On Wednesday, February 20, 2013 10:45:24 PM UTC+1, Dale wrote: | > | >> | > | >> Johan, | > | >> | > | >> I am suspicious about your use of overrides in the pharo section ... | > is | > | >> it the pharo load that is causing your error? Otherwise things look | > | >> correct... | > | >> | > | >> I'd like to know the receiver in | > | >> MetacelloMCProjectSpec>>ensureLoadUsing:, where the ensureLoadUsing | > is | > | >> probably coming from ... | > | >> | > | >> | > | >> The ensureLoadUsing: error looks like it might be related to an out | > of | > | >> date cache. You might try: | > | >> | > | >> MetacelloProjectRegistration primeRegistryFromImage | > | >> | > | >> or | > | >> | > | >> MetacelloProjectRegistration | > | >> resetRegistry; | > | >> primeRegistryFromImage | > | >> | > | >> ... if one of those two works, let me know. | > | >> | > | >> Dale | > | >> | > | >> ----- Original Message ----- | > | >> | From: "Johan Brichau" <[hidden email]> | > | >> | To: [hidden email] | > | >> | Sent: Wednesday, February 20, 2013 1:11:36 PM | > | >> | Subject: [Metacello] Re: Sample metacello configuration referencing | > a | > | >> github project? | > | >> | | > | >> | I managed to get a little further and maybe the problem is more | > related | > | >> to | > | >> | the fact that I need a different project spec for Pharo and | > Gemstone. | > | >> | In the Pharo section, I can use the 'traditional' project spec: | > | >> | | > | >> | spec | > | >> | project: 'ZincHTTP' | > | >> | overrides: | > | >> | [ spec | > | >> | className: 'ConfigurationOfZincHTTPComponents'; | > | >> | versionString: '1.7'; | > | >> | file: 'ConfigurationOfZincHTTPComponents'; | > | >> | loads: 'Core'; | > | >> | repository: 'http://www.squeaksource.com/ZincHTTPComponents']. | > | >> | | > | >> | In the Gemstone section, I now include the following project spec | > to | > | >> load | > | >> | the one from github: | > | >> | | > | >> | "Zinc HTTP" | > | >> | spec | > | >> | baseline: 'ZincHTTP' | > | >> | with: | > | >> | [ spec | > | >> | className: 'BaselineOfZinc'; | > | >> | loads: 'Core'; | > | >> | repository: 'github://glassdb/zinc:gemstone2.4/repository']. | > | >> | ] | > | >> | | > | >> | In the common section, I merely mention: | > | >> | | > | >> | spec project: 'ZincHTTP'. | > | >> | | > | >> | Because otherwise, I get a 'name not found' when trying to load. | > | >> However, | > | >> | this also leads to an error trying to load: | > | >> | | > | >> | No method was found for the selector #'ensureLoadUsing:' when sent | > | >> | to nil with arguments contained in anArray( | > | >> | aMetacelloFetchingMCSpecLoader(linea | > | >> | r load : | > | >> | explicit load : 1.7.1-baseline [ConfigurationOfNextPlan] | > | >> | explicit load : 1.7.1-baseline [ConfigurationOfNextPlan] | > | >> | explicit load : 1.7.1-baseline [ConfigurationOfNextPlan] | > | >> | explicit load : 1.7.1-baseline [ConfigurationOfNextPlan])). | > | >> | | > | >> | Furthermore, if I include the complete project spec for Pharo in | > the | > | >> common | > | >> | section, Metacello tries to load that version in gemstone in spite | > of | > | >> the | > | >> | specific Gemstone section. | > | >> | | > | >> | Any ideas what I might be doing wrong? | > | >> | | > | >> | thanks | > | >> | Johan | > | >> | | > | >> | On Wednesday, February 20, 2013 5:57:06 PM UTC+1, Johan Brichau | > wrote: | > | >> | > | > | >> | > Hi there, | > | >> | > | > | >> | > I am trying to include the Zinc project on Github in our | > Metacello | > | >> | > configuration. | > | >> | > However, I'm getting errors probably because I'm not sure how to | > | >> include a | > | >> | > project reference to github inside my metacello conf. | > | >> | > | > | >> | > For example: | > | >> | > | > | >> | > spec | > | >> | > project: 'ZincHTTP' | > | >> | > with:: | > | >> | > [ spec | > | >> | > loads: 'Core'; | > | >> | > version: #stable; | > | >> | > file: 'BaselineOfZinc'; | > | >> | > repository: 'github://glassdb/zinc:gemstone2.4/repository']. | > | >> | > | > | >> | > Are there existing configurations that I can take a look at to | > know | > | >> how to | > | >> | > reference a project on github? | > | >> | > | > | >> | > thanks | > | >> | > Johan | > | >> | > | > | >> | | > | >> | -- | > | >> | You received this message because you are subscribed to the Google | > | >> Groups | > | >> | "Metacello" group. | > | >> | To unsubscribe from this group and stop receiving emails from it, | > send | > | >> an | > | >> | email to [hidden email]. | > | >> | For more options, visit https://groups.google.com/groups/opt_out. | > | >> | | > | >> | | > | >> | | > | >> | > | > | > | | > | -- | > | You received this message because you are subscribed to the Google | > Groups | > | "Metacello" group. | > | To unsubscribe from this group and stop receiving emails from it, send | > an | > | email to [hidden email] <javascript:>. | > | For more options, visit https://groups.google.com/groups/opt_out. | > | | > | | > | | > | | -- | You received this message because you are subscribed to the Google Groups | "Metacello" group. | To unsubscribe from this group and stop receiving emails from it, send an | email to [hidden email]. | For more options, visit https://groups.google.com/groups/opt_out. | | | -- You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/groups/opt_out. |
Free forum by Nabble | Edit this page |