April 2018 - Pharo-users - lists.pharo.org

Calypso error after clean up

by Hilaire

Hello, I have this error when opening calypso on a P7 image, likely the critic stuff. The image was tightly cleaned. Likely one package was removed and it should not. Any idea which package family to look at Thanks Hilaire -- Dr. Geo http://drgeo.eu

April 3, 2018

Re: [Pharo-users] Howto BaselineOf

by Thierry Goubier

2018-04-03 16:31 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > Probably, but my hands are already full. Mine as well :( I still believe a "release" kind of script could help, associated with a project: update the baselineOf, save everything with a nice commit, tag the commit, done. I would need one for OSProcess, and for the GitFileTree-MergeDriver. But it's kind of specific to the way you package DrGeo, so no single command would fit. Thierry > > > > Le 03/04/2018 Ã 15:52, Thierry Goubier a Ã©crit : >> >> Couldn't you call a bazaar routine to get that information? >> >> Writing a specific method with the version number on each release is a >> bit of a pain, to have practised that before. >> Unless you write a release command that adds the code and do the >> necessary stuff to package the release. >> >> Thierry > > > -- > Dr. Geo > http://drgeo.eu > > >

April 3, 2018

Re: [Pharo-users] Howto BaselineOf

by Hilaire

Probably, but my hands are already full. Le 03/04/2018 Ã 15:52, Thierry Goubier a Ã©critÂ : > Couldn't you call a bazaar routine to get that information? > > Writing a specific method with the version number on each release is a > bit of a pain, to have practised that before. > Unless you write a release command that adds the code and do the > necessary stuff to package the release. > > Thierry -- Dr. Geo http://drgeo.eu

April 3, 2018

Re: [Pharo-users] Howto BaselineOf

by Thierry Goubier

2018-04-03 15:25 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > I don't use github. I will just use a class method returning a version > number. Couldn't you call a bazaar routine to get that information? Writing a specific method with the version number on each release is a bit of a pain, to have practised that before. Unless you write a release command that adds the code and do the necessary stuff to package the release. Thierry > > Le 03/04/2018 Ã 14:14, Thierry Goubier a Ã©crit : >> >> Normally, you should do it via the repository url. If you use tags in >> your repository management and integration >> into Monticello (like filetree and gitfiletree), you can retrieve a >> branch or tag name by scanning the repository >> url: for example, github://XX/DrGeo:18.06/src. > > > -- > Dr. Geo > http://drgeo.eu > > >

April 3, 2018

Re: [Pharo-users] Howto BaselineOf

by Hilaire

I don't use github. I will just use a class method returning a version number. Le 03/04/2018 Ã 14:14, Thierry Goubier a Ã©critÂ : > Normally, you should do it via the repository url. If you use tags in > your repository management and integration > into Monticello (like filetree and gitfiletree), you can retrieve a > branch or tag name by scanning the repository > url: for example, github://XX/DrGeo:18.06/src. -- Dr. Geo http://drgeo.eu

April 3, 2018

Proper Monticello (with Iceberg integration) update

by Juraj Kubelka

Hi! What is the proper updated mechanism on projects stored on GitHub? To be more explicit, the script: Metacello new baseline: #DiscordSt; repository: 'github://JurajKubelka/DiscordSt/src'; load. With the Iceberg integration, it does not work if an older version is already in a Pharo image. Doing pull from the Iceberg UI neither works as the new version may have new packages and new external dependencies. Actually it is also tricky if the Iceberg integration is not involved. I use this script in such scenario: ``` UIManager default informUserDuring: [ :bar | bar label: 'Removing cached DiscordSt repository from github-cache'. bar current: 0. (FileLocator workingDirectory / 'github-cache' / 'JurajKubelka' / 'DiscordSt') ensureDeleteAll. bar label: 'Updating DiscordSt baseline definition'. bar current: 0.33. Iceberg enableMetacelloIntegration ifFalse: [ Gofer new url: 'github://JurajKubelka/DiscordSt/src' asZnUrl; package: 'BaselineOfDiscordSt'; load ]. bar label: 'Updating DiscordSt source files'. bar current: 0.66. Metacello new baseline: #DiscordSt; repository: 'github://JurajKubelka/DiscordSt/src'; onConflict: [:ex | ex allow]; load: #default. bar current: 1 ]. ``` I think I need a script that: 1. updates a local Iceberg repository (if exists) 2. loads new BaselineOfDiscordSt package version to a Pharo image 3. executes the Metacello script. How can I do properly the first two steps when Iceberg is involved? Thanks! Juraj

April 3, 2018

Re: [Pharo-users] Howto BaselineOf

by Thierry Goubier

Hi Hilaire, 2018-04-03 12:40 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > Ok, adding the package names was needed in the baseline and resolved the > remaining errors: > > spec package: 'DrGeoII-core'; package: 'DrGeoII-Polymorph'; etc. > > Now I would like to insert in the BaselineOf a version number more > meaningfull than <baseline> > > I want to extract from 'BaselineOfDrGeo project version' an object with a > DrGeo release number (aka 18.06, etc.) > > How can I insert it in the BaselineOfDrGeo? Normally, you should do it via the repository url. If you use tags in your repository management and integration into Monticello (like filetree and gitfiletree), you can retrieve a branch or tag name by scanning the repository url: for example, github://XX/DrGeo:18.06/src. Thierry > > > Le 03/04/2018 Ã 12:20, Hilaire a Ã©crit : >> >> Moving the BaselineOfDrGeo out of the ConfigurationOfDrGeo package in the >> file based tonel helps to get over this error. More error followed but need >> to be examined. > > > -- > Dr. Geo > http://drgeo.eu > > >

April 3, 2018

Re: [Pharo-users] Howto BaselineOf

by Hilaire

Ok, adding the package names was needed in the baseline and resolved the remaining errors: spec package: 'DrGeoII-core'; package: 'DrGeoII-Polymorph'; etc. Now I would like to insert in the BaselineOf a version number more meaningfull than <baseline> I want to extract from 'BaselineOfDrGeo project version' an object with a DrGeo release number (aka 18.06, etc.) How can I insert it in the BaselineOfDrGeo? Le 03/04/2018 Ã 12:20, Hilaire a Ã©critÂ : > Moving the BaselineOfDrGeo out of the ConfigurationOfDrGeo package in > the file based tonel helps to get over this error. More error followed > but need to be examined. -- Dr. Geo http://drgeo.eu

April 3, 2018

Re: [Pharo-users] Howto BaselineOf

by Hilaire

Moving the BaselineOfDrGeo out of the ConfigurationOfDrGeo package in the file based tonel helps to get over this error. More error followed but need to be examined. Le 03/04/2018 Ã 11:42, Hilaire a Ã©critÂ : > Does not work either. > > PharoDebug.log is not updated with this error. I paste bellow the > stack from the debugger (but there is a no attribute values). -- Dr. Geo http://drgeo.eu

April 3, 2018

Re: [Pharo-users] Howto BaselineOf

by Hilaire

Hi Thierry, Does not work either. PharoDebug.log is not updated with this error. I paste bellow the stack from the debugger (but there is a no attribute values). Hilaire MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: [ | references nearestReference cachedReference externalReference mcVersion loadedVersionInfos | cachedReference := nil. packageSpec Â Â Â searchCacheRepositoryForPackage: [ "check to see if mcz file is already in cacheRepository" Â Â Â Â Â Â cachedReference := self Â Â Â Â Â Â Â Â Â resolvePackageSpec: packageSpec Â Â Â Â Â Â Â Â Â cachedGofer: self loaderPolicy cacheGofer. Â Â Â Â Â Â (cachedReference ~~ nil and: [ packageSpec getFile ~~ nil ]) Â Â Â Â Â Â Â Â Â ifTrue: [ cachedReference name = packageSpec file Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â [ "exact match between packageSpec file and cache" ^ self scheduleFetchFor: packageSpec cachedReference: cachedReference ] ] ]. references := self Â Â Â retryingResolvePackageSpecReferences: packageSpec Â Â Â gofer: gofer.Â Â Â "look up mcz file" nearestReference := references last Â Â Â asMetacelloCachingResolvedReference. (cachedReference ~~ nil Â Â Â and: [ cachedReference name = nearestReference name ]) Â Â Â ifTrue: [ "latest reference in repository matches cachedReference ... " Â Â Â Â Â Â ^ self Â Â Â Â Â Â Â Â Â scheduleFetchFor: packageSpec Â Â Â Â Â Â Â Â Â nearestReference: nearestReference ]. (self ignoreImage not Â Â Â and: [ (loadedVersionInfos := self ancestorsFor: packageSpec) ~~ nil ]) Â Â Â ifTrue: [ "If the mcz is already loaded into the image, no need to copy" Â Â Â Â Â Â loadedVersionInfos Â Â Â Â Â Â Â Â Â do: [ :info | Â Â Â Â Â Â Â Â Â Â Â Â info name = nearestReference name Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [ | spc | Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â spc := packageSpec copy. Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â spc file: info name. Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â (MetacelloIgnorePackageLoaded signal: spc) Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [ ^ self ] ] ] ]. externalReference := (references Â Â Â select: [ :ref | ref name = nearestReference name ]) first Â Â Â asMetacelloCachingResolvedReference. self repositoryMap Â Â Â at: externalReference name Â Â Â put: externalReference repository. (self Â Â Â resolveDependencies: externalReference Â Â Â nearest: nearestReference Â Â Â into: (OrderedCollection with: nearestReference)) Â Â Â do: [ :reference | Â Â Â Â Â Â | pSpec l | Â Â Â Â Â Â mcVersion := reference version. Â Â Â Â Â Â (l := (GoferVersionReference name: reference name) Â Â Â Â Â Â Â Â Â resolveAllWith: self loaderPolicy cacheGofer) isEmpty Â Â Â Â Â Â Â Â Â ifTrue: [ self cacheRepository storeVersion: mcVersion. Â Â Â Â Â Â Â Â Â Â Â Â reference == nearestReference Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [ pSpec := packageSpec ] Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [ pSpec := packageSpec project packageSpec. Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â pSpec name: mcVersion package name ]. Â Â Â Â Â Â Â Â Â Â Â Â self loadData Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â addVersion: mcVersion Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â versionInfo: mcVersion info Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â resolvedReference: reference Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â packageSpec: pSpec ] ]. self Â Â Â scheduleFetchFor: packageSpec Â Â Â externalReference: externalReference ] in MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: [ | references nearestReference cachedReference ex...etc... IceMetacelloPharoPlatform(MetacelloPlatform)>>do:displaying: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: MetacelloPackageSpec>>loadUsing:gofer: [ :pkg | pkg loadUsing: self gofer: gofer ] in MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [ :pkg | pkg loadUsing: self gofer: gofer ] Array(SequenceableCollection)>>do: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: [ super Â Â Â linearLoadPackageSpecs: packageSpecs Â Â Â repositories: repositories ] in MetacelloFetchingMCSpecLoader>>explicitLoadPackageSpecs:repositories: in Block: [ super... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushExplicitLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>explicitLoadPackageSpecs:repositories: MetacelloPackageSpec>>explicitLoadUsing: MetacelloPackageSpec>>load [ spec projectPackage load ] in MetacelloScriptEngine>>getBaselineUnconditionalLoad: in Block: [ spec projectPackage load ] BlockClosure>>on:do: MetacelloScriptEngine>>getBaselineUnconditionalLoad: MetacelloScriptEngine>>getBaselineProjectUnconditionalLoad: MetacelloMCBaselineProject>>projectForScriptEngine:unconditionalLoad: MetacelloMCBaselineProject(MetacelloProject)>>projectForScriptEngine: MetacelloMCBaselineOfProjectSpec(MetacelloMCProjectSpec)>>versionForScriptEngine: [ | version loadedSpec | self setDefaultsAndValidateProjectSpec. [ loadedSpec := (self lookupProjectSpecFor: self projectSpec) copy ] Â Â Â on: MetacelloAllowProjectDowngrade , MetacelloAllowProjectUpgrade Â Â Â do: Â Â Â Â Â Â [ :ex | ex handleOnDownGrade: onDownGradeBlock onUpgrade: onUpgradeBlock ]. version := loadedSpec versionForScriptEngine: self. self Â Â Â root: Â Â Â Â Â Â (required isEmpty Â Â Â Â Â Â Â Â Â ifTrue: [ version load ] Â Â Â Â Â Â Â Â Â ifFalse: [ version load: required ]) loadDirective. loadedSpec loads: required. MetacelloProjectRegistration Â Â Â registrationForProjectSpec: loadedSpec Â Â Â ifAbsent: [ :new | Â Â Â Â Â Â new Â Â Â Â Â Â Â Â Â loadedInImage: true; Â Â Â Â Â Â Â Â Â registerProject ] Â Â Â ifPresent: [ :existing :new | Â Â Â Â Â Â existing Â Â Â Â Â Â Â Â Â copyOnWrite: [ :existingCopy | Â Â Â Â Â Â Â Â Â Â Â Â existingCopy Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â loadedInImage: true; Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â merge: new ] ] ] in [ self Â Â Â handleNotificationsForAction: [ | version loadedSpec | Â Â Â Â Â Â self setDefaultsAndValidateProjectSpec. Â Â Â Â Â Â [ loadedSpec := (self lookupProjectSpecFor: self projectSpec) copy ] Â Â Â Â Â Â Â Â Â on: MetacelloAllowProjectDowngrade , MetacelloAllowProjectUpgrade Â Â Â Â Â Â Â Â Â do: Â Â Â Â Â Â Â Â Â Â Â Â [ :ex | ex handleOnDownGrade: onDownGradeBlock onUpgrade: onUpgradeBlock ]. Â Â Â Â Â Â version := loadedSpec versionForScriptEngine: self. Â Â Â Â Â Â self Â Â Â Â Â Â Â Â Â root: Â Â Â Â Â Â Â Â Â Â Â Â (required isEmpty Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [ version load ] Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [ version load: required ]) loadDirective. Â Â Â Â Â Â loadedSpec loads: required. Â Â Â Â Â Â MetacelloProjectRegistration Â Â Â Â Â Â Â Â Â registrationForProjectSpec: loadedSpec Â Â Â Â Â Â Â Â Â ifAbsent: [ :new | Â Â Â Â Â Â Â Â Â Â Â Â new Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â loadedInImage: true; Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â registerProject ] Â Â Â Â Â Â Â Â Â ifPresent: [ :existing :new | Â Â Â Â Â Â Â Â Â Â Â Â existing Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â copyOnWrite: [ :existingCopy | Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â existingCopy Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â loadedInImage: true; Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â merge: new ] ] ] ] in MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade: in Block: [ | version loadedSpec |... BlockClosure>>on:do: [ actionBlock Â Â Â on: Â Â Â Â Â Â MetacelloLookupProjectSpec , MetacelloLookupProjectSpecForLoad Â Â Â Â Â Â Â Â Â , MetacelloProjectSpecLoadedNotification Â Â Â Â Â Â Â Â Â , MetacelloScriptEnsureProjectLoadedForDevelopment Â Â Â Â Â Â Â Â Â , MetacelloLookupBaselineSpecForEnsureLoad Â Â Â do: Â Â Â Â Â Â [ :ex | "lookup and registration handlers need to be innermost set of handlers ...they may throw option notifications" ex handleResolutionFor: self ] ] in [ [ actionBlock Â Â Â on: Â Â Â Â Â Â MetacelloLookupProjectSpec , MetacelloLookupProjectSpecForLoad Â Â Â Â Â Â Â Â Â , MetacelloProjectSpecLoadedNotification Â Â Â Â Â Â Â Â Â , MetacelloScriptEnsureProjectLoadedForDevelopment Â Â Â Â Â Â Â Â Â , MetacelloLookupBaselineSpecForEnsureLoad Â Â Â do: Â Â Â Â Â Â [ :ex | "lookup and registration handlers need to be innermost set of handlers ...they may throw option notifications" ex handleResolutionFor: self ] ] Â Â Â on: Â Â Â Â Â Â MetacelloAllowProjectDowngrade , MetacelloAllowProjectUpgrade Â Â Â Â Â Â Â Â Â , MetacelloAllowConflictingProjectUpgrade Â Â Â do: Â Â Â Â Â Â [ :ex | "option handlers need to be outermost set of handlers ... last line of defense before users are involved" ex handleResolutionFor: self ] ] in [ [ [ actionBlock Â Â Â on: Â Â Â Â Â Â MetacelloLookupProjectSpec , MetacelloLookupProjectSpecForLoad Â Â Â Â Â Â Â Â Â , MetacelloProjectSpecLoadedNotification Â Â Â Â Â Â Â Â Â , MetacelloScriptEnsureProjectLoadedForDevelopment Â Â Â Â Â Â Â Â Â , MetacelloLookupBaselineSpecForEnsureLoad Â Â Â do: Â Â Â Â Â Â [ :ex | "lookup and registration handlers need to be innermost set of handlers ...they may throw option notifications" ex handleResolutionFor: self ] ] Â Â Â on: Â Â Â Â Â Â MetacelloAllowProjectDowngrade , MetacelloAllowProjectUpgrade Â Â Â Â Â Â Â Â Â , MetacelloAllowConflictingProjectUpgrade Â Â Â do: Â Â Â Â Â Â [ :ex | "option handlers need to be outermost set of handlers ... last line of defense before users are involved" ex handleResolutionFor: self ] ] Â Â Â on: MetacelloAllowLockedProjectChange Â Â Â do: Â Â Â Â Â Â [ :ex | "MetacelloAllowLockedProjectChange need to be outermost handler ... since it is signaled from second line of handlers" ex handleResolutionFor: self ] ] in MetacelloScriptEngine>>handleNotificationsForAction: in Block: [ actionBlock... BlockClosure>>on:do: [ [ actionBlock Â Â Â on: Â Â Â Â Â Â MetacelloLookupProjectSpec , MetacelloLookupProjectSpecForLoad Â Â Â Â Â Â Â Â Â , MetacelloProjectSpecLoadedNotification Â Â Â Â Â Â Â Â Â , MetacelloScriptEnsureProjectLoadedForDevelopment Â Â Â Â Â Â Â Â Â , MetacelloLookupBaselineSpecForEnsureLoad Â Â Â do: Â Â Â Â Â Â [ :ex | "lookup and registration handlers need to be innermost set of handlers ...they may throw option notifications" ex handleResolutionFor: self ] ] Â Â Â on: Â Â Â Â Â Â MetacelloAllowProjectDowngrade , MetacelloAllowProjectUpgrade Â Â Â Â Â Â Â Â Â , MetacelloAllowConflictingProjectUpgrade Â Â Â do: Â Â Â Â Â Â [ :ex | "option handlers need to be outermost set of handlers ... last line of defense before users are involved" ex handleResolutionFor: self ] ] in [ [ [ actionBlock Â Â Â on: Â Â Â Â Â Â MetacelloLookupProjectSpec , MetacelloLookupProjectSpecForLoad Â Â Â Â Â Â Â Â Â , MetacelloProjectSpecLoadedNotification Â Â Â Â Â Â Â Â Â , MetacelloScriptEnsureProjectLoadedForDevelopment Â Â Â Â Â Â Â Â Â , MetacelloLookupBaselineSpecForEnsureLoad Â Â Â do: Â Â Â Â Â Â [ :ex | "lookup and registration handlers need to be innermost set of handlers ...they may throw option notifications" ex handleResolutionFor: self ] ] Â Â Â on: Â Â Â Â Â Â MetacelloAllowProjectDowngrade , MetacelloAllowProjectUpgrade Â Â Â Â Â Â Â Â Â , MetacelloAllowConflictingProjectUpgrade Â Â Â do: Â Â Â Â Â Â [ :ex | "option handlers need to be outermost set of handlers ... last line of defense before users are involved" ex handleResolutionFor: self ] ] Â Â Â on: MetacelloAllowLockedProjectChange Â Â Â do: Â Â Â Â Â Â [ :ex | "MetacelloAllowLockedProjectChange need to be outermost handler ... since it is signaled from second line of handlers" ex handleResolutionFor: self ] ] in MetacelloScriptEngine>>handleNotificationsForAction: in Block: [ [ actionBlock... BlockClosure>>on:do: [ [ [ actionBlock Â Â Â on: Â Â Â Â Â Â MetacelloLookupProjectSpec , MetacelloLookupProjectSpecForLoad Â Â Â Â Â Â Â Â Â , MetacelloProjectSpecLoadedNotification Â Â Â Â Â Â Â Â Â , MetacelloScriptEnsureProjectLoadedForDevelopment Â Â Â Â Â Â Â Â Â , MetacelloLookupBaselineSpecForEnsureLoad Â Â Â do: Â Â Â Â Â Â [ :ex | "lookup and registration handlers need to be innermost set of handlers ...they may throw option notifications" ex handleResolutionFor: self ] ] Â Â Â on: Â Â Â Â Â Â MetacelloAllowProjectDowngrade , MetacelloAllowProjectUpgrade Â Â Â Â Â Â Â Â Â , MetacelloAllowConflictingProjectUpgrade Â Â Â do: Â Â Â Â Â Â [ :ex | "option handlers need to be outermost set of handlers ... last line of defense before users are involved" ex handleResolutionFor: self ] ] Â Â Â on: MetacelloAllowLockedProjectChange Â Â Â do: Â Â Â Â Â Â [ :ex | "MetacelloAllowLockedProjectChange need to be outermost handler ... since it is signaled from second line of handlers" ex handleResolutionFor: self ] ] in MetacelloScriptEngine>>handleNotificationsForAction: in Block: [ [ [ actionBlock... BlockClosure>>on:do: Le 03/04/2018 Ã 10:51, Thierry Goubier a Ã©critÂ : > Hi Hilaire, > > try > > Metacello new > baseline: 'DrGeo'; > repository: 'tonel://', SmalltalkImage current imageDirectory > pathString, '/src'; > load > > Thierry -- Dr. Geo http://drgeo.eu

April 3, 2018