[Glass] Load Seaside30 in GLASS 3.1.0.6
Locked
12
12
Re: [Glass] Load Seaside30 in GLASS 3.1.0.6
 
|
I resubmit the command:
GsDeployer bulkMigrate: [ Metacello new configuration: 'Pier3AddOns'; squeaksource: 'MetacelloRepository'; version: #stable; load. ]. the system erase the error: a MetacelloConflictingProjectError occurred (error 2710), Load Conflict between existing ConfigurationOfMagritte3AddOns 3.0.0 from http://www.squeaksource.com/MetacelloRepository and ConfigurationOfMagritte3AddOns stable from http://www.squeaksource.com/MetacelloRepository - G/S[MeetingRoberta3106:5] AbstractException >> _signalWith: (envId 0) AbstractException >> signal: (envId 0) AbstractException class >> signal: (envId 0) MetacelloAllowConflictingProjectUpgrade >> defaultAction (envId 0) AbstractException >> _signalWith: (envId 0) AbstractException >> signal (envId 0) [] in MetacelloScriptEngine >> lookupProjectSpecFor: (envId 0) [] in MetacelloProjectRegistration class >> registrationForProjectSpec:ifAbsent:ifPresent: (envId 0) [] in MetacelloProjectRegistry >> registrationFor:ifPresent:ifAbsent: (envId 0) AbstractDictionary >> at:ifPresent: (envId 0) MetacelloProjectRegistry >> registrationFor:ifPresent:ifAbsent: (envId 0) MetacelloProjectRegistration class >> registrationForProjectSpec:ifAbsent:ifPresent: (envId 0) MetacelloScriptEngine >> lookupProjectSpecFor: (envId 0) MetacelloScriptEngine >> handleLookupProjectSpecForLoad: (envId 0) MetacelloLookupProjectSpecForLoad >> handleResolutionFor: (envId 0) [] in MetacelloScriptEngine >> handleNotificationsForAction: (envId 0) AbstractException >> _executeHandler: (envId 0) AbstractException >> _signalWith: (envId 0) AbstractException >> signal (envId 0) MetacelloGenericProjectSpec >> load (envId 0) MetacelloProjectReferenceSpec >> loadUsing:gofer: (envId 0) [] in MetacelloCommonMCSpecLoader >> linearLoadPackageSpecs:repositories: (envId 0) Collection >> do: (envId 0) MetacelloCommonMCSpecLoader >> linearLoadPackageSpecs:repositories: (envId 0) [] in MetacelloFetchingMCSpecLoader >> linearLoadPackageSpecs:repositories: (envId 0) ExecBlock >> ensure: (envId 0) MetacelloLoaderPolicy >> pushLoadDirective:during: (envId 0) MetacelloLoaderPolicy >> pushLinearLoadDirectivesDuring:for: (envId 0) MetacelloFetchingMCSpecLoader >> linearLoadPackageSpecs:repositories: (envId 0) MetacelloCommonMCSpecLoader >> load (envId 0) MetacelloMCVersionSpecLoader >> load (envId 0) MetacelloMCVersion >> executeLoadFromArray: (envId 0) [] in MetacelloMCVersion >> fetchRequiredFromArray: (envId 0) [] in MetacelloPlatform >> useStackCacheDuring:defaultDictionary: (envId 0) ExecBlock >> on:do: (envId 0) MetacelloPlatform >> useStackCacheDuring:defaultDictionary: (envId 0) [] in MetacelloMCVersion >> fetchRequiredFromArray: (envId 0) ExecBlock >> ensure: (envId 0) [] in MetacelloMCVersion >> fetchRequiredFromArray: (envId 0) MetacelloPlatform >> do:displaying: (envId 0) MetacelloMCVersion >> fetchRequiredFromArray: (envId 0) [] in MetacelloMCVersion >> doLoadRequiredFromArray: (envId 0) ExecBlock >> ensure: (envId 0) MetacelloMCVersion >> doLoadRequiredFromArray: (envId 0) MetacelloMCVersion >> load (envId 0) [] in MetacelloScriptEngine >> load:onProjectDownGrade:onProjectUpgrade: (envId 0) ExecBlock >> on:do: (envId 0) [] in MetacelloScriptEngine >> handleNotificationsForAction: (envId 0) ExecBlock >> on:do: (envId 0) MetacelloScriptEngine >> handleNotificationsForAction: (envId 0) [] in MetacelloScriptEngine >> load:onProjectDownGrade:onProjectUpgrade: (envId 0) ExecBlock >> ensure: (envId 0) MetacelloProjectRegistration class >> copyRegistryRestoreOnErrorWhile: (envId 0) MetacelloScriptEngine >> load:onProjectDownGrade:onProjectUpgrade: (envId 0) MetacelloScriptEngine >> load: (envId 0) [] in MetacelloScriptExecutor >> execute: (envId 0) [] in MetacelloScriptApiExecutor >> executeString:do: (envId 0) Collection >> do: (envId 0) MetacelloScriptApiExecutor >> executeString:do: (envId 0) String >> execute:against: (envId 0) MetacelloScriptExecutor >> execute: (envId 0) Metacello >> execute (envId 0) Metacello >> load (envId 0) [] in Executed Code (envId 0) [] in GsDeployer >> deploy: (envId 0) ExecBlock >> on:do: (envId 0) [] in GsDeployer >> deploy: (envId 0) [] in MCPlatformSupport class >> commitOnAlmostOutOfMemoryDuring: (envId 0) ExecBlock >> ensure: (envId 0) MCPlatformSupport class >> commitOnAlmostOutOfMemoryDuring: (envId 0) [] in GsDeployer >> mcPlatformSupportDo: (envId 0) ExecBlock >> ensure: (envId 0) GsDeployer >> mcPlatformSupportDo: (envId 0) GsDeployer >> deploy: (envId 0) GsDeployer class >> bulkMigrate: (envId 0) Executed Code String >> evaluateInContext:symbolList: (envId 0) JadeServer >> evaluate:inContext: (envId 0) JadeServer >> printIt:in: (envId 0) GsNMethod class >> _gsReturnToC (envId 0) Any idea ? Thanks, Dario > I changed it. > It was breaking my load scripts here as well... > > The latest version should at least not yield a compiler error now. > > Johan > > On 10 Jun 2014, at 19:31, Dale Henrichs <[hidden email]> wrote: > >> Now the error is that it is using a symbol that does not compile in GemStone: >> >> #pharo4.x >> >> needs to be in GemStone: >> >> #'pharo4.x' >> >> I'm reluctant to make any changes at this minute because Stephan might still be making changes ... you should try explicitly loading ConfigurationOfSeaside3-JohanBrichau.148 into your image and then try doing a load ... the broken configuration was committed this morning at 2:36 in someones timezone:) which probably did not help you in your attempts to load ... >> >> Dale >> >> >> >> On Tue, Jun 10, 2014 at 10:27 AM, Dale Henrichs <[hidden email]> wrote: >> Dario, >> >> I looks like someone is actively changing the ConfiburationOfSeaside3. ConfigurationOfSeaside3-StephanEggermont.150 no longer has that compile error in it .. but I am still getting errors in trying to load into GemStone ... >> >> >> On Tue, Jun 10, 2014 at 10:19 AM, Dale Henrichs <[hidden email]> wrote: >> Well, that is a configuration that cannot be loaded into GemStone ... some one apparently tried to comment out a symbol: >> >> #"pharo3.x" >> >> and that does not compile in gemstone ... surprised that it compiles in pharo ... but it does.. >> >> I'll see if I can find and repair the configuration ... >> >> Dale >> >> >> On Tue, Jun 10, 2014 at 10:15 AM, Dario Trussardi <[hidden email]> wrote: >> Dale, >> >> see the compile error: >> >> Dario >> >>> >>> Dale, >>> >>>> Dario, >>> >>> i resubmit the command: >>> >>> GsDeployer bulkMigrate: [ >>> Metacello new >>> >>> configuration: 'Pier3AddOns'; >>> squeaksource: 'MetacelloRepository'; >>> version: #stable; >>> load. >>> ]. >>> >>> The system answer: >>> >>> a UserDefinedError occurred (error 2318), reason:halt, Compile error in Class: #'ConfigurationOfSeaside3' method: version3102: spec >>> <version: '3.1.0.2' imports: #('3.1.0-baseline' )> >>> >>> spec for: #'common' do: [ >>> spec blessing: #'release'. >>> spec author: 'StephanEggermont'. >>> spec timestamp: '2014-04-07'. >>> spec >>> project: 'Grease' with: #'release1.1'; >>> project: 'Grease Core Tests' with: #'release1.1'; >>> project: 'SPort2' with: '2.33'; >>> project: 'Swazoo2' with: #'stable'; >>> project: 'Zinc Project' with: #'stable'. >>> spec >>> package: 'Seaside-Canvas' with: 'Seaside-Canvas-pmm.127'; >>> package: 'Seaside-Component' with: 'Seaside-Component-pmm.101'; >>> package: 'Seaside-Core' with: 'Seaside-Core-pmm.808'; - G/S[MeetingRoberta3106:5] >>> >>> >>> The relative stack is: >>> >>> AbstractException >> _signalWith: (envId 0) >>> AbstractException >> signal (envId 0) >>> Object >> error: (envId 0) >> 'Compile error in Class: #''ConfigurationOfSeaside3'' method: version3102: spec >> <version: ''3.1.0.2'' imports: #(''3.1.0-baseline'' )> >> >> spec for: #''common'' do: [ >> spec blessing: #''release''. >> spec author: ''StephanEggermont''. >> spec timestamp: ''2014-04-07''. >> spec >> project: ''Grease'' with: #''release1.1''; >> project: ''Grease Core Tests'' with: #''release1.1''; >> project: ''SPort2'' with: ''2.33''; >> project: ''Swazoo2'' with: #''stable''; >> project: ''Zinc Project'' with: #''stable''. >> spec >> package: ''Seaside-Canvas'' with: ''Seaside-Canvas-pmm.127''; >> package: ''Seaside-Component'' with: ''Seaside-Component-pmm.101''; >> package: ''Seaside-Core'' with: ''Seaside-Core-pmm.808''; >> package: ''Seaside-Development'' with: ''Seaside-Development-pmm.163''; >> package: ''Seaside-Email'' with: ''Seaside-Email-pmm.25''; >> package: ''Seaside-Environment'' with: ''Seaside-Environment-pmm.81''; >> package: ''Seaside-Examples'' with: ''Seaside-Examples-pmm.24''; >> package: ''Seaside-Flow'' with: ''Seaside-Flow-pmm.24''; >> package: ''Seaside-InternetExplorer'' with: ''Seaside-InternetExplorer-pmm.7''; >> package: ''Seaside-RenderLoop'' with: ''Seaside-RenderLoop-JohanBrichau.95''; >> package: ''Seaside-Session'' with: ''Seaside-Session-pmm.168''; >> package: ''Seaside-Tools-Core'' with: ''Seaside-Tools-Core-pmm.23''; >> package: ''Seaside-Tools-Web'' with: ''Seaside-Tools-Web-pmm.118''; >> package: ''Seaside-Widgets'' with: ''Seaside-Widgets-pmm.33''; >> package: ''Seaside-Tests-Canvas'' with: ''Seaside-Tests-Canvas-pmm.64''; >> package: ''Seaside-Tests-Component'' with: ''Seaside-Tests-Component-pmm.36''; >> package: ''Seaside-Tests-Core'' with: ''Seaside-Tests-Core-pmm.272''; >> package: ''Seaside-Tests-Development'' with: ''Seaside-Tests-Development-pmm.45''; >> package: ''Seaside-Tests-Email'' with: ''Seaside-Tests-Email-pmm.18''; >> package: ''Seaside-Tests-Environment'' with: ''Seaside-Tests-Environment-pmm.30''; >> package: ''Seaside-Tests-Examples'' with: ''Seaside-Tests-Examples-pmm.11''; >> package: ''Seaside-Tests-Flow'' with: ''Seaside-Tests-Flow-pmm.37''; >> package: ''Seaside-Tests-Functional'' with: ''Seaside-Tests-Functional-pmm.156''; >> package: ''Seaside-Tests-InternetExplorer'' with: ''Seaside-Tests-InternetExplorer-lr.9''; >> package: ''Seaside-Tests-RenderLoop'' with: ''Seaside-Tests-RenderLoop-lr.13''; >> package: ''Seaside-Tests-Session'' with: ''Seaside-Tests-Session-pmm.72''; >> package: ''Seaside-Tests-Tools-Web'' with: ''Seaside-Tests-Tools-Web-pmm.23''; >> package: ''Seaside-Tests-UTF8'' with: ''Seaside-Tests-UTF8-pmm.14''; >> package: ''Javascript-Core'' with: ''Javascript-Core-pmm.95''; >> package: ''Javascript-Tests-Core'' with: ''Javascript-Tests-Core-pmm.71''; >> package: ''JQuery-Core'' with: ''JQuery-Core-pmm.128''; >> package: ''JQuery-Tests-Core'' with: ''JQuery-Tests-Core-pmm.138''; >> package: ''JQuery-JSON'' with: ''JQuery-JSON-pmm.1''; >> package: ''JQuery-Tests-JSON'' with: ''JQuery-Tests-JSON-pmm.1''; >> package: ''JQuery-UI'' with: ''JQuery-UI-pmm.88''; >> package: ''JQuery-Tests-UI'' with: ''JQuery-Tests-UI-pmm.85''; >> package: ''Seaside-FileSystem'' with: ''Seaside-FileSystem-JohanBrichau.27''; >> package: ''Seaside-Tests-FileSystem'' with: ''Seaside-Tests-FileSystem-JohanBrichau.14''; >> package: ''Seaside-JSON-Core'' with: ''Seaside-JSON-Core-pmm.23''; >> package: ''Seaside-Tests-JSON'' with: ''Seaside-Tests-JSON-pmm.11''; >> package: ''RSS-Core'' with: ''RSS-Core-pmm.69''; >> package: ''RSS-Tests-Core'' with: ''RSS-Tests-Core-lr.30''; >> package: ''Seaside-REST-Core'' with: ''Seaside-REST-Core-pmm.52''; >> package: ''Seaside-Tests-REST-Core'' with: ''Seaside-Tests-REST-Core-JohanBrichau.31''; >> package: ''RSS-Examples'' with: ''RSS-Examples-pmm.27''; >> package: ''Zinc-Seaside'' with: ''Zinc-Seaside-SvenVanCaekenberghe.40''; >> package: ''Seaside-Swazoo'' with: ''Seaside-Swazoo-pmm.20''; >> package: ''Seaside-Adaptors-Swazoo'' with: ''Seaside-Adaptors-Swazoo-pmm.44''; >> package: ''Comet-Core'' with: ''Comet-Core-pmm.55''; >> package: ''Comet-Tests-Core'' with: ''Comet-Tests-Core-lr.11''; >> package: ''Comet-Examples'' with: ''Comet-Examples-pmm.26''; >> package: ''Prototype-Core'' with: ''Prototype-Core-pmm.28''; >> package: ''Prototype-Tests-Core'' with: ''Prototype-Tests-Core-pmm.17''; >> package: ''Scriptaculous-Core'' with: ''Scriptaculous-Core-pmm.105''; >> package: ''Scriptaculous-Tests-Core'' with: ''Scriptaculous-Tests-Core-pmm.63''; >> package: ''Scriptaculous-Components'' with: ''Scriptaculous-Components-pmm.114''; >> package: ''Scriptaculous-Tests-Components'' with: ''Scriptaculous-Tests-Components-pmm.42''; >> package: ''Seaside-Welcome'' with: ''Seaside-Welcome-pmm.47''; >> package: ''Seaside-Tests-Welcome'' with: ''Seaside-Tests-Welcome-lr.6''. ]. >> >> spec for: #''gs3.x'' do: [ >> spec >> baseline:''Seaside3'' with: [ spec repository: ''github://glassdb/Seaside31:gemstone3.1/repository'' ]; >> import: ''Seaside3'' >> ]. >> >> spec for: #''squeakCommon'' do: [ >> spec >> project: ''WebClient Project'' with: ''1.5''. >> spec >> package: ''WebClient-Seaside'' with: ''WebClient-Seaside-ar.10''; >> package: ''Seaside-Pharo-Canvas'' with: ''Seaside-Pharo-Canvas-pmm.4''; >> package: ''Seaside-Tests-Pharo-Canvas'' with: ''Seaside-Tests-Pharo-Canvas-pmm.1''; >> package: ''Seaside-Pharo-Continuation'' with: ''Seaside-Pharo-Continuation-lr.5''; >> package: ''Seaside-Pharo-Development'' with: ''Seaside-Pharo-Development-JohanBrichau.66''; >> package: ''Seaside-Pharo-Environment'' with: ''Seaside-Pharo-Environment-lr.6''; >> package: ''Seaside-Pharo-Flow'' with: ''Seaside-Pharo-Flow-lr.5''; >> package: ''Seaside-Tests-Pharo-Continuation'' with: ''Seaside-Tests-Pharo-Continuation-pmm.9''; >> package: ''Seaside-Tests-Pharo-Development'' with: ''Seaside-Tests-Pharo-Development-JohanBrichau.33''; >> package: ''Seaside-Tests-Pharo-Email'' with: ''Seaside-Tests-Pharo-Email-pmm.1''; >> package: ''Seaside-Tests-Pharo-Functional'' with: ''Seaside-Tests-Pharo-Functional-pmm.15''; >> package: ''Seaside-Pharo-JSON-Core'' with: ''Seaside-Pharo-JSON-Core-pmm.2''; >> package: ''Seaside-Tests-Pharo-JSON-Core'' with: ''Seaside-Tests-Pharo-JSON-Core-pmm.1''; >> package: ''Comet-Pharo-Core'' with: ''Comet-Pharo-Core-lr.6''. ]. >> >> spec for: #(#''squeak'' #''pharo1.x'' ) do: [ >> spec project: ''OB'' with: #''stable''. >> spec >> package: ''Seaside-Pharo-Tools-Web'' with: ''Seaside-Pharo-Tools-Web-pmm.49''; >> package: ''Seaside-Pharo-Core'' with: ''Seaside-Pharo-Core-pmm.23''; >> package: ''Seaside-Tests-Pharo-Core'' with: ''Seaside-Tests-Pharo-Core-pmm.30''; >> package: ''Seaside-Tests-Pharo-Functional'' with: ''Seaside-Tests-Pharo-Functional-pmm.15''; >> package: ''Seaside-Pharo-Email'' with: ''Seaside-Pharo-Email-pmm.16''; >> package: ''Seaside-Pharo-REST-Core'' with: ''Seaside-Pharo-REST-Core-pmm.7''; >> package: ''Seaside-Pharo-Tools-OmniBrowser'' with: ''Seaside-Pharo-Tools-OmniBrowser-lr.7''; >> package: ''Seaside-Tools-OmniBrowser'' with: ''Seaside-Tools-OmniBrowser-pmm.29'' ]. >> >> spec for: #''pharo1.x'' do: [ >> spec >> package: ''Seaside-Slime'' with: ''Seaside-Slime-pmm.85''; >> package: ''Seaside-Tests-Slime'' with: ''Seaside-Tests-Slime-pmm.44''; >> package: ''Javascript-Pharo-Core'' with: ''Javascript-Pharo-Core-JohanBrichau.12''; >> package: ''Javascript-Tests-Pharo-Core'' with: ''Javascript-Tests-Pharo-Core-lr.1''; >> package: ''Seaside-Tests-Adaptors-Comanche'' with: ''Seaside-Tests-Adaptors-Comanche-pmm.15'' ]. >> >> spec for: #''pharo2.x'' do: [ >> spec >> package: ''Seaside-Pharo20-Tools-Web'' with: ''Seaside-Pharo20-Tools-Web-JohanBrichau.3''; >> package: ''Seaside-Pharo20-Core'' with: ''Seaside-Pharo20-Core-pmm.3''; >> package: ''Seaside-Tests-Pharo20-Core'' with: ''Seaside-Tests-Pharo20-Core-pmm.4''; >> package: ''Seaside-Pharo-Email'' with: ''Seaside-Pharo-Email-pmm.16''; >> package: ''Seaside-Pharo20-REST-Core'' with: ''Seaside-Pharo20-REST-Core-JohanBrichau.2''; >> package: ''Seaside-Pharo-Tools-Spec'' with: ''Seaside-Pharo-Tools-Spec-pmm.9''; >> package: ''Javascript-Pharo20-Core'' with: ''Javascript-Pharo20-Core-JohanBrichau.4''; >> package: ''Javascript-Tests-Pharo-Core'' with: ''Javascript-Tests-Pharo-Core-lr.1''. ]. >> >> spec for: #(#''pharo3.x'' #pharo4.x) do: [ >> * ^1^2 ******* >> spec >> package: ''Seaside-Pharo20-Tools-Web'' with: ''Seaside-Pharo20-Tools-Web-JohanBrichau.3''; >> package: ''Seaside-Pharo20-Core'' with: ''Seaside-Pharo20-Core-pmm.3''; >> package: ''Seaside-Tests-Pharo20-Core'' with: ''Seaside-Tests-Pharo20-Core-pmm.4''; >> package: ''Seaside-Pharo-Email'' with: ''Seaside-Pharo-Email-pmm.16''; >> package: ''Seaside-Pharo20-REST-Core'' with: ''Seaside-Pharo20-REST-Core-JohanBrichau.2''; >> package: ''Seaside-Pharo-Tools-Spec'' with: ''Seaside-Pharo-Tools-Spec-pmm.9''; >> package: ''Javascript-Pharo20-Core'' with: ''Javascript-Pharo20-Core-JohanBrichau.4''; >> package: ''Javascript-Tests-Pharo-Core'' with: ''Javascript-Tests-Pharo-Core-lr.1''. ]. >> >> spec for: #''pharo'' do: [ >> spec >> project: ''Grease Slime'' with: #''release1.1''; >> project: ''Grease Slime Tests'' with: #''release1.1''. >> spec >> package: ''Seaside-Adaptors-Comanche'' with: ''Seaside-Adaptors-Comanche-pmm.79''; >> package: ''Seaside-Tests-Adaptors-Comanche'' with: ''Seaside-Tests-Adaptors-Comanche-pmm.15''; >> package: ''Seaside-Pharo-Welcome'' with: ''Seaside-Pharo-Welcome-NickAger.2''. ]. >> >> spec for: #''squeak'' do: [ >> spec >> package: ''Seaside-Squeak-Welcome'' with: ''Seaside-Squeak-Welcome-NickAger.1''; >> package: ''Javascript-Pharo-Core'' with: ''Javascript-Pharo-Core-JohanBrichau.12''; >> package: ''Javascript-Tests-Pharo-Core'' with: ''Javascript-Tests-Pharo-Core-lr.1''. ]. >> >> 1: [1013] expected a right parenthesis >> 2: [1034] unexpected token >> >>> >>> Need other informations ? >>> >>> Dario >>> >>>> >>>> I need to see the logs from your failed attempts ... Metacello produces voluminous logging information ... so I suspect that the clues as to what is going wrong is in the logs ... >>>> >>>> The compile error in your second run means there must be some sort of problem in ConfigurationOfSeaside3 (the fact that a compile error is coming from the spec for 3.1.0.2 is why I want to get away from the class based configurations...) >>>> >>>> I suspect that one or more Monticello repository sites are down or slow to respond but without stacks and logging information I can only guess... >>>> >>>> Dale >>>> >>>> >>>> On Tue, Jun 10, 2014 at 9:29 AM, Dario Trussardi <[hidden email]> wrote: >>>> >>>> Dale >>>> >>>>> Dario, >>>>> >>>>> Johan's expression uses `ConfigurationofSeaside` and you are using `ConfigurationOfSeaside30` these are two completely different configurations ... >>>> >>>> If i not wrong i used ConfigurationOfSeaside30 because i need to load not last stable version, but 3.0.8 version >>>> >>>> Into GLASS 3.1.0.4 ( a valid environment ) the ConfigurationOfSeaside30 project currentVersion report: >=3.0.8 [ConfigurationOfSeaside30] >>>> >>>>> Have you tried loading things based on my suggestion using GsDeployer and the Metacello load api? >>>> >>>> I follow your indication: >>>> >>>> GsDeployer bulkMigrate: [ >>>> Metacello new >>>> >>>> configuration: 'Pier3AddOns'; >>>> squeaksource: 'MetacelloRepository'; >>>> version: #stable; >>>> load. >>>> ]. >>>> >>>> but i found some problems. >>>> >>>> i do some test starting whenever from clear GLASS. >>>> >>>> >>>> 1) The first time the system work for some minutes, but when end ( without error ) none package is found in the GLASS >>>> >>>> 2) The second time the system work for eight minutes and after erase the error: >>>> >>>> >>>> a UserDefinedError occurred (error 2318), reason:halt, Compile error in Class: #'ConfigurationOfSeaside3' method: version3102: spec >>>> <version: '3.1.0.2' imports: #('3.1.0-baseline' )> >>>> >>>> 3) the third time the system work for more 50 minutes and other. >>>> >>>> After i interup the command. >>>> >>>> This is all, for now, >>>> >>>> Dario >>>> >>>>> >>>>> >>>>> On Tue, Jun 10, 2014 at 9:14 AM, Dario Trussardi <[hidden email]> wrote: >>>>> Ciao Johan, >>>>> >>>>> >>>>>> For what it's worth: I'm pretty sure you can still load ConfigurationOfSeaside3 in GLASS without the Metacello preview constructs. >>>>>> The following works if you have GLASS 1.0-beta.9 >>>>> >>>>> My GemTools when open the new 3.1.0.6 report GLASS 1.0-beta.9 >>>>> >>>>> >>>>>> (ConfigurationOfSeaside project version: #stable) load >>>>>> >>>>> >>>>> I do this commmand: >>>>> >>>>> A) Gofer it >>>>> squeaksource: 'MetacelloRepository'; >>>>> package: 'ConfigurationOfSeaside30'; >>>>> load. >>>>> >>>>> B) (ConfigurationOfSeaside30 project version: #stable) load >>>>> >>>>> But after some times the system answer: >>>>> >>>>> Error: VM temporary object memory is full >>>>> , almost out of memory, too many markSweeps since last successful scavenge >>>>> >>>>> >>>>> Your indication is same of my hold notes when i setup 3.1.0.4 , in it i load all ( Seaside30 - Magritte - Pier ) >>>>> >>>>> with only the command : >>>>> >>>>> A) Gofer it >>>>> squeaksource: 'MetacelloRepository'; >>>>> package: 'ConfigurationOfPier3AddOns'; >>>>> load >>>>> >>>>> B) ConfigurationOfPier3AddOns load >>>>> >>>>> >>>>> Now what i can do to manage the VM temporary object memory is full. >>>>> >>>>> I need to setup some parameters? >>>>> >>>>> Thanks for any indications, >>>>> >>>>> Dario >>>>> >>>>>> Johan >>>>>> >>>>>> On 10 Jun 2014, at 15:11, Dale Henrichs <[hidden email]> wrote: >>>>>> >>>>>>> The "a MessageNotUnderstood occurred (error 2010), a MetacelloVersionConstructor does not understand #'baseline:with:' - G/S[MeetingRoberta3106:5]" is occurring because you are not using the new Metacello driver: >>>>>>> >>>>>>> GsDeployer bulkMigrate: [ >>>>>>> Metacello new >>>>>>> configuration: 'fPier3AddOns'; >>>>>>> squeaksource: 'MetacelloRepository'; >>>>>>> version: '???'; >>>>>>> load: #('??'). >>>>>>> ]. >>>>>>> >>>>>>> Seaside and other projects have started using features that are only present when the new loading form is used ... >>>>>>> >>>>>>> Gofer Project is a predecessor to the new Metacello loading form ... not sure what the error is there ... >>>>>>> >>>>>>> I should probably delete all of the wiki pages on the ttps://code.google.com/p/glassdb site, but there are links from all of my blog posts and other places that would be broken, but then I should probably delete all of the blog posts, too because they contain obsolete instructions as well ... so I can't do that ... if I am going to rewrite the posts instead the changes I make should refer to tODE ... wait you aren't using tODE yet... >>>>>>> >>>>>>> All I can do is apologize... >>>>>>> >>>>>>> Dale >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Jun 10, 2014 at 5:43 AM, Dario Trussardi <[hidden email]> wrote: >>>>>>> Ciao, >>>>>>> >>>>>>> i do some test. >>>>>>> >>>>>>>> Ciao, >>>>>>>> >>>>>>>> i have a new GLASS 3.1.0.6 image where i need to load **** Seaside30 - Magritte - Pier Package, >>>>>>>> >>>>>>>> In GLASS 3.1.0.4 i load all from Gemtools ( without error ) with the command: >>>>>>>> >>>>>>>> >>>>>>>> A) Gofer it >>>>>>>> squeaksource: 'MetacelloRepository'; >>>>>>>> package: 'ConfigurationOfPier3AddOns'; >>>>>>>> load >>>>>>>> >>>>>>>> B) ConfigurationOfPier3AddOns load >>>>>>>> >>>>>>>> Now when i do B into new GLASS 3.1.0.6 the system erase the error: >>>>>>>> >>>>>>>> Error: VM temporary object memory is full >>>>>>>> , almost out of memory, too many markSweeps since last successful scavenge >>>>>>>> >>>>>>>> >>>>>>>> Can anyone suggest the best method to load All *** >>>>>>> >>>>>>> A) i load Seaside30 with the command: >>>>>>> >>>>>>> MCPlatformSupport commitOnAlmostOutOfMemoryDuring: [ >>>>>>> ConfigurationOfMetacello project updateProject. >>>>>>> ConfigurationOfMetacello loadLatestVersion. >>>>>>> Gofer project load: 'Seaside30'. >>>>>>> ]. >>>>>>> >>>>>>> >>>>>>> B1) After A when i do: >>>>>>> >>>>>>> ConfigurationOfPier3AddOns load >>>>>>> >>>>>>> the system answer: >>>>>>> >>>>>>> a MessageNotUnderstood occurred (error 2010), a MetacelloVersionConstructor does not understand #'baseline:with:' - G/S[MeetingRoberta3106:5] >>>>>>> >>>>>>> MessageNotUnderstood >> defaultAction (envId 0) >>>>>>> AbstractException >> _signalWith: (envId 0) >>>>>>> AbstractException >> signal (envId 0) >>>>>>> Object >> doesNotUnderstand: (envId 0) >>>>>>> Object >> _doesNotUnderstand:args:envId:reason: (envId 0) >>>>>>> [] in ConfigurationOfSeaside3 >> baseline311gemstone: (envId 0) >>>>>>> ExecBlock >> ensure: (envId 0) >>>>>>> MetacelloAbstractVersionConstructor >> with:during: (envId 0) >>>>>>> [] in MetacelloVersionConstructor >> specResolverBlock (envId 0) >>>>>>> Collection >> do: (envId 0) >>>>>>> [] in MetacelloVersionConstructor >> specResolverBlock (envId 0) >>>>>>> Collection >> do: (envId 0) >>>>>>> [] in MetacelloVersionConstructor >> specResolverBlock (envId 0) >>>>>>> [] in MetacelloVersionConstructor >> collectAllVersionsFromVersionPragmasInto:using: (envId 0) >>>>>>> Collection >> do: (envId 0) >>>>>>> [] in MetacelloVersionConstructor >> collectAllVersionsFromVersionPragmasInto:using: (envId 0) >>>>>>> Dictionary >> keysAndValuesDo: (envId 0) >>>>>>> MetacelloVersionConstructor >> collectAllVersionsFromVersionPragmasInto:using: (envId 0) >>>>>>> MetacelloVersionConstructor >> calculate:project: (envId 0) >>>>>>> [] in MetacelloVersionConstructor >> on:project: (envId 0) >>>>>>> [] in MetacelloPlatform >> stackCacheFor:cacheClass:at:doing: (envId 0) >>>>>>> [] in MetacelloPlatform >> useStackCacheDuring:defaultDictionary: (envId 0) >>>>>>> ExecBlock >> on:do: (envId 0) >>>>>>> MetacelloPlatform >> useStackCacheDuring:defaultDictionary: (envId 0) >>>>>>> MetacelloPlatform >> stackCacheFor:cacheClass:at:doing: (envId 0) >>>>>>> MetacelloPlatform >> stackCacheFor:at:doing: (envId 0) >>>>>>> MetacelloVersionConstructor >> on:project: (envId 0) >>>>>>> MetacelloVersionConstructor class >> on:project: (envId 0) >>>>>>> ConfigurationOfSeaside3 >> project (envId 0) >>>>>>> MetacelloMCProjectSpec >> projectClassProject (envId 0) >>>>>>> MetacelloMCProjectSpec >> version (envId 0) >>>>>>> [] in MetacelloMCProjectSpec >> versionOrNil (envId 0) >>>>>>> ExecBlock >> on:do: (envId 0) >>>>>>> MetacelloMCProjectSpec >> versionOrNil (envId 0) >>>>>>> MetacelloProjectReferenceSpec >> versionOrNil (envId 0) >>>>>>> [] in MetacelloMCVersionSpec >> isPartiallyCurrentAgainst: (envId 0) >>>>>>> MetacelloProjectReferenceSpec >> projectDo:packageDo:groupDo: (envId 0) >>>>>>> [] in MetacelloMCVersionSpec >> specsNamed:projectDo:packageDo:groupDo: (envId 0) >>>>>>> Collection >> do: (envId 0) >>>>>>> MetacelloMCVersionSpec >> specsNamed:projectDo:packageDo:groupDo: (envId 0) >>>>>>> MetacelloMCVersionSpec >> isPartiallyCurrentAgainst: (envId 0) >>>>>>> [] in MetacelloProject >> currentVersionAgainst: (envId 0) >>>>>>> Collection >> do: (envId 0) >>>>>>> [] in MetacelloProject >> currentVersionAgainst: (envId 0) >>>>>>> [] in MetacelloPlatform >> stackCacheFor:cacheClass:at:doing: (envId 0) >>>>>>> [] in MetacelloPlatform >> useStackCacheDuring:defaultDictionary: (envId 0) >>>>>>> ExecBlock >> on:do: (envId 0) >>>>>>> MetacelloPlatform >> useStackCacheDuring:defaultDictionary: (envId 0) >>>>>>> MetacelloPlatform >> stackCacheFor:cacheClass:at:doing: (envId 0) >>>>>>> MetacelloPlatform >> stackCacheFor:at:doing: (envId 0) >>>>>>> MetacelloProject >> currentVersionAgainst: (envId 0) >>>>>>> MetacelloMCProjectSpec >> relativeCurrentVersion (envId 0) >>>>>>> MetacelloProjectReferenceSpec >> relativeCurrentVersion (envId 0) >>>>>>> [] in MetacelloMCVersionSpec >> isPartiallyCurrentAgainst: (envId 0) >>>>>>> MetacelloProjectReferenceSpec >> projectDo:packageDo:groupDo: (envId 0) >>>>>>> [] in MetacelloMCVersionSpec >> specsNamed:projectDo:packageDo:groupDo: (envId 0) >>>>>>> Collection >> do: (envId 0) >>>>>>> MetacelloMCVersionSpec >> specsNamed:projectDo:packageDo:groupDo: (envId 0) >>>>>>> MetacelloMCVersionSpec >> isPartiallyCurrentAgainst: (envId 0) >>>>>>> MetacelloMCVersionSpec >> isPartiallyCurrent (envId 0) >>>>>>> [] in MetacelloProject >> currentVersionAgainst: (envId 0) >>>>>>> Collection >> do: (envId 0) >>>>>>> [] in MetacelloProject >> currentVersionAgainst: (envId 0) >>>>>>> [] in MetacelloPlatform >> stackCacheFor:cacheClass:at:doing: (envId 0) >>>>>>> [] in MetacelloPlatform >> useStackCacheDuring:defaultDictionary: (envId 0) >>>>>>> ExecBlock >> on:do: (envId 0) >>>>>>> MetacelloPlatform >> useStackCacheDuring:defaultDictionary: (envId 0) >>>>>>> MetacelloPlatform >> stackCacheFor:cacheClass:at:doing: (envId 0) >>>>>>> MetacelloPlatform >> stackCacheFor:at:doing: (envId 0) >>>>>>> MetacelloProject >> currentVersionAgainst: (envId 0) >>>>>>> [] in MetacelloProject >> currentVersion (envId 0) >>>>>>> [] in MetacelloPlatform >> stackCacheFor:cacheClass:at:doing: (envId 0) >>>>>>> [] in MetacelloPlatform >> useStackCacheDuring:defaultDictionary: (envId 0) >>>>>>> ExecBlock >> on:do: (envId 0) >>>>>>> MetacelloPlatform >> useStackCacheDuring:defaultDictionary: (envId 0) >>>>>>> MetacelloPlatform >> stackCacheFor:cacheClass:at:doing: (envId 0) >>>>>>> MetacelloPlatform >> stackCacheFor:at:doing: (envId 0) >>>>>>> MetacelloProject >> currentVersion (envId 0) >>>>>>> MetacelloMCProjectSpec >> compareCurrentVersion:targetVersionStatus:using: (envId 0) >>>>>>> [] in MetacelloMCVersionSpecLoader >> load (envId 0) >>>>>>> Collection >> do: (envId 0) >>>>>>> MetacelloMCVersionSpecLoader >> load (envId 0) >>>>>>> MetacelloMCVersion >> executeLoadFromArray: (envId 0) >>>>>>> [] in MetacelloMCVersion >> fetchRequiredFromArray: (envId 0) >>>>>>> [] in MetacelloPlatform >> useStackCacheDuring:defaultDictionary: (envId 0) >>>>>>> ExecBlock >> on:do: (envId 0) >>>>>>> MetacelloPlatform >> useStackCacheDuring:defaultDictionary: (envId 0) >>>>>>> [] in MetacelloMCVersion >> fetchRequiredFromArray: (envId 0) >>>>>>> ExecBlock >> ensure: (envId 0) >>>>>>> [] in MetacelloMCVersion >> fetchRequiredFromArray: (envId 0) >>>>>>> MetacelloPlatform >> do:displaying: (envId 0) >>>>>>> MetacelloMCVersion >> fetchRequiredFromArray: (envId 0) >>>>>>> [] in MetacelloMCVersion >> doLoadRequiredFromArray: (envId 0) >>>>>>> ExecBlock >> ensure: (envId 0) >>>>>>> MetacelloMCVersion >> doLoadRequiredFromArray: (envId 0) >>>>>>> MetacelloMCVersion >> load (envId 0) >>>>>>> ConfigurationOfPier3AddOns class >> load (envId 0) >>>>>>> Executed Code >>>>>>> String >> evaluateInContext:symbolList: (envId 0) >>>>>>> JadeServer >> evaluate:inContext: (envId 0) >>>>>>> JadeServer >> printIt:in: (envId 0) >>>>>>> GsNMethod class >> _gsReturnToC (envId 0) >>>>>>> >>>>>>> >>>>>>> B2) if i do: >>>>>>> >>>>>>> MCPlatformSupport commitOnAlmostOutOfMemoryDuring: [ >>>>>>> ConfigurationOfMetacello project updateProject. >>>>>>> ConfigurationOfMetacello loadLatestVersion. >>>>>>> Gofer project load: 'ConfigurationOfPier3AddOns'. >>>>>>> ]. >>>>>>> >>>>>>> the system answer: >>>>>>> >>>>>>> >>>>>>> a UserDefinedError occurred (error 2318), reason:halt, Project not found - G/S[MeetingRoberta3106:5] >>>>>>> >>>>>>> AbstractException >> _signalWith: (envId 0) >>>>>>> AbstractException >> signal (envId 0) >>>>>>> Object >> error: (envId 0) >>>>>>> [] in GoferProjectLoader >> findRepositoryContaining: (envId 0) >>>>>>> SequenceableCollection >> detect:ifNone: (envId 0) >>>>>>> GoferProjectLoader >> findRepositoryContaining: (envId 0) >>>>>>> GoferProjectLoader >> findOrCreateProject: (envId 0) >>>>>>> GoferProjectLoader >> load:version:group: (envId 0) >>>>>>> GoferProjectLoader >> load:version: (envId 0) >>>>>>> GoferProjectLoader >> load: (envId 0) >>>>>>> [] in Executed Code (envId 0) >>>>>>> [] in MCPlatformSupport class >> commitOnAlmostOutOfMemoryDuring: (envId 0) >>>>>>> ExecBlock >> ensure: (envId 0) >>>>>>> MCPlatformSupport class >> commitOnAlmostOutOfMemoryDuring: (envId 0) >>>>>>> Executed Code >>>>>>> String >> evaluateInContext:symbolList: (envId 0) >>>>>>> JadeServer >> evaluate:inContext: (envId 0) >>>>>>> JadeServer >> printIt:in: (envId 0) >>>>>>> GsNMethod class >> _gsReturnToC (envId 0) >>>>>>> >>>>>>> >>>>>>> where projectString is set to: ConfigurationOfPier3AddOns >>>>>>> >>>>>>> >>>>>>> Thanks for any considerations. >>>>>>> >>>>>>> Dario >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Glass mailing list >>>>>>> [hidden email] >>>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Glass mailing list >>>>>>> [hidden email] >>>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Glass mailing list >>>>> [hidden email] >>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass >>>>> >>>> >>>> >>> >>> _______________________________________________ >>> Glass mailing list >>> [hidden email] >>> http://lists.gemtalksystems.com/mailman/listinfo/glass >> >> >> >> >> _______________________________________________ >> Glass mailing list >> [hidden email] >> http://lists.gemtalksystems.com/mailman/listinfo/glass > _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Load Seaside30 in GLASS 3.1.0.6
|
|
Dario, In an earlier message I asked you to send me the list of projects and versions that you have loaded in your working 3.1.0.2 image ... could we please start there? ... If I have the list of projects/versions that work for you in the 3.1.0.2, I can actually attempt to create a load script myself that duplicates your 3.1.0.2 setup and identify first hand the issues .. I am handicapped by not knowing the versions that "work in 3.1.0.2".
If a load script worked two months ago there is no guarantee that the same script will give you exactly the same results today. As we've seen with the compile error in the seaside configuration, all configurations are in a constant state of flux and those changes are largely being made by folks who aren't ensuring that their changes work in GemStone ...
Unfortunately there is no real defense for that ... except to use git repositories ... with git repositories you can have local git repositories for each project that you are using and those local repositories will only change WHEN YOU ARE READY TO CHANGE and even then through the use of tags, you can guarantee that a load script will always load exactly the same thing .... This type of guarantee is impossible with configurations and packages in public monticello repositories ....
We are not able to use git for all projects, yet. For GLASS we've copied the Seaside3 and Zinc code bases to github, so that we better control change process, plus we can run automated tests on travis-ci to ensure that the projects load correctly in a variety of GemStone versions and that all the tests pass). The same thing should be done for the Magritte and Pier code bases ... ultimately this is the correct solution for a stable build environment.
Until then we have to slog through the configurations and fix the new problems with old scripts every time we attempt a load:( Regarding the "conflicting version" from Metacello, that is one of the features of the new api and the following expression can be used to say that you want to allow the load of all conflicting versions:
GsDeployer bulkMigrate: [ Metacello new configuration: 'Pier3AddOns'; squeaksource: 'MetacelloRepository'; version: #stable; onConflict: [:ex :existing :new | ex allow ]; load. ]. The correct expression for the onConflict: depends upon which version of Magritte you actually want and that depends upon which version of Magritte you have loaded in your working 3.1.0.2 image.
Dale On Tue, Jun 10, 2014 at 10:52 AM, Dario Trussardi <[hidden email]> wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Load Seaside30 in GLASS 3.1.0.6
|
|
Dale,
excuse for my delay but i was busy.
Ok, my stable GLASS is based on 3.1.0.4 the relative Version report is: 1. ConfigurationOfFileTree 1.0.1 #'release' 2. ConfigurationOfGLASS 1.0-beta.9.1 #'development' 3. ConfigurationOfGofer 1.0.5.1 #'release' 4. ConfigurationOfGoferProjectLoader 1.0-alpha2.2 #'development' 5. ConfigurationOfGrease 1.0.8 #'development' 6. ConfigurationOfGsCore 0.248 #'development' 7. ConfigurationOfGsFastCGI 0.235 #'release' 8. ConfigurationOfGsMisc 0.242 #'release' 9. ConfigurationOfGsMonticello 0.244.2 #'release' 10. ConfigurationOfGsOB 0.242.1 #'release' 11. ConfigurationOfGsSIXX 0.3-c.1 #'development' 12. ConfigurationOfGsSqueakCommon 0.9.4 #'release' 13. ConfigurationOfJQueryWidgetBox 2.7 #'development' 14. ConfigurationOfMagritte3 3.0 #'development' 15. ConfigurationOfMagritte3AddOns 3.0.0 #'release' 16. ConfigurationOfMetacello 1.0-beta.32 #'development' 17. ConfigurationOfPier3 3.0.0 #'release' 18. ConfigurationOfPier3AddOns 3.0.3 #'development' 19. ConfigurationOfSeaside30 3.0.8 #'stable' 20. ConfigurationOfSwazoo2 2.2.0.4 #'development' 21. ConfigurationOfTopFeeder 1.0.0 #'release' 22. ConfigurationOfTwitterBootstrap 1.0.1 #'release' 23. ConfigurationOfXMLSupport 1.0.5 #'stable' 24. ConfigurationOfZincHTTPComponents 1.1 #'release'
the error report: a MetacelloConflictingProjectError occurred (error 2710), Load Conflict between existing ConfigurationOfMagritte3AddOns 3.0.0 fromhttp://www.squeaksource.com/MetacelloRepository and ConfigurationOfMagritte3AddOns stable fromhttp://www.squeaksource.com/MetacelloRepository - G/S[MeetingRoberta3106:5] Ciao, thanks, Dario
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Load Seaside30 in GLASS 3.1.0.6
|
|
In reply to this post by Dale Henrichs-3
Dale,
excuse for my delay but i was busy.
Ok, my stable GLASS is based on 3.1.0.4 the relative Version report is: 1. ConfigurationOfFileTree 1.0.1 #'release' 2. ConfigurationOfGLASS 1.0-beta.9.1 #'development' 3. ConfigurationOfGofer 1.0.5.1 #'release' 4. ConfigurationOfGoferProjectLoader 1.0-alpha2.2 #'development' 5. ConfigurationOfGrease 1.0.8 #'development' 6. ConfigurationOfGsCore 0.248 #'development' 7. ConfigurationOfGsFastCGI 0.235 #'release' 8. ConfigurationOfGsMisc 0.242 #'release' 9. ConfigurationOfGsMonticello 0.244.2 #'release' 10. ConfigurationOfGsOB 0.242.1 #'release' 11. ConfigurationOfGsSIXX 0.3-c.1 #'development' 12. ConfigurationOfGsSqueakCommon 0.9.4 #'release' 13. ConfigurationOfJQueryWidgetBox 2.7 #'development' 14. ConfigurationOfMagritte3 3.0 #'development' 15. ConfigurationOfMagritte3AddOns 3.0.0 #'release' 16. ConfigurationOfMetacello 1.0-beta.32 #'development' 17. ConfigurationOfPier3 3.0.0 #'release' 18. ConfigurationOfPier3AddOns 3.0.3 #'development' 19. ConfigurationOfSeaside30 3.0.8 #'stable' 20. ConfigurationOfSwazoo2 2.2.0.4 #'development' 21. ConfigurationOfTopFeeder 1.0.0 #'release' 22. ConfigurationOfTwitterBootstrap 1.0.1 #'release' 23. ConfigurationOfXMLSupport 1.0.5 #'stable' 24. ConfigurationOfZincHTTPComponents 1.1 #'release'
the error report: a MetacelloConflictingProjectError occurred (error 2710), Load Conflict between existing ConfigurationOfMagritte3AddOns 3.0.0 fromhttp://www.squeaksource.com/MetacelloRepository and ConfigurationOfMagritte3AddOns stable fromhttp://www.squeaksource.com/MetacelloRepository - G/S[MeetingRoberta3106:5] Ciao, thanks, Dario
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Load Seaside30 in GLASS 3.1.0.6
|
|
In reply to this post by dario trussardi
Dario, I see that you are using Seaside 3.0.8 ... when I do the load of PierAddOns Seaside3.1 is loaded because of a configuration issue in the Pier addons configuration that causes the "latest version of Seaside" to be loaded because of a Metacello bug an attempt is made to load Seaside 3.1.0.2, but seaside 3.1.0 is broken for GemStone ... I'm looking into a Metacello fix, if I were to "fix metacello" we'd still end up getting Seaside 3.1 loaded and I concerned that the version of Pier you are loading (which is a year old) may not work with Seaside 3.1....
Until you let me know that Seaside 3.1 is okay for your purposes, I will work on figuring out how to keep your load on Seaside 3.0.....BTW, the onConflict: and/or onUpgrade: blocks will be involved so at the end of the day, I will end up giving you a little more complicated Metacello load script:)
Dale On Tue, Jun 10, 2014 at 1:29 PM, Dario Trussardi <[hidden email]> wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Load Seaside30 in GLASS 3.1.0.6
|
|
In reply to this post by dario trussardi
Dale,
The system answer: a MetacelloSymbolicVersionDoesNotExistError occurred (error 2710) - G/S[MeetingRoberta3106:5] AbstractException >> _signalWith: (envId 0) AbstractException >> signal (envId 0) [] in MetacelloProject >> version: (envId 0) Dictionary >> at:ifAbsent: (envId 0) where self is: ConfigurationOfGrease(1.0-alpha1-baseline [ConfigurationOfGrease], 1.0-alpha1 [ConfigurationOfGrease], 1.0-alpha2-baseline [ConfigurationOfGrease], 1.0-alpha2 [ConfigurationOfGrease], 1.0-alpha3 [ConfigurationOfGrease], 1.0-alpha4 [ConfigurationOfGrease], 1.0-alpha5-baseline [ConfigurationOfGrease], 1.0-alpha5.1 [ConfigurationOfGrease], 1.0-alpha6 [ConfigurationOfGrease], 1.0-alpha7-baseline [ConfigurationOfGrease], 1.0-alpha7 [ConfigurationOfGrease], 1.0-alpha8 [ConfigurationOfGrease], 1.0-alpha9 [ConfigurationOfGrease], 1.0-alpha9.1 [ConfigurationOfGrease], 1.0-alpha9.2 [ConfigurationOfGrease], 1.0-alpha9.3-baseline [ConfigurationOfGrease], 1.0-alpha9.3 [ConfigurationOfGrease], 1.0-baseline [ConfigurationOfGrease], 1.0-rc-baseline [ConfigurationOfGrease], 1.0-rc [ConfigurationOfGrease], 1.0-rc.1 [ConfigurationOfGrease], 1.0-rc.2 [ConfigurationOfGrease], 1.0 [ConfigurationOfGrease], 1.0.1-baseline [ConfigurationOfGrease], 1.0.1 [ConfigurationOfGrease], 1.0.1.1-baseline [ConfigurationOfGrease], 1.0.1.1 [ConfigurationOfGrease], 1.0.2-baseline [ConfigurationOfGrease], 1.0.2 [ConfigurationOfGrease], 1.0.2.1 [ConfigurationOfGrease], 1.0.3-baseline [ConfigurationOfGrease], 1.0.3 [ConfigurationOfGrease], 1.0.3.1 [ConfigurationOfGrease], 1.0.4-baseline [ConfigurationOfGrease], 1.0.4 [ConfigurationOfGrease], 1.0.5 [ConfigurationOfGrease], 1.0.5.1 [ConfigurationOfGrease], 1.0.6 [ConfigurationOfGrease], 1.0.6.1-baseline [ConfigurationOfGrease], 1.0.6.1 [ConfigurationOfGrease], 1.0.6.2 [ConfigurationOfGrease], 1.0.6.3 [ConfigurationOfGrease], 1.0.6.4 [ConfigurationOfGrease], 1.0.6.5 [ConfigurationOfGrease], 1.0.7 [ConfigurationOfGrease], 1.0.7.1-baseline [ConfigurationOfGrease], 1.0.7.1 [ConfigurationOfGrease], 1.0.7.2 [ConfigurationOfGrease], 1.0.8-baseline [ConfigurationOfGrease], 1.0.8 [ConfigurationOfGrease], 1.1.0-baseline [ConfigurationOfGrease], 1.1.0 [ConfigurationOfGrease], 1.1.1 [ConfigurationOfGrease], 1.1.2 [ConfigurationOfGrease], 1.1.3-baseline [ConfigurationOfGrease], 1.1.3 [ConfigurationOfGrease], ) MetacelloProject >> version: (envId 0) where version is : #'release1.1' MetacelloMCProjectSpec >> version (envId 0) MetacelloProjectSpec >> canUpgradeTo: (envId 0) MetacelloMCProjectSpec >> canUpgradeTo: (envId 0) MetacelloProjectRegistration >> canUpgradeTo: (envId 0) [] in MetacelloScriptEngine >> lookupProjectSpecFor: (envId 0) [] in MetacelloProjectRegistration class >> registrationForProjectSpec:ifAbsent:ifPresent: (envId 0) [] in MetacelloProjectRegistry >> registrationFor:ifPresent:ifAbsent: (envId 0) AbstractDictionary >> at:ifPresent: (envId 0) MetacelloProjectRegistry >> registrationFor:ifPresent:ifAbsent: (envId 0) MetacelloProjectRegistration class >> registrationForProjectSpec:ifAbsent:ifPresent: (envId 0) MetacelloScriptEngine >> lookupProjectSpecFor: (envId 0) MetacelloScriptEngine >> handleLookupProjectSpec: (envId 0) MetacelloLookupProjectSpec >> handleResolutionFor: (envId 0) Ciao, Dario
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Load Seaside30 in GLASS 3.1.0.6
|
|
Dario, Okay ... that particular problem means that you don't have the right ConfigurationOfGrease loaded ... why don't you let me fiddle with the problems for a bit ... I've got your target configuration versions and I'm peeling back the onion on Metacello and Configuration issuess ...
I'm working under the assumption that you are interested in sticking with Seaside3.0 ... the error you are seeing is likely to be due to going down the Seaside3.1 branch if you are willing to have Seaside3.1 loaded (which is different than the "known to work" Seaside3.0.8) then please let me know ASAP...
Dale On Tue, Jun 10, 2014 at 3:13 PM, Dario Trussardi <[hidden email]> wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Load Seaside30 in GLASS 3.1.0.6
|
|
Dario, I have a formula for successfully loading your "known to work" projects/versions into a 3.1.0.6 image ... I basically locked the following projects/versions and edited the ConfigurationOfNAFileUpload to specify an explicit version for Seaside3 (as the bleeding edge load was causing Seaside 3.1.0.2 to be loaded which is "known not to work in GemStone"). :
14. ConfigurationOfMagritte3 3.0 #'development'
15. ConfigurationOfMagritte3AddOns 3.0.0 #'release'
17. ConfigurationOfPier3 3.0.0 #'release' 18. ConfigurationOfPier3AddOns 3.0.3 #'development'
ConfigurationOfSeaside3 3.0.12 24. ConfigurationOfZincHTTPComponents 1.1 #'release' The only change to those versions is loading Seaside 3.0.12, which is a simple bugfix upgrade over Seaside 3.0.8 which you had loaded ... Right now I am testing in a tODE image that has the latest GLASS1 and Metacello projects loaded, so my next step is to get a formula for loading into a virgin 3.1.0.6 seaside extent .... With this little flurry of activity I am getting a picture of which project/version combinations are "working" together BTW, patching ConfigurationOfNAFileUpload may be all it takes to get Pier to load with Seaside3.1 ... I may give that a try later tonight depending upon how things go ... Of course just because something loads, doesn't mean it works ...
I haven't heard from anyone else who might be using Pier with Seaside3.1 so I can't speak (at this moment) as to whether it "works" or not... If the formula ends up working for, we should publish it on webEditionHome as the formula for Pier ... until we learn whether or not Pier3 works with Seaside3.1...
Dale On Tue, Jun 10, 2014 at 3:56 PM, Dale Henrichs <[hidden email]> wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Load Seaside30 in GLASS 3.1.0.6
|
|
Dario, Here's the script ... GsDeployer bulkMigrate: [ {#('Seaside3' '3.0.13' 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main').
#('ZincHTTPComponents' '1.1' 'http://www.squeaksource.com/ZincHTTPComponents'). #('Magritte3' '3.0' 'http://www.squeaksource.com/MetacelloRepository').
#('Magritte3AddOns' '3.0.0' 'http://www.squeaksource.com/MetacelloRepository'). #('Pier3' '3.0.0' 'http://www.squeaksource.com/MetacelloRepository').
#('Pier3AddOns' '3.0.3' 'http://www.squeaksource.com/MetacelloRepository')} do: [ :ar | | projectName version repository |
projectName := ar at: 1. version := ar at: 2. repository := ar at: 3. Metacello new configuration: projectName; repository: repository;
get. Metacello new configuration: projectName; version: version; repository: repository; onUpgrade: [ :ex :existing :new |
existing locked ifTrue: [ ex disallow ] ifFalse: [ ex allow ] ]; onConflict: [ :ex | ex disallow ]; load.
Metacello new configuration: projectName; version: version; repository: repository; lock ] ] I've tested this against a fresh extent0.seaside.dbf not even GLASS upgraded ... straight load ... I haven't run tests but this has loaded up pretty much what you had in 3.1.0.2... Let me know how it goes for you. Dale On Tue, Jun 10, 2014 at 6:06 PM, Dale Henrichs <[hidden email]> wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Load Seaside30 in GLASS 3.1.0.6
|
|
Ciao Dale,
I run your script and it work well. Very thanks. Some considerations: A) After load your script the `Admin >> doit.. >> Version Report` erase an error: a UserDefinedError occurred (error 2318), reason:halt, Name not found: Base - G/S[MeetingRoberta3106:5] AbstractException >> _signalWith: (envId 0) AbstractException >> signal (envId 0) Object >> error: (envId 0) [] in MetacelloVersionSpec >> resolveToLoadableSpec:forLoad:forMap:packages: (envId 0) [] in MetacelloVersionSpec >> packageNamed:forLoad:forMap:ifAbsent: (envId 0) Dictionary >> at:ifAbsent: (envId 0) where at is: 'Base' aDictionary is: aDictionary( 'Seaside-Tests-REST-Core'->spec name: 'Seaside-Tests-REST-Core'; requires: #('Seaside-REST-Core' 'Seaside-Tests-Core' )., 'REST Tests'->spec name: 'REST Tests'; includes: #('REST' 'Seaside-Tests-REST-Core' )., 'Seaside-Gettext-Core'->spec name: 'Seaside-Gettext-Core'; requires: #('Gettext-Project' 'Seaside-Session' )., 'Seaside3'->spec name: 'Seaside3'; projectReference: [ spec repository: '<a href="github://glassdb/Seaside31:3.1.1-gs31/repository'">github://glassdb/Seaside31:3.1.1-gs31/repository'; repository: '<a href="github://glassdb/Seaside31:gemstone3.1/repository'">github://glassdb/Seaside31:gemstone3.1/repository' ]., 'REST'->spec name: 'REST'; includes: #('Core' 'Seaside-REST-Core' )., 'Gettext-Project'->spec name: 'Gettext-Project'; projectReference: [ spec className: 'ConfigurationOfGettext'; repository: 'http://www.smalltalkhub.com/mc/PharoExtras/Gettext/main' ]., ...) MetacelloVersionSpec >> packageNamed:forLoad:forMap:ifAbsent: (envId 0) MetacelloVersionSpec >> resolveToLoadableSpec:forLoad:forMap:packages: (envId 0) B) in the opt3106/Gemstone/log/ environmentName.log i found this text: SESSION CONFIGURATIONS: The maximun number of current session is 41 Questions: as session is intend the Seaside session ? For now it's all, Thanks, Dario
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Load Seaside30 in GLASS 3.1.0.6
|
|
Dario, I know it was quite an ordeal and I appreciate your patience with the situation ... loads are *supposed* to work without the intervention of the end user and you shouldn't have to become an expert in debugging Metacello load issues either ... I created the lock command in the Metacello Scripting API to be used in just this type of situation where you need to use a particular version of project and you don't want Metacello to automatically upgrade your project out from under you ...
Regarding the version report error ... is it true that you have a package named 'Base - G/S[MeetingRoberta3106:5]'? At first blush I don't see anything fundamentally wrong with that package name, but there must be somewhere in Metacello or the version report code that is not handling the spaces in the name well ... I'll have to dig into this a bit.
The "The maximun number of current session is 41" is a reference to the maximum number of gemstone sessions not seaside sessions (I think that line refers to the default number of sessions when an explicit session count is not specified) ...
Dale
On Wed, Jun 11, 2014 at 1:39 AM, Dario Trussardi <[hidden email]> wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Load Seaside30 in GLASS 3.1.0.6
|
|
Ciao Dale,
Not i don't load any package, the error is erase after load your script. I think Base is relative to: Dictionary >> at:ifAbsent: (envId 0) aDictionary( 'Seaside-Tests-REST-Core'->spec name: 'Seaside-Tests-REST-Core';
What do you intend for gemstone sessions ? Is the Gems open on the database ? Thanks for your help, Dario
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Load Seaside30 in GLASS 3.1.0.6
|
|
On Wed, Jun 11, 2014 at 8:52 AM, Dario Trussardi <[hidden email]> wrote:
Okay, I was confused by the 'Base - G/S[MeetingRoberta3106:5]' in the stack dump ...
gemstone session refers to the number of concurrent logins allowed: mainly topaz processes and gem processes (launched from GemTools for example) pl
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
|
|
In reply to this post by Dale Henrichs-3
Ciao,
i'm interested to understand and work with tODE and i follow the: webEditionHome/docs/install/gettingStartedWithTode.md I download the tODE_0.0.3-p1.4 and the testLogin answer : 'Stone : !TCP@meeting001#server!roberta Stone host : meeting001 GemStone version : 3.1.0.6 cpu kind : x86_64 GLASS version : >=1.0-beta.9 [ConfigurationOfGLASS] Metacello version: >=1.0-beta.32 [ConfigurationOfMetacello] GLASS1 not installed Tode not installed '. After when i do: tODE install on the server the system answer: tode 1 > script --script=installTode
Topez ERROR: Error: Unable to log into server:a MetacelloPackageSpecResolutionError occurred (error 2710)
tode 1 > The Transcript report: Project: Announcements 0.240.1 [0.243]
Project: XML Parser 1.0.5 [1.1.8]
Project: XML-Writer 1.0.4 [1.0.5]
Project: Grease Core 1.0.3 [1.0.9]
Project: System-Digital-Signatures 0.241.1
Project: SMTPMail 0.241.1
Project: UTF8 0.241.1
Project: Change-Notification 0.241
Project: Monticello 0.243
Project: Metacello Tools 1.0-beta.32
Project: FileTree 1.0.1
Project: GsMonticello 0.244.2
Project: Gofer 1.0.5.1
Project: OmniBrowser stable
Project: Gofer Project Loader 1.0-alpha2.2
Project: Gofer Core 1.0.2.1
Project: OB 0.242.1
Project: Release Support 0.243
Project: Grease 1.0.7.2
Project: SqueakCommon 0.9.4
Project: Grease 1.0.7.1
Evaluated -> 1.0-beta.32 [ConfigurationOfMetacello] >> metacelloPrimeRegistryFor10beta32
Evaluated -> 1.0-beta.32 [ConfigurationOfMetacello] >> metacelloPrimeRegistryFor10beta32
Evaluated -> 1.0-alpha2.2 [ConfigurationOfGoferProjectLoader] >> postLoadLoader
...finished 1.0-beta.9.1
No instance migrations performed.
-----Upgrading Metacello to issue_238 branch ... tODE needs the bugfixes in that branch
...RETRY->BaselineOfMetacello
...RETRY->BaselineOfMetacello
gofer repository error: 'GoferRepositoryError: file is too short'...ignoring
...FAILED->BaselineOfMetacello Any considerations? I need to follow the instructions by Tode shell help command ? The other Tode shell command answer: tode 1 > project list
Topez ERROR: Error: Unable to log into server:a CompileError occurred (error 1001), compilation errors -- parameter 1 is error descriptor
tode 1 > man --all Topez ERROR: ValueNotFound: value Transcript not found in WeakValueDictionary Thanks in advanced, Dario _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
|
|
Dario, My comment about "wait you aren't using tODE yet..." was meant to be sarcastic ... tODE is not ready for folks to use yet .... One of the areas that needs work is to get the install instructions up to snuff amongst a few other things... There a couple of developers who've been taking tODE for a spin, but I've been distracted by resolving GLASS issues recently and haven't found the time to focus on getting tODE out the door:(
With that said, and since you've given it a try....and found a new issue... Your transcript output looks significantly different than what I see when I do an install into 3.1.0.5 (and 3.1.0.6 should not be significantly different than 3.1.0.5) ... my transcriptis att end of message[1]...
I'm going to guess that you did not get your ConfigurationOfGLASS updated ... you should have ConfigurationOfGLASS-dkh.232 loaded into the image ... with seaside.gemstone.com forwarding problem I think I'm going to have to change the updateGLASS instructions ...
oddly enough I just checked this morning and seaside.gemstone.com is now redirected to seaside.gemtalksystems.com again ... see the "redirecting" in my transcript .... perhaps that change hasn't propagated to your side of the world yet ...
Nonetheless `ConfigurationOfGLASS project updateProject.` cannot be relied upon to work any more and I will change that script and ask you to try again ... for testing purposes ... If you want to continue to use tODE (assuming we get through the install phase) I should warn you that I still have some changes in store for some of the commands ... I will also ask that you use the tode_st mailing list for discussing tode issues and comments ... when I do a merge to master I send mail to the tode_st list describing the bugfixes and new/changed features and any special instructions ...
I will let you know when I have a new version of the $WE_HOME/dev/tode/server/scripts/upgradeGLASS.ws file ... Dale [1] Loading baseline of BaselineOfTode...
Project: Ston baseline Project: FFI stable [1.7] ...finished baseline -----Upgrading GLASS to 1.0-beta.9.1redirecting to http://seaside.gemtalksystems.com/ss/MetacelloRepository/?C=M;O=D
redirecting to http://seaside.gemtalksystems.com/ss/MetacelloRepository/ConfigurationOfGLASS-dkh.232.mcz
Fetched -> ConfigurationOfGLASS-dkh.232 --- http://seaside.gemstone.com/ss/MetacelloRepository --- http://seaside.gemstone.com/ss/MetacelloRepositoryredirecting to http://seaside.gemtalksystems.com/ss/MetacelloRepository/?C=M;O=D
Loaded -> ConfigurationOfGLASS-dkh.232 --- http://seaside.gemstone.com/ss/MetacelloRepository --- cache Loading 1.0-beta.9.1 of ConfigurationOfGLASS...
Fetched -> ConfigurationOfMetacello-dkh.796 --- http://seaside.gemtalksystems.com/ss/metacello --- http://seaside.gemtalksystems.com/ss/metacello
Loaded -> ConfigurationOfMetacello-dkh.796 --- http://seaside.gemtalksystems.com/ss/metacello --- http://seaside.gemtalksystems.com/ss/metacello
Fetched -> ConfigurationOfGsCore-dkh.297 --- http://seaside.gemtalksystems.com/ss/MetacelloRepository --- http://seaside.gemtalksystems.com/ss/MetacelloRepository
Loaded -> ConfigurationOfGsCore-dkh.297 --- http://seaside.gemtalksystems.com/ss/MetacelloRepository --- http://seaside.gemtalksystems.com/ss/MetacelloRepository
Fetched -> ConfigurationOfGsMonticello-dkh.173 --- http://seaside.gemtalksystems.com/ss/MetacelloRepository --- http://seaside.gemtalksystems.com/ss/MetacelloRepository
Loaded -> ConfigurationOfGsMonticello-dkh.173 --- http://seaside.gemtalksystems.com/ss/MetacelloRepository --- http://seaside.gemtalksystems.com/ss/MetacelloRepository
Fetched -> ConfigurationOfGsSqueakCommon-dkh.25 --- http://seaside.gemtalksystems.com/ss/MetacelloRepository --- http://seaside.gemtalksystems.com/ss/MetacelloRepository
Loaded -> ConfigurationOfGsSqueakCommon-dkh.25 --- http://seaside.gemtalksystems.com/ss/MetacelloRepository --- cache
Fetched -> (nearest) ConfigurationOfMetacello-dkh.796 --- http://seaside.gemtalksystems.com/ss/metacello --- http://seaside.gemtalksystems.com/ss/metacello
Loaded -> ConfigurationOfMetacello-dkh.796 --- http://seaside.gemtalksystems.com/ss/metacello --- http://seaside.gemtalksystems.com/ss/metacello
Fetched -> ConfigurationOfGsMisc-dkh.116 --- http://seaside.gemtalksystems.com/ss/MetacelloRepository --- http://seaside.gemtalksystems.com/ss/MetacelloRepository
Loaded -> ConfigurationOfGsMisc-dkh.116 --- http://seaside.gemtalksystems.com/ss/MetacelloRepository --- http://seaside.gemtalksystems.com/ss/MetacelloRepository
Project: Core 0.248 Fetched -> Core.v3-DaleHenrichs.76 --- http://seaside.gemtalksystems.com/ss/monticello --- http://seaside.gemtalksystems.com/ss/monticello
Fetched -> Bootstrap.v3-DaleHenrichs.230 --- http://seaside.gemtalksystems.com/ss/monticello --- http://seaside.gemtalksystems.com/ss/monticello
Fetched -> Squeak.v3-DaleHenrichs.298 --- http://seaside.gemtalksystems.com/ss/monticello --- http://seaside.gemtalksystems.com/ss/monticello
Project: Monticello 0.244 [0.244.2] Project: Metacello 1.0-beta.32 Fetched -> ConfigurationOfFileTree-dkh.64 --- http://ss3.gemtalksystems.com/ss/FileTree --- http://ss3.gemtalksystems.com/ss/FileTree
Loaded -> ConfigurationOfFileTree-dkh.64 --- http://ss3.gemtalksystems.com/ss/FileTree --- http://ss3.gemtalksystems.com/ss/FileTree
Project: FileTree 1.0.1 Project: Gofer 1.0.5.1 Project: OmniBrowser stable [0.242.1]redirecting to http://seaside.gemtalksystems.com/ss/MetacelloRepository/?C=M;O=D
Fetched -> (nearest) ConfigurationOfGsMisc-dkh.116 --- cache --- cache Loaded -> ConfigurationOfGsMisc-dkh.116 --- cache --- cache Project: Announcements 0.240.1 [0.243]
Project: Metacello Tools 1.0-beta.32 Project: FileTree 1.0.1 Project: Gofer 1.0.5.1 Project: OmniBrowser stable Project: Gofer Project Loader 1.0-alpha2.2 Project: Gofer Core 1.0.2.1
Project: OB 0.242.1 Project: Release Support 0.243 Project: Grease 1.0.7.2 Project: System-Digital-Signatures 0.241.1 Project: SMTPMail 0.241.1 Project: UTF8 0.241.1
Project: SqueakCommon 0.9.4 Project: Grease 1.0.7.1 Evaluated -> Core >> preLoad02322 Starting atomic load Loaded -> Core.v3-DaleHenrichs.76 --- http://seaside.gemtalksystems.com/ss/monticello --- cache
Loaded -> Bootstrap.v3-DaleHenrichs.230 --- http://seaside.gemtalksystems.com/ss/monticello --- cache
Loaded -> Squeak.v3-DaleHenrichs.298 --- http://seaside.gemtalksystems.com/ss/monticello --- cache
Finished atomic load Evaluated -> Squeak >> postLoad233 Evaluated -> 1.0-beta.32 [ConfigurationOfMetacello] >> metacelloPrimeRegistryFor10beta32 Evaluated -> 1.0-beta.32 [ConfigurationOfMetacello] >> metacelloPrimeRegistryFor10beta32
Evaluated -> 1.0-alpha2.2 [ConfigurationOfGoferProjectLoader] >> postLoadLoader ...finished 1.0-beta.9.1 No instance migrations performed.
On Wed, Jun 18, 2014 at 6:57 AM, Dario Trussardi <[hidden email]> wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
|
|
Dario, I have pushed a new version of the upgrade script to github...I am suspicious that there are some seaside.gemstone.com references from the installMetacello.ws script, but since I'm no longer failing I can't be sure that they will cause a problem for you especially since the seaside.gemstone.com restoration may propagate to you before I figure out a fix:)...
I have to get ready to go into the office, so it will be a little while before I can delve any further... Dale
On Wed, Jun 18, 2014 at 8:08 AM, Dale Henrichs <[hidden email]> wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
«
Return to GLASS
|
1 view|%1 views
| Free forum by Nabble | Edit this page |