Smalltalk › Pharo › Pharo Smalltalk Users

Seaside can not be used with Pharo 60261

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

16 messages Options

Pierre Chanson

Seaside can not be used with Pharo 60261

In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x’ have been removed and Seaside does not have configuration for pharo6.

Is there a plan to update the configuration of Seaside ?

Thanks !

Pierre and Norbert

EstebanLM

Re: Seaside can not be used with Pharo 60261

this is a question more appropriate for Seaside list :)

> On 17 Oct 2016, at 20:07, Pierre CHANSON <[hidden email]> wrote:
>
> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x’ have been removed and Seaside does not have configuration for pharo6.
>
> Is there a plan to update the configuration of Seaside ?
>
> Thanks !
>
> Pierre and Norbert

Johan Brichau-2

Re: [Seaside] Seaside can not be used with Pharo 60261

Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6.

I will upload them as soon as I receive them

Johan

> On 17 Oct 2016, at 21:04, Esteban Lorenzano <[hidden email]> wrote:
>
> this is a question more appropriate for Seaside list :)
>
>> On 17 Oct 2016, at 20:07, Pierre CHANSON <[hidden email]> wrote:
>>
>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x’ have been removed and Seaside does not have configuration for pharo6.
>>
>> Is there a plan to update the configuration of Seaside ?
>>
>> Thanks !
>>
>> Pierre and Norbert
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Johan Brichau-2

Re: [Seaside] Seaside can not be used with Pharo 60261

I uploaded the changes by Christophe. If it does not work, let me know. I did not try.

cheers
Johan

ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5

> On 18 Oct 2016, at 10:00, Johan Brichau <[hidden email]> wrote:
>
> Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6.
>
> I will upload them as soon as I receive them
>
> Johan
>
>> On 17 Oct 2016, at 21:04, Esteban Lorenzano <[hidden email]> wrote:
>>
>> this is a question more appropriate for Seaside list :)
>>
>>> On 17 Oct 2016, at 20:07, Pierre CHANSON <[hidden email]> wrote:
>>>
>>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x’ have been removed and Seaside does not have configuration for pharo6.
>>>
>>> Is there a plan to update the configuration of Seaside ?
>>>
>>> Thanks !
>>>
>>> Pierre and Norbert
>>
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

NorbertHartl

Re: [Seaside] Seaside can not be used with Pharo 60261

>
>> On 18 Oct 2016, at 10:00, Johan Brichau <[hidden email]> wrote:
>>
>> Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6.
>>
>> I will upload them as soon as I receive them
>>
>> Johan
>>
>>> On 17 Oct 2016, at 21:04, Esteban Lorenzano <[hidden email]> wrote:
>>>
>>> this is a question more appropriate for Seaside list :)
>>>
>>>> On 17 Oct 2016, at 20:07, Pierre CHANSON <[hidden email]> wrote:
>>>>
>>>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x’ have been removed and Seaside does not have configuration for pharo6.
>>>>
>>>> Is there a plan to update the configuration of Seaside ?
>>>>
>>>> Thanks !
>>>>
>>>> Pierre and Norbert
>>>
>>> _______________________________________________
>>> seaside mailing list
>>> [hidden email]
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>
>

NorbertHartl

Re: [Seaside] Seaside can not be used with Pharo 60261

In reply to this post by Johan Brichau-2

You uploaded ConfigurationOfGrease but not Seaside. Mistake?

Norbert

> Am 18.10.2016 um 10:11 schrieb Johan Brichau <[hidden email]>:
>
> I uploaded the changes by Christophe. If it does not work, let me know. I did not try.
>
> cheers
> Johan
>
> ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5
>
>> On 18 Oct 2016, at 10:00, Johan Brichau <[hidden email]> wrote:
>>
>> Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6.
>>
>> I will upload them as soon as I receive them
>>
>> Johan
>>
>>> On 17 Oct 2016, at 21:04, Esteban Lorenzano <[hidden email]> wrote:
>>>
>>> this is a question more appropriate for Seaside list :)
>>>
>>>> On 17 Oct 2016, at 20:07, Pierre CHANSON <[hidden email]> wrote:
>>>>
>>>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x’ have been removed and Seaside does not have configuration for pharo6.
>>>>
>>>> Is there a plan to update the configuration of Seaside ?
>>>>
>>>> Thanks !
>>>>
>>>> Pierre and Norbert
>>>
>>> _______________________________________________
>>> seaside mailing list
>>> [hidden email]
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>
>

Johan Brichau-2

Re: [Seaside] Seaside can not be used with Pharo 60261

I only received a config for Grease :)
In my haste, I did not check you need Seaside :)

Right now, I’m a bit too busy so until someone can provide a working config, it will have to wait.

cheers
Johan

> On 18 Oct 2016, at 10:19, Norbert Hartl <[hidden email]> wrote:
>
> You uploaded ConfigurationOfGrease but not Seaside. Mistake?
>
> Norbert
>
>> Am 18.10.2016 um 10:11 schrieb Johan Brichau <[hidden email]>:
>>
>> I uploaded the changes by Christophe. If it does not work, let me know. I did not try.
>>
>> cheers
>> Johan
>>
>> ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5
>>
>>> On 18 Oct 2016, at 10:00, Johan Brichau <[hidden email]> wrote:
>>>
>>> Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6.
>>>
>>> I will upload them as soon as I receive them
>>>
>>> Johan
>>>
>>>> On 17 Oct 2016, at 21:04, Esteban Lorenzano <[hidden email]> wrote:
>>>>
>>>> this is a question more appropriate for Seaside list :)
>>>>
>>>>> On 17 Oct 2016, at 20:07, Pierre CHANSON <[hidden email]> wrote:
>>>>>
>>>>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x’ have been removed and Seaside does not have configuration for pharo6.
>>>>>
>>>>> Is there a plan to update the configuration of Seaside ?
>>>>>
>>>>> Thanks !
>>>>>
>>>>> Pierre and Norbert
>>>>
>>>> _______________________________________________
>>>> seaside mailing list
>>>> [hidden email]
>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>
>>
>>
>
>

CyrilFerlicot

Re: [Seaside] Seaside can not be used with Pharo 60261

In reply to this post by Johan Brichau-2

Le 18/10/2016 à 15:41, Cyril Ferlicot D. a écrit :

> Hi!
>
> I could load Seaside but when I start the adaptor and go to
> localhost:8080 I get an error[1] `receiver of #from:to: is nil`.
> There is some error on Jenkin's logs that where not here before[2].
>
>
> [1] http://puu.sh/rN9fV/780adbcfe0.png
> [2] http://puu.sh/rN9rb/dd9de6776a.png
>

I think that this mcz should correct the problem but I don't have the
rights on Seaside repo. Can someone add me to the Seaside Team or copy
the mcz?

I just added a 'pharo6.x' in the configuration where there is a
'pharo5.x' so it should be a safe change.

--
Cyril Ferlicot

http://www.synectique.eu

2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

ConfigurationOfSeaside3-CyrilFerlicot.321.mcz (324K) Download Attachment

signature.asc (836 bytes) Download Attachment

NorbertHartl

Re: [Seaside] Seaside can not be used with Pharo 60261

In reply to this post by Johan Brichau-2

I tried to but I failed. It is very strange indeed. I added the platform attribute #'pharo6.x' to every location where there is a #'pharo5.x' attribute (see attached configuration).
When loading metacello looks into older versions as well (in this case version 3.1.6). There the platform attribute does not exist and it seems to fallback on a configuration for #pharo where a package Seaside-Pharo-Development is referenced. While trying to find the definition of that package it fails.

Does somebody know why it behaves that weird? Or even better know a solution :)

thanks,

Norbert

> Am 18.10.2016 um 10:37 schrieb Johan Brichau <[hidden email]>:
>
> I only received a config for Grease :)
> In my haste, I did not check you need Seaside :)
>
> Right now, I’m a bit too busy so until someone can provide a working config, it will have to wait.
>
> cheers
> Johan
>
>> On 18 Oct 2016, at 10:19, Norbert Hartl <[hidden email]> wrote:
>>
>> You uploaded ConfigurationOfGrease but not Seaside. Mistake?
>>
>> Norbert
>>
>>> Am 18.10.2016 um 10:11 schrieb Johan Brichau <[hidden email]>:
>>>
>>> I uploaded the changes by Christophe. If it does not work, let me know. I did not try.
>>>
>>> cheers
>>> Johan
>>>
>>> ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5
>>>
>>>> On 18 Oct 2016, at 10:00, Johan Brichau <[hidden email]> wrote:
>>>>
>>>> Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6.
>>>>
>>>> I will upload them as soon as I receive them
>>>>
>>>> Johan
>>>>
>>>>> On 17 Oct 2016, at 21:04, Esteban Lorenzano <[hidden email]> wrote:
>>>>>
>>>>> this is a question more appropriate for Seaside list :)
>>>>>
>>>>>> On 17 Oct 2016, at 20:07, Pierre CHANSON <[hidden email]> wrote:
>>>>>>
>>>>>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x’ have been removed and Seaside does not have configuration for pharo6.
>>>>>>
>>>>>> Is there a plan to update the configuration of Seaside ?
>>>>>>
>>>>>> Thanks !
>>>>>>
>>>>>> Pierre and Norbert
>>>>>
>>>>> _______________________________________________
>>>>> seaside mailing list
>>>>> [hidden email]
>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>
>>>
>>>
>>
>>
>
>

ConfigurationOfSeaside3-NorbertHartl.321.mcz (323K) Download Attachment

Johan Brichau-2

Re: [Seaside] Seaside can not be used with Pharo 60261

Can you post the snippet how you load it?

> On 18 Oct 2016, at 16:21, Norbert Hartl <[hidden email]> wrote:
>
> I tried to but I failed. It is very strange indeed. I added the platform attribute #'pharo6.x' to every location where there is a #'pharo5.x' attribute (see attached configuration).
> When loading metacello looks into older versions as well (in this case version 3.1.6). There the platform attribute does not exist and it seems to fallback on a configuration for #pharo where a package Seaside-Pharo-Development is referenced. While trying to find the definition of that package it fails.
>
> Does somebody know why it behaves that weird? Or even better know a solution :)
>
> thanks,
>
> Norbert
>
> <ConfigurationOfSeaside3-NorbertHartl.321.mcz>
>
>> Am 18.10.2016 um 10:37 schrieb Johan Brichau <[hidden email]>:
>>
>> I only received a config for Grease :)
>> In my haste, I did not check you need Seaside :)
>>
>> Right now, I’m a bit too busy so until someone can provide a working config, it will have to wait.
>>
>> cheers
>> Johan
>>
>>> On 18 Oct 2016, at 10:19, Norbert Hartl <[hidden email]> wrote:
>>>
>>> You uploaded ConfigurationOfGrease but not Seaside. Mistake?
>>>
>>> Norbert
>>>
>>>> Am 18.10.2016 um 10:11 schrieb Johan Brichau <[hidden email]>:
>>>>
>>>> I uploaded the changes by Christophe. If it does not work, let me know. I did not try.
>>>>
>>>> cheers
>>>> Johan
>>>>
>>>> ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5
>>>>
>>>>> On 18 Oct 2016, at 10:00, Johan Brichau <[hidden email]> wrote:
>>>>>
>>>>> Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6.
>>>>>
>>>>> I will upload them as soon as I receive them
>>>>>
>>>>> Johan
>>>>>
>>>>>> On 17 Oct 2016, at 21:04, Esteban Lorenzano <[hidden email]> wrote:
>>>>>>
>>>>>> this is a question more appropriate for Seaside list :)
>>>>>>
>>>>>>> On 17 Oct 2016, at 20:07, Pierre CHANSON <[hidden email]> wrote:
>>>>>>>
>>>>>>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x’ have been removed and Seaside does not have configuration for pharo6.
>>>>>>>
>>>>>>> Is there a plan to update the configuration of Seaside ?
>>>>>>>
>>>>>>> Thanks !
>>>>>>>
>>>>>>> Pierre and Norbert
>>>>>>
>>>>>> _______________________________________________
>>>>>> seaside mailing list
>>>>>> [hidden email]
>>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>

NorbertHartl

Re: [Seaside] Seaside can not be used with Pharo 60261

I have a ConfigurationOfAster with a baseline

baseline01: spec
<version: '0.1-baseline'>

spec for: #'common' do: [
spec blessing: #'baseline'.
spec repository: 'filetree://repository/'.
spec
project: 'RFB' with: [
spec
className: #ConfigurationOfRFB;
versionString: '0.64';
repository: 'http://smalltalkhub.com/mc/PharoExtras/RFB/main/' ];
project: 'Seaside3' with: [
spec
className: #ConfigurationOfSeaside3;
versionString: #'release3.2';
repository: 'filetree://repository/' ].
spec
package: #'Aster-Core';
package: #'Aster-Seaside' with: [
spec requires: #(#'Aster-Core' 'Seaside3' 'RFB' ). ]. ].

and I load

(ConfigurationOfAster project version: #development) load

Norbert

> Am 18.10.2016 um 16:32 schrieb Johan Brichau <[hidden email]>:
>
> Can you post the snippet how you load it?
>
>> On 18 Oct 2016, at 16:21, Norbert Hartl <[hidden email]> wrote:
>>
>> I tried to but I failed. It is very strange indeed. I added the platform attribute #'pharo6.x' to every location where there is a #'pharo5.x' attribute (see attached configuration).
>> When loading metacello looks into older versions as well (in this case version 3.1.6). There the platform attribute does not exist and it seems to fallback on a configuration for #pharo where a package Seaside-Pharo-Development is referenced. While trying to find the definition of that package it fails.
>>
>> Does somebody know why it behaves that weird? Or even better know a solution :)
>>
>> thanks,
>>
>> Norbert
>>
>> <ConfigurationOfSeaside3-NorbertHartl.321.mcz>
>>
>>> Am 18.10.2016 um 10:37 schrieb Johan Brichau <[hidden email]>:
>>>
>>> I only received a config for Grease :)
>>> In my haste, I did not check you need Seaside :)
>>>
>>> Right now, I’m a bit too busy so until someone can provide a working config, it will have to wait.
>>>
>>> cheers
>>> Johan
>>>
>>>> On 18 Oct 2016, at 10:19, Norbert Hartl <[hidden email]> wrote:
>>>>
>>>> You uploaded ConfigurationOfGrease but not Seaside. Mistake?
>>>>
>>>> Norbert
>>>>
>>>>> Am 18.10.2016 um 10:11 schrieb Johan Brichau <[hidden email]>:
>>>>>
>>>>> I uploaded the changes by Christophe. If it does not work, let me know. I did not try.
>>>>>
>>>>> cheers
>>>>> Johan
>>>>>
>>>>> ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5
>>>>>
>>>>>> On 18 Oct 2016, at 10:00, Johan Brichau <[hidden email]> wrote:
>>>>>>
>>>>>> Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6.
>>>>>>
>>>>>> I will upload them as soon as I receive them
>>>>>>
>>>>>> Johan
>>>>>>
>>>>>>> On 17 Oct 2016, at 21:04, Esteban Lorenzano <[hidden email]> wrote:
>>>>>>>
>>>>>>> this is a question more appropriate for Seaside list :)
>>>>>>>
>>>>>>>> On 17 Oct 2016, at 20:07, Pierre CHANSON <[hidden email]> wrote:
>>>>>>>>
>>>>>>>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x’ have been removed and Seaside does not have configuration for pharo6.
>>>>>>>>
>>>>>>>> Is there a plan to update the configuration of Seaside ?
>>>>>>>>
>>>>>>>> Thanks !
>>>>>>>>
>>>>>>>> Pierre and Norbert
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> seaside mailing list
>>>>>>> [hidden email]
>>>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
>

Johan Brichau-2

Re: [Seaside] Seaside can not be used with Pharo 60261

On 18 Oct 2016, at 16:36, Norbert Hartl <[hidden email]> wrote:

(ConfigurationOfAster project version: #development) load

There are issues with this ‘old’ way of Metacello loading. Can you try:

Metacello new

configuration:’Aster’;

version: #development;

load.

(Maybe you need to add the repo to, don’t know).

Cheers

Johan

NorbertHartl

Re: [Seaside] Seaside can not be used with Pharo 60261

Thanks, that worked. Feels really strange encountering this. So one cannot use the commandline handler for loading a configuration anymore. Sad! The same way sad as you cannot use versionner anymore when you start to use BaselineOf instead of ConfigurationOf.

This is not a complaint because I can understand why this happens. It is just that we need more energy to solve all this than we have. Sad!

Norbert

Am 18.10.2016 um 17:20 schrieb Johan Brichau <[hidden email]>:

On 18 Oct 2016, at 16:36, Norbert Hartl <[hidden email]> wrote:

(ConfigurationOfAster project version: #development) load

There are issues with this ‘old’ way of Metacello loading. Can you try:

Metacello new
configuration:’Aster’;
version: #development;
load.

(Maybe you need to add the repo to, don’t know).

Cheers
Johan

NorbertHartl

Re: [Seaside] Seaside can not be used with Pharo 60261

In reply to this post by Johan Brichau-2

Hi Johan,

can you please upload the ConfigurationOfSeaside3 I've sent in this thread?

thanks,

Norbert

Am 18.10.2016 um 17:20 schrieb Johan Brichau <[hidden email]>:

On 18 Oct 2016, at 16:36, Norbert Hartl <[hidden email]> wrote:

(ConfigurationOfAster project version: #development) load

There are issues with this ‘old’ way of Metacello loading. Can you try:

Metacello new
configuration:’Aster’;
version: #development;
load.

(Maybe you need to add the repo to, don’t know).

Cheers
Johan

Johan Brichau-2

Re: [Seaside] Seaside can not be used with Pharo 60261

Done!

Looked good to me, but I did not test.

If anyone experiences errors, let me know!

Johan

On 20 Oct 2016, at 11:39, Norbert Hartl <[hidden email]> wrote:

Hi Johan,

can you please upload the ConfigurationOfSeaside3 I've sent in this thread?

thanks,

Norbert

Am 18.10.2016 um 17:20 schrieb Johan Brichau <[hidden email]>:

On 18 Oct 2016, at 16:36, Norbert Hartl <[hidden email]> wrote:

(ConfigurationOfAster project version: #development) load

There are issues with this ‘old’ way of Metacello loading. Can you try:

Metacello new
configuration:’Aster’;
version: #development;
load.

(Maybe you need to add the repo to, don’t know).

Cheers
Johan

Johan Brichau-2

Re: [Seaside] Seaside can not be used with Pharo 60261

In reply to this post by NorbertHartl

I feel you pain.

It is vastly underestimated how much work is required to keep up with upgrades that break backwards compatibility, from OS upgrades to Pharo upgrades and everything in between…

Then again, the omelet does not make itself and certainly not without breaking the eggs ;)

Johan

On 18 Oct 2016, at 17:29, Norbert Hartl <[hidden email]> wrote:

Thanks, that worked. Feels really strange encountering this. So one cannot use the commandline handler for loading a configuration anymore. Sad! The same way sad as you cannot use versionner anymore when you start to use BaselineOf instead of ConfigurationOf.
This is not a complaint because I can understand why this happens. It is just that we need more energy to solve all this than we have. Sad!

Norbert

Am 18.10.2016 um 17:20 schrieb Johan Brichau <[hidden email]>:

On 18 Oct 2016, at 16:36, Norbert Hartl <[hidden email]> wrote:

(ConfigurationOfAster project version: #development) load

There are issues with this ‘old’ way of Metacello loading. Can you try:

Metacello new
configuration:’Aster’;
version: #development;
load.

(Maybe you need to add the repo to, don’t know).

Cheers
Johan