Trying to upgrade from Seaside 3.1 to 3.2 Metacello problem

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Trying to upgrade from Seaside 3.1 to 3.2 Metacello problem

GLASS mailing list
Hi,

I have a stone with Seaside loaded from github://GsDevKit/Seaside31:3.1.?/repository and I am loading it now from  'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'.

I am executing this code:

      Metacello new
          baseline: 'Seaside3';
          repository: 'github://GsDevKit/Seaside31:3.1.?/repository';
       unlock.


Metacello new
    baseline: 'Seaside3';
    repository:
    load:
        #('Core' 'Zinc-Seaside' 'Javascript' 'JQuery' 'JSON' 'FastCGI' 'Email');
    onConflict: [ :ex :loaded :incoming | ex useIncoming ];
    onUpgrade: [ :ex :loaded :incoming | ex useIncoming ];
    onWarning: [ :ex | ex resume ];
    version: '3.2.3';
    lock.


And I am still getting the attached error. 

How can I get rid of it? I am already telling it to #useIncoming on conflict, on upgrade....

Thanks in advance



--

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

Screen Shot 2017-07-07 at 5.34.42 PM.png (579K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Trying to upgrade from Seaside 3.1 to 3.2 Metacello problem

GLASS mailing list
OK, I did a #unregister besides the #unlock to the previous project and now it went a bit further.  But it still fails trying to load Grease...

Sure...I can try to manually unlock the filetree one, but why my code doesn't work?

See attached. 





On Fri, Jul 7, 2017 at 5:36 PM, Mariano Martinez Peck <[hidden email]> wrote:
Hi,

I have a stone with Seaside loaded from github://GsDevKit/Seaside31:3.1.?/repository and I am loading it now from  'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'.

I am executing this code:

      Metacello new
          baseline: 'Seaside3';
          repository: 'github://GsDevKit/Seaside31:3.1.?/repository';
       unlock.


Metacello new
    baseline: 'Seaside3';
    repository:
    load:
        #('Core' 'Zinc-Seaside' 'Javascript' 'JQuery' 'JSON' 'FastCGI' 'Email');
    onConflict: [ :ex :loaded :incoming | ex useIncoming ];
    onUpgrade: [ :ex :loaded :incoming | ex useIncoming ];
    onWarning: [ :ex | ex resume ];
    version: '3.2.3';
    lock.


And I am still getting the attached error. 

How can I get rid of it? I am already telling it to #useIncoming on conflict, on upgrade....

Thanks in advance



--



--

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

Screen Shot 2017-07-07 at 5.49.28 PM.png (713K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Trying to upgrade from Seaside 3.1 to 3.2 Metacello problem

GLASS mailing list
The code does not even halt on the closure of #onLock: ...

On Fri, Jul 7, 2017 at 5:50 PM, Mariano Martinez Peck <[hidden email]> wrote:
OK, I did a #unregister besides the #unlock to the previous project and now it went a bit further.  But it still fails trying to load Grease...

Sure...I can try to manually unlock the filetree one, but why my code doesn't work?

See attached. 





On Fri, Jul 7, 2017 at 5:36 PM, Mariano Martinez Peck <[hidden email]> wrote:
Hi,

I have a stone with Seaside loaded from github://GsDevKit/Seaside31:3.1.?/repository and I am loading it now from  'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'.

I am executing this code:

      Metacello new
          baseline: 'Seaside3';
          repository: 'github://GsDevKit/Seaside31:3.1.?/repository';
       unlock.


Metacello new
    baseline: 'Seaside3';
    repository:
    load:
        #('Core' 'Zinc-Seaside' 'Javascript' 'JQuery' 'JSON' 'FastCGI' 'Email');
    onConflict: [ :ex :loaded :incoming | ex useIncoming ];
    onUpgrade: [ :ex :loaded :incoming | ex useIncoming ];
    onWarning: [ :ex | ex resume ];
    version: '3.2.3';
    lock.


And I am still getting the attached error. 

How can I get rid of it? I am already telling it to #useIncoming on conflict, on upgrade....

Thanks in advance



--



--



--

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: Trying to upgrade from Seaside 3.1 to 3.2 Metacello problem

GLASS mailing list
OK...sorry, forget about all my emails...I guess I am too tired...



On Fri, Jul 7, 2017 at 5:53 PM, Mariano Martinez Peck <[hidden email]> wrote:
The code does not even halt on the closure of #onLock: ...

On Fri, Jul 7, 2017 at 5:50 PM, Mariano Martinez Peck <[hidden email]> wrote:
OK, I did a #unregister besides the #unlock to the previous project and now it went a bit further.  But it still fails trying to load Grease...

Sure...I can try to manually unlock the filetree one, but why my code doesn't work?

See attached. 





On Fri, Jul 7, 2017 at 5:36 PM, Mariano Martinez Peck <[hidden email]> wrote:
Hi,

I have a stone with Seaside loaded from github://GsDevKit/Seaside31:3.1.?/repository and I am loading it now from  'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'.

I am executing this code:

      Metacello new
          baseline: 'Seaside3';
          repository: 'github://GsDevKit/Seaside31:3.1.?/repository';
       unlock.


Metacello new
    baseline: 'Seaside3';
    repository:
    load:
        #('Core' 'Zinc-Seaside' 'Javascript' 'JQuery' 'JSON' 'FastCGI' 'Email');
    onConflict: [ :ex :loaded :incoming | ex useIncoming ];
    onUpgrade: [ :ex :loaded :incoming | ex useIncoming ];
    onWarning: [ :ex | ex resume ];
    version: '3.2.3';
    lock.


And I am still getting the attached error. 

How can I get rid of it? I am already telling it to #useIncoming on conflict, on upgrade....

Thanks in advance



--



--



--



--

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass