- Pharo-dev - lists.pharo.org

Do we kill the catalog?

by Stephane Ducasse

Hi guys What do we do with it? What alternatives? Stef

April 19, 2018

Re: [Pharo-dev] Iceberg and new failure of Metacello github:// URLs

by Esteban Lorenzano

> On 19 Apr 2018, at 08:03, Martin McClure <martin(a)hand2mouse.com> wrote: > > I have a project that depends on OSSubprocess. In the Pharo 7 of a week > ago I could load this by putting in my baseline: > > project: 'OSSubprocess' > with: [ spec > className: #ConfigurationOfOSSubprocess; > versionString: #stable; > repository: > 'github://marianopeck/OSSubprocess:master/repository] > > > but today in build 781 32-bit (my first time trying the new Iceberg GUI) > this no longer works. It fails with > > LGit_GIT_ERROR: error authenticating: no auth sock variable > > It appears to be attempting to clone > 'git@github.com:marianopeck/OSSubprocess.git' which looks like it > *would* be right if it were *my* Github project. But it's not, so it > would want an SSH key to be able to clone that, I guess? > > Normally, if doing a manual clone of this repo, I'd use > 'https://github.com/marianopeck/OSSubprocess.git'. > > Is this a bug? Or is my usage incorrect? What's the approved way of > doing this? yes, metacello should have fallbacked to use HTTPS after failing with SSH (this was working on old version and seems to be lost in current one) problem is reported here: https://github.com/pharo-vcs/iceberg/issues/643 <https://github.com/pharo-vcs/iceberg/issues/643> cheers, Esteban > > Thanks, > > -Martin > > > Stack of error in case it helps someone: > > > > LGitReturnCodeEnum>>handleLGitReturnCode > LGitRepository(LGitExternalObject)>>withReturnHandlerDo: > LGitRepository>>clone:options:to: > LGitRepository>>clone:options: > IceGitScpRemote(IceGitRemote)>>cloneIn:subdirectory: > IceRepositoryCreator>>cloneRepository > [ self validate. > self isCloning > ifTrue: [ self cloneRepository ] > ifFalse: [ self addLocalRepository ] ] in > IceRepositoryCreator>>createRepository in Block: [ self validate.... > BlockClosure>>on:do: > IceRepositoryCreator>>createRepository > [ repository := builder createRepository ] in > MCGitHubRepository(MCGitBasedNetworkRepository)>>createIcebergRepositoryFor: > in Block: [ repository := builder createRepository ] > BlockClosure>>on:do: > MCGitHubRepository(MCGitBasedNetworkRepository)>>createIcebergRepositoryFor: > [ self createIcebergRepositoryFor: remoteUrl ] in > MCGitHubRepository(MCGitBasedNetworkRepository)>>getOrCreateIcebergRepository > in Block: [ self createIcebergRepositoryFor: remoteUrl ] > OrderedCollection(Collection)>>detect:ifFound:ifNone: > OrderedCollection(Collection)>>detect:ifNone: > MCGitHubRepository(MCGitBasedNetworkRepository)>>getOrCreateIcebergRepository > IceGithubRepositoryType>>mcRepository > Iceberg class>>mcRepositoryFor: > IceMetacelloPharoPlatform>>createRepository: > MetacelloMCBaselineProject(MetacelloMCProject)>>createRepository: > MetacelloRepositorySpec>>createRepository > [ aSpec createRepository ] in [ :aSpec | > | description repo | > description := aSpec description. > (repo := repositories > detect: [ :rep | rep description = description ] > ifNone: [ aSpec createRepository ]) ~~ nil > ifTrue: [ repos add: repo ] ] in > MetacelloEnsureFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom:ignoreOverrides: > in Block: [ aSpec createRepository ] > Array(Collection)>>detect:ifFound:ifNone: > Array(Collection)>>detect:ifNone: > [ :aSpec | > | description repo | > description := aSpec description. > (repo := repositories > detect: [ :rep | rep description = description ] > ifNone: [ aSpec createRepository ]) ~~ nil > ifTrue: [ repos add: repo ] ] in > MetacelloEnsureFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom:ignoreOverrides: > in Block: [ :aSpec | ... > Array(SequenceableCollection)>>do: > MetacelloEnsureFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom:ignoreOverrides: > MetacelloEnsureFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom: > MetacelloPackageSpec>>explicitLoadUsing: > MetacelloPackageSpec>>ensureLoadUsing: > >

April 19, 2018

[Pharo 7.0-dev] Build #782: 20712 Review RPackageClassesSynchronisationTest, RPackageExtensionMetâ¦

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #782 was: SUCCESS. The Pull Request #1218 was integrated: "20712 Review RPackageClassesSynchronisationTest, RPackageExtensionMetâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/1218 Issue Url: https://pharo.fogbugz.com/f/cases/20712 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 19, 2018

Iceberg and new failure of Metacello github:// URLs

by Martin McClure

I have a project that depends on OSSubprocess. In the Pharo 7 of a week ago I could load this by putting in my baseline: project: 'OSSubprocess' Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â with: [ spec Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â className: #ConfigurationOfOSSubprocess; Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â versionString: #stable; Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â repository: 'github://marianopeck/OSSubprocess:master/repository] but today in build 781 32-bit (my first time trying the new Iceberg GUI) this no longer works. It fails with LGit_GIT_ERROR: error authenticating: no auth sock variable It appears to be attempting to clone 'git@github.com:marianopeck/OSSubprocess.git' which looks like it *would* be right if it were *my* Github project. But it's not, so it would want an SSH key to be able to clone that, I guess? Normally, if doing a manual clone of this repo, I'd use 'https://github.com/marianopeck/OSSubprocess.git'. Is this a bug? Or is my usage incorrect? What's the approved way of doing this? Thanks, -Martin Stack of error in case it helps someone: LGitReturnCodeEnum>>handleLGitReturnCode LGitRepository(LGitExternalObject)>>withReturnHandlerDo: LGitRepository>>clone:options:to: LGitRepository>>clone:options: IceGitScpRemote(IceGitRemote)>>cloneIn:subdirectory: IceRepositoryCreator>>cloneRepository [ self validate. self isCloning Â Â Â ifTrue: [ self cloneRepository ] Â Â Â ifFalse: [ self addLocalRepository ] ] in IceRepositoryCreator>>createRepository in Block: [ self validate.... BlockClosure>>on:do: IceRepositoryCreator>>createRepository [ repository := builder createRepository ] in MCGitHubRepository(MCGitBasedNetworkRepository)>>createIcebergRepositoryFor: in Block: [ repository := builder createRepository ] BlockClosure>>on:do: MCGitHubRepository(MCGitBasedNetworkRepository)>>createIcebergRepositoryFor: [ self createIcebergRepositoryFor: remoteUrl ] in MCGitHubRepository(MCGitBasedNetworkRepository)>>getOrCreateIcebergRepository in Block: [ self createIcebergRepositoryFor: remoteUrl ] OrderedCollection(Collection)>>detect:ifFound:ifNone: OrderedCollection(Collection)>>detect:ifNone: MCGitHubRepository(MCGitBasedNetworkRepository)>>getOrCreateIcebergRepository IceGithubRepositoryType>>mcRepository Iceberg class>>mcRepositoryFor: IceMetacelloPharoPlatform>>createRepository: MetacelloMCBaselineProject(MetacelloMCProject)>>createRepository: MetacelloRepositorySpec>>createRepository [ aSpec createRepository ] in [ :aSpec | | description repo | description := aSpec description. (repo := repositories Â Â Â detect: [ :rep | rep description = description ] Â Â Â ifNone: [ aSpec createRepository ]) ~~ nil Â Â Â ifTrue: [ repos add: repo ] ] in MetacelloEnsureFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom:ignoreOverrides: in Block: [ aSpec createRepository ] Array(Collection)>>detect:ifFound:ifNone: Array(Collection)>>detect:ifNone: [ :aSpec | | description repo | description := aSpec description. (repo := repositories Â Â Â detect: [ :rep | rep description = description ] Â Â Â ifNone: [ aSpec createRepository ]) ~~ nil Â Â Â ifTrue: [ repos add: repo ] ] in MetacelloEnsureFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom:ignoreOverrides: in Block: [ :aSpec | ... Array(SequenceableCollection)>>do: MetacelloEnsureFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom:ignoreOverrides: MetacelloEnsureFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom: MetacelloPackageSpec>>explicitLoadUsing: MetacelloPackageSpec>>ensureLoadUsing:

April 19, 2018

Re: [Pharo-dev] DelayScheduler cleanup & Bootstrap

by Stephane Ducasse

Thanks Ben this is great to see this happening. Thanks again. Now about your question: I do not know and we should document it better, but everything in the in github bootstrap + the scripts Guillermo is teaching somewhere in France coming friday like me. On Sun, Apr 15, 2018 at 3:19 PM, Ben Coman <btc(a)openinworld.com> wrote: > I am doing a pass to cleanup the DelayScheduler hierarchy. > I'll be refactoring of the hierarchy to aid code understanding > and eliminate redundant instance variables from the original code. > The target structure is.... > DelayNullScheduler -- minimum interface to avoid errors in rest of system (6 > empty methods) > |__DelayBasicScheduler -- fully working sans race protection (equivalent to > Courageous scheduler) > |__DelaySpinScheduler -- plus race protection > > Can someone advise how/where the Bootstrap loads Delay and the > DelaySchedulers? > where the invocation of Delay_class>>#initialize selects the delay > scheduler. > I need to determine whether during transition the Bootstrap might need to > temporarily hop to a different scheduler, > and how to provide the new structure in the Image for operational testing > before switching. > > cheers -ben

April 19, 2018

Hierarchy (roots) of package

by Stephane Ducasse

Hi Given a package I would like to know the classes that are roots of hierarchy inside the package. Do we have something like that? Stef

April 19, 2018

Re: [Pharo-dev] pharo-contribution CI machines out of disk space

by monty

Thanks. I reconfiguring mine to keep fewer anyway. > Sent: Wednesday, April 18, 2018 at 4:02 AM > From: "Christophe Demarey" <christophe.demarey(a)inria.fr> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] pharo-contribution CI machines out of disk space > > > > Le 18 avr. 2018 Ã 09:52, Christophe Demarey <christophe.demarey(a)inria.fr> a Ã©crit : > > > > > >> Le 18 avr. 2018 Ã 05:05, monty <monty2(a)programmer.net> a Ã©crit : > >> > >> Not quite fixed: https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1822/PHARO=30… > >> > >> Should we start reconfiguring jobs to keep fewer builds? > > > > I do not think so. > > The problem here is that the root partition of the slaves are full because /tmp has thousands of zip files that are downloaded by metacello from github. > > There is no problem with job workspace or the number of builds to keep. > > I will define a job running on slaves daily to remove tmp folder content. > > done: https://ci.inria.fr/pharo-contribution/job/temp-folder-cleaner/ > > > >

April 18, 2018

Re: [Pharo-dev] distribute aplication lockdown image

by Ben Coman

On 19 April 2018 at 04:20, Juan <smalltalker.marcelo(a)gmail.com> wrote: > Hi there, > > I write here, to ask what is the best way to distribute an image, > without starting in the development tools, and start a window of my > application. > Perhaps having a look at PhLDeployment in Pharo Launcher would help. http://files.pharo.org/pharo-launcher/ > I think I remember a package called imageLockdown or something like > that, but I can not find it in smalltalkhub, maybe it's in another > repository. > Any response, idea are welcome. > > Thank you > best > > jmdcc > > PS: sorry without this is not the correct list, what would it be? > pharo-users would be the best place. http://lists.pharo.org/mailman/listinfo/pharo-users_lists.pharo.org cheers -ben

April 18, 2018

Re: [Pharo-dev] distribute aplication lockdown image

by BenoÃ®t Verhaeghe

Hi, Maybe this could help you ? https://github.com/VincentBlondeau/Cruiser BenoÃ®t Verhaeghe Le mer. 18 avr. 2018 Ã 22:21, Juan <smalltalker.marcelo(a)gmail.com> a Ã©crit : > Hi there, > > I write here, to ask what is the best way to distribute an image, > without starting in the development tools, and start a window of my > application. > I think I remember a package called imageLockdown or something like > that, but I can not find it in smalltalkhub, maybe it's in another > repository. > Any response, idea are welcome. > > Thank you > best > > jmdcc > > PS: sorry without this is not the correct list, what would it be? > >

April 18, 2018

Re: [Pharo-dev] distribute aplication lockdown image

by Stephane Ducasse

Hi juan this is the correct list. Vincent Blondeau was working on making easier to build application with Pharo. So he may have an asnwer. Stef On Wed, Apr 18, 2018 at 10:20 PM, Juan <smalltalker.marcelo(a)gmail.com> wrote: > Hi there, > > I write here, to ask what is the best way to distribute an image, > without starting in the development tools, and start a window of my > application. > I think I remember a package called imageLockdown or something like > that, but I can not find it in smalltalkhub, maybe it's in another > repository. > Any response, idea are welcome. > > Thank you > best > > jmdcc > > PS: sorry without this is not the correct list, what would it be? >

April 18, 2018