[Pharo-users] Pharo 8 64 bit image fails to launch

2020-02-19 Thread Michael Burns via Pharo-users 
--- Begin Message ---
I just downloaded Pharo Launcher and downloaded Pharo 8.0 - 64bit (Stable)
I created an image but when I try to run it, I see the below Console entries 
and the process disappears.

Im running Catalina on a MacBookPro.

Console filter : Pharo

default 12:45:28.183485-0600hiddConnection removed: 
IOHIDEventSystemConnection uuid:7B1A1A94-63A2-47C7-BCA6-BCC1D2EB629A pid:44235 
process:Pharo type:Passive entitlements:0x0 caller:HIServices: 
___GetIOHIDEventSystemClient_block_invoke + 26 attributes:(null) inactive:1 
events:0 mask:0x0
default 12:45:28.185375-0600kernel  AGC:: [Pharo pid 44235 non-mux-aware] 
exiting, non-mux-aware app count 0, runtime: 0:46:40.238
default 12:45:28.185501-0600kernel  AGC:: [Pharo pid 44235 mux-aware] 
exiting, non-mux-aware app count 0, runtime: 0:46:40.239
default 12:45:28.185340-0600hiddConnection removed: 
IOHIDEventSystemConnection uuid:12E9BB2B-2602-4885-8303-33C1285F8AA7 pid:44235 
process:Pharo type:Passive entitlements:0x0 caller:HIToolbox: 
___GetIOHIDEventSystemClient_block_invoke + 26 attributes:(null) inactive:1 
events:0 mask:0x0
default 12:45:28.192573-0600runningboardd   Invalidating assertion 
398-200-7609 (target:executable) from originator 200
default 12:45:28.206986-0600mDNSResponder   [R75091] 
DNSServiceCreateConnection STOP PID[44235](Pharo)
default 12:45:28.206883-0600runningboardd   [executable:44235] 
Death sentinel fired!
default 12:45:28.218215-0600loginwindow -[PersistentAppsSupport 
applicationQuit:] | for app:PharoLauncher, _appTrackingState = 2
default 12:45:28.218254-0600loginwindow -[PersistentAppsSupport 
applicationQuit:] | App: PharoLauncher, quit, updating active tracking timer
default 12:45:28.221573-0600runningboardd   Invalidating assertion 
398-200-7463 (target:executable) from originator 200
default 12:45:28.295074-0600runningboardd   [executable:44235] 
Ignoring jetsam update because this process is not memory-managed
default 12:45:28.295213-0600runningboardd   [executable:44235] 
Ignoring suspend because this process is not lifecycle managed
default 12:45:28.295401-0600runningboardd   [executable:44235] 
Ignoring GPU update because this process is not GPU managed
default 12:45:28.308173-0600runningboardd   Removing process: 
[executable:44235]
default 12:45:28.315872-0600runningboardd   Removing assertions for 
terminated process: [executable:44235]
default 12:45:30.214210-0600Finder  Requested application  has 
policy 0, associated category:DH1009 associated sites:(null) equivalent bundle 
identifiers:org.pharo.PharoLauncher
default 12:45:30.755403-0600Finder  Requested application  has 
policy 0, associated category:DH1009 associated sites:(null) equivalent bundle 
identifiers:org.pharo.PharoLauncher
default 12:45:33.211384-0600NotificationCenter  Looking up app info for 
org.pharo.PharoLauncher
default 12:45:33.218892-0600NotificationCenter  Found info for 
org.pharo.PharoLauncher at . app name: 
default 12:45:33.220539-0600loginwindow -[PersistentAppsSupport 
saveLogoutPersistentState:finalSnapshot:] |  previouslyRunningApps: (
{
BackgroundState = 2;
BundleID = "com.apple.safari";
Hide = 0;
Path = "/Applications/Safari.app";
},
{
BackgroundState = 2;
BundleID = "com.apple.finder";
Hide = 0;
Path = "/System/Library/CoreServices/Finder.app";
},
{
BackgroundState = 2;
BundleID = "com.apple.mail";
Hide = 0;
Path = "/System/Applications/Mail.app";
},
{
BackgroundState = 2;
BundleID = "org.pharo.pharolauncher";
Hide = 0;
Path = "/Applications/PharoLauncher.app";
},
{
BackgroundState = 2;
BundleID = "com.apple.systempreferences";
Hide = 0;
Path = "/System/Applications/System Preferences.app";
},
{
BackgroundState = 2;
BundleID = "com.apple.console";
Hide = 0;
Path = "/System/Applications/Utilities/Console.app";
},
{
BackgroundState = 2;
BundleID = "com.apple.activitymonitor";
Hide = 0;
Path = "/System/Applications/Utilities/Activity Monitor.app";
},
{
BackgroundState = 2;
BundleID = "com.agilebits.onepassword4";
Hide = 0;
Path = "/Applications/others/ accounting/1Password 6.app";
},
{
BackgroundState = 2;
BundleID = "com.apple.terminal";
Hide = 0;
Path = "/System/Applications/Utilities/Terminal.app";
},
{
BackgroundState = 3;
BundleID = "org.macosforge.xquartz.x11";
Hide = 0;
Path = "/Applications/Utilities/XQuartz.app";
},
{
BackgroundState = 2;
BundleID = "com.electron.kitematic_(beta)";
Hide = 0;
Path = "/Applications/Kitematic

Re: [Pharo-users] All file accesses get externalCalledFailed exceptions.

2020-04-24 Thread Michael Burns via Pharo-users 
--- Begin Message ---
Thanks Tim!

Problem solved. 

I did as you suggest and added Pharo.app (and Squeak*.app) to the "Files and 
Folders” and tried again.
That resolved the primary issue but when opening File Browser I got a different 
exception referring to /.VolumeIcon.icns not being able to be opened.
The volume was my boot partition and in Catalina that is a readonly filesystem.
I looked at that file with ls and file commands, and it turns out that it was a 
broken link to the same file in the contained Data volume.
The destination does not exist:  
[graphe:/Volumes/Graphe6] Michael% file .VolumeIcon.icns
.VolumeIcon.icns: broken symbolic link to System/Volumes/Data/.VolumeIcon.icns

So, I created an empty file there:

[graphe:/Volumes/Graphe6] Michael% sudo touch .VolumeIcon.icns

And rechecked the link:

[graphe:/Volumes/Graphe6] Michael% file .VolumeIcon.icns
.VolumeIcon.icns: empty


File Browser now opens and lets me navigate around.  

All is well. 


> On Apr 22, 2020, at 5:40 AM, Tim Mackinnon  wrote:
> 
> H Michael- that seems strange, I just tried the following on a Pharo8 with 
> Catalina: 
> 
> OSPlatform current currentWorkingDirectoryPath.
> 
> > /Users/macta/Dev/Smalltalk/Pharo/Pharo 8.0 - 64bit
> 
> I’m using PharoLauncher, although my images are not stored in Documents, but 
> ~/Dev/Smalltalk/Pharo (I adjusted the launcher settings). Not sure if that 
> makes a difference? Or - perhaps you didn’t allow Pharo disk read privileges 
> (that is a new security check in Catalina - see the OSX System Preferences, 
> Security and Privacy, Files and Folders. Mine has a pharo entry with access 
> to Downloads, Documents and Desktop).
> 
> Tim
> 
>> On 22 Apr 2020, at 10:25, Michael Burns via Pharo-users 
>> mailto:pharo-users@lists.pharo.org>> wrote:
>> 
>> 
>> From: Michael Burns mailto:michaelbu...@mac.com>>
>> Subject: All file accesses get externalCalledFailed exceptions.
>> Date: 22 April 2020 at 10:25:56 BST
>> To: Pharo users > <mailto:pharo-users@lists.pharo.org>>
>> 
>> 
>> Newbie to Pharo
>> Just installed the latest 8.0 stable image.
>> Some things work, but anything I do to access any files gets an exception 
>> dealing with getcwd in libc.dylib.
>> 
>> I am running MacOS Catalina.
>> I searched and found the lib.dylib file and it is an alias to another .dylib 
>> file. 
>> 
>> Is there something else I need to install or configure?
>> 
>> 
>> Sent from my iPad
>> 
> 

--- End Message ---

[Pharo-users] All file accesses get externalCalledFailed exceptions.

2020-04-22 Thread Michael Burns via Pharo-users 
--- Begin Message ---
Newbie to Pharo
Just installed the latest 8.0 stable image.
Some things work, but anything I do to access any files gets an exception 
dealing with getcwd in libc.dylib.

I am running MacOS Catalina.
I searched and found the lib.dylib file and it is an alias to another .dylib 
file. 

Is there something else I need to install or configure?


Sent from my iPad--- End Message ---

[Pharo-users] git and Pharo new book...

2020-05-13 Thread Michael Burns via Pharo-users 
--- Begin Message ---


I think we just jumped threads. 
I’m still getting familiar with using this list. 

Cédrick just posted this 
I think in response to my exception  report:
http://forum.world.st/file/t372658/Screen_Shot_2020-05-12_at_2.png

> I just had a quick look. This is cool. 
> I might be missing a use case where I dit a previous fork and I want to use 
> it later in time. I think that’s nice to cover this use case. Do you sync 
> your fork on github ? From iceberg ? Or maybe no sync is possible ?
> 
> Cheers,
> Cedrick 
> 
Assuming that is true here is my response:

I have not done any syncing yet.  I created an empty github repository and was 
trying to add that to Iceberg when this exception.  There is virtually nothing 
in my github repo:
Https://github.com/MichaelKentBurns/FredsLunch-Pharo-iceberg

“trying to use iceberg to coordinate with GitHub repository“


--- End Message ---

[Pharo-users] Cant add local git repo to Iceberg

2020-05-18 Thread Michael Burns via Pharo-users 
--- Begin Message ---
I already have a GitHub repository named FredsLunch-Pharo.
The local clone of that (using shell and git) is

Importing repository from /Users/Michael/Development/gitRepos/FredsLunch-Pharo

> [graphe:~/Development/gitRepos/FredsLunch-Pharo] Michael% git status
> On branch master
> Your branch is up-to-date with 'origin/master'.
> Changes to be committed:
>   (use "git reset HEAD ..." to unstage)
> 
>   modified:   FredsLunch.st
>   new file:   FredsLunchCSV.st
>   new file:   FredsLunchLunch.st
>   new file:   FredsLunchLunchData.st
>   new file:   FredsLunchLunchList.st
>   new file:   FredsLunchMain.st
>   new file:   FredsLunchMember.st
>   new file:   FredsLunchMemberList.st
>   new file:   FredsLunchParticipant.st
>   new file:   FredsLunchTest.st
>   modified:   FredsLunchTests.st
>   new file:   ManifestFredsLunch.st
> 
> Untracked files:
>   (use "git add ..." to include in what will be committed)
> 
>   pharo-local/
> 
> [graphe:~/Development/gitRepos/FredsLunch-Pharo] Michael% pwd
> /Users/Michael/Development/gitRepos/FredsLunch-Pharo
> [graphe:~/Development/gitRepos/FredsLunch-Pharo] Michael% 
> 


The files currently in that repo were the result of doing a fileOut of each of 
the classes in the package.

Now, I’m trying to register that local repository in Iceberg.

After I supply the pathname for the repository and press OK I get an exception 
window.

Copy stack from debug window:   

> FFICallout>>loaderForArgNamed:
> FFICallout>>loaderForArgNamed:indirectIndex:
> FFIVariableArgument>>resolveUsing:
> [ :arg2 | arg2 resolveUsing: arg1 ] in FFIFunctionSpec>>resolveUsing: in 
> Block: [ :arg2 | arg2 resolveUsing: arg1 ]
> OrderedCollection>>do:
> FFIFunctionSpec>>resolveUsing:
> FFICalloutMethodBuilder>>generateMethodFromSpec:
> FFICalloutMethodBuilder>>generate
> FFICalloutMethodBuilder>>build:
> FFICalloutAPI>>function:library:
> FFICalloutAPI>>function:module:
> LGitRepository(LGitExternalObject)>>callUnchecked:options:
> LGitRepository>>repository_open:bare_path:
> [ self
> repository_open: self
> bare_path: self repositoryReference pathString ] in LGitRepository>>open in 
> Block: [ self...
> LGitRepository(LGitExternalObject)>>withReturnHandlerDo:
> LGitRepository>>open
> IceLibgitRepository>>repositoryHandle
> [ | tmp1 |
> self isValid
> ifFalse: [ ^ #() ].
> tmp1 := self repositoryHandle allRemotes.
> ^ tmp1
> collect: [ :arg1 | 
> | tmp3 |
> tmp3 := IceGitRemote name: arg1 remoteName url: arg1 url.
> tmp3
> localRepository: self;
> yourself ] ] in IceLibgitRepository>>remotes in Block: [ | tmp1 |...
> BlockClosure>>on:do:
> IceLibgitRepository>>handleLibgitError:
> IceLibgitRepository>>remotes
> IcePharoPlugin class>>isAvailableFor:
> [ :arg2 | arg2 isAvailableFor: arg1 ] in IcePlugin class>>allAvailableFor: in 
> Block: [ :arg2 | arg2 isAvailableFor: arg1 ]
> OrderedCollection>>select:
> IcePlugin class>>allAvailableFor:
> IcePluginManager>>availablePluginsFor:
> IcePluginManager>>initializeRepository:
> IcePluginManager class>>managerFor:
> IceLibgitRepository(IceRepository)>>pluginManager
> IceRepositoryCreator>>addLocalRepository
> 
> 

If I try to Fuel out the exception I get another exception whose stack looks 
like this:

> File>>openForWrite:
> File>>openForWrite
> File>>writeStream
> File>>writeStreamDo:
> FLPharo7Platform>>fileNamed:writeStreamDo:
> FLSerializer>>serialize:toFileNamed:
> FuelOutStackDebugAction class>>serializeTestFailureContext:toFileNamed:
> FuelOutStackDebugAction>>serializeStack
> FuelOutStackDebugAction>>executeAction
> FuelOutStackDebugAction(DebugAction)>>execute
> [ self execute ] in FuelOutStackDebugAction(DebugAction)>>asGlamourAction in 
> Block: [ self execute ]
> BlockClosure>>glamourValueWithArgs:
> GLMGenericAction(GLMAction)>>actOn:
> GLMGenericAction(GLMAction)>>morphicActOn:
> [ | tmp2 |
> (tmp2 := selector numArgs) = 0
>   ifTrue: [ target perform: selector ]
>   ifFalse: [ tmp2 = arguments size
>   ifTrue: [ target perform: selector withArguments: 
> arguments ]
>   ifFalse: [ target perform: selector withArguments: 
> (arguments copyWith: arg1) ] ].
> self
>   showShortcut;
>   changed ] in ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: in 
> Block: [ | tmp2 |...
> BlockClosure>>ensure:
> CursorWithMask(Cursor)>>showWhile:
> ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent:
> ToggleMenuItemMorph(MenuItemMorph)>>mouseUp:
> ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp:
> MouseButtonEvent>>sentTo:
> ToggleMenuItemMorph(Morph)>>handleEvent:
> MorphicEventDispatcher>>dispatchDefault:with:
> MorphicEventDispatcher>>handleMouseUp:
> MouseButtonEvent>>sentTo:
> [ ^ arg1 sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: in 
> Block: [ ^ arg1 sentTo: self ]
> BlockClosure>>ensure:
> MorphicEventDispatcher>>dispatchEvent:with:
> ToggleMenuItemMorph(Morph)>>processEvent:using:
>

[Pharo-users] Need help putting my Pharo package under source control

2020-05-11 Thread Michael Burns via Pharo-users 
--- Begin Message ---
I read the section in 2018-09-29-UPDATEDPHAROBYEXAMPLE:

"Monticello packages” just after Figure 3-27

I have a smalltalkhub account and created a repository: 
MCHttpRepository
location: 'http://smalltalkhub.com/mc/MichaelKentBurns/FredsLunch/main'
user: ''
password: ‘' 

In Pharo I registered this as a new smalltalkhub repository:
'http://smalltalkhub.com/mc/MichaelKentBurns/FredsLunch/main’

And it shows up in the repository list for my package.

Then I think I’m supposed to poke ‘Save’.
It was kind of sketchy and popped up exception dialogs while I was typing my 
comment, but eventually it worked.

I was able to download the resultant .mcz file and unzip it, then change the ^M 
to newlines to get a readable source.

I’m not really happy about this process.

I would like to actually save this into my GitHub repository.
The document mentioned at the top mentions using git, but just says:

There is a chapter in preparation on how to use Git with Pharo. Request 
it on the Pharo mailing list.

Question 1: Is there such a document?   If so, can you point me to it?

Question 2: Is there a way to fileOut a class, or a package?  


--- End Message ---

Re: [Pharo-users] Pushing to GitHub repository from my iceberg repository is hung (beachball). How do I interrupt the process?

2020-05-23 Thread Michael Burns via Pharo-users 
--- Begin Message ---
Thanks Stéphane:

Sorry I did not answer your questions below earlier.   I often see your mails 
on my iPad while having coffee.
By the time I got to my computer I had forgotten. 

Answers below marked MKB: 

> On May 23, 2020, at 3:48 AM, Stéphane Ducasse  
> wrote:
> 
> Hi michael
> 
> I’m sincerly sad about the bad experience you encounter (especially when I 
> see how stable is the system on my 
> machine — and I’m a bug magnet for any software — everything crashes with me 
> — sadly enough).
> 
>> 
>> I had been following the Developing a simple counter chapter.
>> All was well.
>> I created an iceberg repository and added my Project to it.
>> I committed the sources to git.
>> Still working OK.
>> Then I did a push of all that to my GitHub/MichaelKentBurns/MyCounter 
>> repository.
>> I got a progress bar for the push which never made any progress.  
> 
> Can you tell us what is your OS?
>   version

MKB: MacOS 10.15.4.

>   pharo version

MKB: Pharo 8.0.0
Build information: 
Pharo-8.0.0+build.1124.sha.0932da82f08175e906b0e2a8052120c823374e9f (64 Bit)


> 
> Can you commit from the command line?

MKB: Yes, I’ve used git from a shell and several git Gui clients for years.
I started earlier (before I was introduced to Iceberg) by filing out my classes 
into the top level of a git repo for this project.
Then I can commit and push from there to GitHub

> 
> Are you using ssh or Https?

MKB:  I have probably used ssh, but more likely https.

> 
> If ssh are you using an agent?

MKB: Not sure what you mean.  Not that I’m aware of.

> 
> In Pharo 90 we are about to release a new C binding for libgit because the 
> version we use is .25 and we will get to 1.0. 
> 
>> Instead I got the beachball spinner.  After quite some time I wanted to 
>> interrupt it to see if I could recover, but I could find a way.
>> Eventually I had to force-quit.
> 
> Arg. 
>> 
>> When I restarted my Pharo image, all of that work was lost because I had not 
>> done a save.
> 
> Your code is there. 
> Open the change code. 
> And you can reapply your changes.
> As a general principle the only thing that you can really lose is the method 
> you are editing but did not compile
> (and all your code if you do not have write permissions but this is a bit 
> normal)
> 

MKB: I was able to recover all the changes.  Thanks.

> 
>  
> 
>> 
>> My Question: Is there some way to interrupt such a process?
>> 
>> You should be able to push  where meta is Ctrl / Alt / Command 
>> depending on your OS.
>> i.e. push period and meta keys together.
>> 
>> btw, in Pharo 7 I have been experiencing a few seconds lag before the 
>> debugger appears,
>> such that it seems it didn't work so I end up hammering the  key and 
>> half a dozen debuggers show up.
>> Apart from needing to modify my behaviour, what have other experienced.  
>> I understood there was some work lately to improve responsiveness, so maybe 
>> I move to Pharo 9 soon.
>> 
>> cheers -ben
> 
> 
> Stéphane Ducasse
> http://stephane.ducasse.free.fr  / 
> http://www.pharo.org  
> 03 59 35 87 52
> Assistant: Aurore Dalle 
> FAX 03 59 57 78 50
> TEL 03 59 35 86 16
> S. Ducasse - Inria
> 40, avenue Halley, 
> Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
> Villeneuve d'Ascq 59650
> France
> 

--- End Message ---

Re: [Pharo-users] Pushing to GitHub repository from my iceberg repository is hung (beachball). How do I interrupt the process?

2020-05-23 Thread Michael Burns via Pharo-users 
--- Begin Message ---
Thanks.   Comments below marked MKB:

> On May 23, 2020, at 3:49 AM, Stéphane Ducasse  
> wrote:
> 
> Ok I will that you are
> 
>   P8 
>   sometimes we have to wait for timeout it should be 1 min (from memory). 
>   
>   Can you push from the command line?

MKB: Yes, I have been using git for years.
I am trying to see how Iceberg’s use of git repo differs from what I’m used to.

> 
> S.
> 
>> On 23 May 2020, at 00:16, Michael Burns > > wrote:
>> 
>> 
>> From: Michael Burns mailto:michaelbu...@mac.com>>
>> Subject: Pushing to GitHub repository from my iceberg repository is hung 
>> (beachball). How do I interrupt the process?
>> Date: 23 May 2020 at 00:16:54 CEST
>> To: "pharo-users@lists.pharo.org " 
>> mailto:pharo-users@lists.pharo.org>>
>> Cc: Michael Burns mailto:michaelbu...@mac.com>>
>> 
>> 
>> I had been following the Developing a simple counter chapter.
>> All was well.
>> I created an iceberg repository and added my Project to it.
>> I committed the sources to git.
>> Still working OK.
>> Then I did a push of all that to my GitHub/MichaelKentBurns/MyCounter 
>> repository.
>> I got a progress bar for the push which never made any progress.  
>> Instead I got the beachball spinner.  After quite some time I wanted to 
>> interrupt it to see if I could recover, but I could find a way.
>> Eventually I had to force-quit.
>> 
>> When I restarted my Pharo image, all of that work was lost because I had not 
>> done a save.
>> 
>> My Question: Is there some way to interrupt such a process?
>> 
>> Screen capture attached.
>> 
>> 
>> 
>> 
> 
> 
> Stéphane Ducasse
> http://stephane.ducasse.free.fr  / 
> http://www.pharo.org  
> 03 59 35 87 52
> Assistant: Aurore Dalle 
> FAX 03 59 57 78 50
> TEL 03 59 35 86 16
> S. Ducasse - Inria
> 40, avenue Halley, 
> Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
> Villeneuve d'Ascq 59650
> France
> 

--- End Message ---

Re: [Pharo-users] Moving a Pharo window under Centos

2020-05-25 Thread Michael Burns via Pharo-users 
--- Begin Message ---
Good news on this issue:  

I changed Parallels to Coherence Mode where every window floats free on the Mac 
display.
This problem does not occur in Coherence.

The thinking was that events like Mouse Down and Up are somewhat time sensitive.
My guess is that without Coherence mode windows has more levels of event 
propagation.
The System Browser depends on Pharo,  Pharo depends on Centos, Centos depends 
on Parallels, and finally Parallels depends on MacOS.
I’m guessing that Coherence mode cuts out one or two levels of event 
propagation (maybe Centos and/or Parallels).

Any better interpretation? 

In any case, this problem is no longer an issue for me.


> On May 25, 2020, at 5:12 AM, Stéphane Ducasse  
> wrote:
> 
> Hi michael
> 
> pay attention because parallels is simulating so the crew here got some 
> problems that there are low level difference
> and we had to have a windows machine for real. 
> 
> S. 
>> 
>> 
>> From: Michael Burns mailto:michaelbu...@mac.com>>
>> Subject: Moving a Pharo window under Centos
>> Date: 24 May 2020 at 22:51:54 CEST
>> To: "pharo-users@lists.pharo.org " 
>> mailto:pharo-users@lists.pharo.org>>
>> Cc: Michael Burns mailto:michaelbu...@mac.com>>
>> 
>> 
>> I’m trying out Pharo on Centos.
>> Since I don’t have a spare PC that I can install Centos, I installed on my 
>> Mac under Parallels.
>> 
>> Centos runs fine, and I was able to install latest Pharo 8.0.
>> 
>> With any other windows under Centos I can grab the title bar, move it, then 
>> drop it where I like.
>> However, inside Pharo, any window I grab by the title bar, though it moves 
>> to follow my cursor,  Does not drop when I let up on the mouse.
>> I’m then stuck where all I can do is drag that window around but never drop 
>> it.
>> For some reason when I Cmd-tab away to a Mac App, then move the cursor back 
>> to Pharo it only rarely fixes the problem.
>> 
>> Anybody else run Pharo under Centos, under Parallels?
>> 
>> Anybody else seen this?
>> 
>> Is there a fix or a workaround?
>> 
>> 
>> 
>> 
> 
> 
> Stéphane Ducasse
> http://stephane.ducasse.free.fr  / 
> http://www.pharo.org  
> 03 59 35 87 52
> Assistant: Aurore Dalle 
> FAX 03 59 57 78 50
> TEL 03 59 35 86 16
> S. Ducasse - Inria
> 40, avenue Halley, 
> Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
> Villeneuve d'Ascq 59650
> France
> 

--- End Message ---

[Pharo-users] ExternalLibraryFunction(Object) can't find libgit2.so

2020-05-24 Thread Michael Burns via Pharo-users 
--- Begin Message ---
MacOS —> Parallels -> Centos —> Pharo 8.0

I’m trying to import an empty repository in Iceberg.
I created a repos on GitHub, then made a local clone in Terminal.
Now, when importing I get a progress bar “Importing repository from 
/home/Michael/…
It makes no progress and I immediately get the debugger.

The top of the stack is ExternalLibraryFunction(Object) and the message is:


"
” self

I see that yum has already installed libgit2.x86_64.

But this is looking for the file in Pharo’s vms/80-x64, and it is there:

[michael@localhost /]$ ls -l 
/home/michael/Pharo/vms/80-x64/lib/pharo/5.0-202002121043/libgit2.so
-rw-r--r--. 1 michael michael 3203664 Feb 12 06:07 
/home/michael/Pharo/vms/80-x64/lib/pharo/5.0-202002121043/libgit2.so


Is there a workaround or a fix?
--- End Message ---

[Pharo-users] Moving a Pharo window under Centos

2020-05-24 Thread Michael Burns via Pharo-users 
--- Begin Message ---
I’m trying out Pharo on Centos.
Since I don’t have a spare PC that I can install Centos, I installed on my Mac 
under Parallels.

Centos runs fine, and I was able to install latest Pharo 8.0.

With any other windows under Centos I can grab the title bar, move it, then 
drop it where I like.
However, inside Pharo, any window I grab by the title bar, though it moves to 
follow my cursor,  Does not drop when I let up on the mouse.
I’m then stuck where all I can do is drag that window around but never drop it.
For some reason when I Cmd-tab away to a Mac App, then move the cursor back to 
Pharo it only rarely fixes the problem.

Anybody else run Pharo under Centos, under Parallels?

Anybody else seen this?

Is there a fix or a workaround?


--- End Message ---

Re: [Pharo-users] Moose install

2020-06-04 Thread Michael Burns via Pharo-users 
--- Begin Message ---
Three questions:

1) What is the proper way to undo the Moose that I installed incorrectly?  

2) I’ve found (I think) the GitHub repo for Moose.   
https://github.com/moosetechnology/Moose 
 

Looking closely at the .travis.yml file:

smalltalk:
  - Pharo64-9.0
  - Pharo64-8.0
It looks like it is supported on Pharo 8 or 9.   I’m using 8

3) However, I also see this:


os:
  - linux

Does this mean it only is supported on linux?  


> On Jun 4, 2020, at 3:08 AM, Stéphane Ducasse  
> wrote:
> 
> I do not think that Moose should be loaded like that. 
> you can obtain a build from the launcher and all the code should be hosted on 
> github now. 
> 
> S. 
> 
>> On 3 Jun 2020, at 22:52, Michael Burns > > wrote:
>> 
>> 
>> From: Michael Burns mailto:michaelbu...@mac.com>>
>> Subject: Moose install
>> Date: 3 June 2020 at 22:52:10 CEST
>> To: "pharo-users@lists.pharo.org " 
>> mailto:pharo-users@lists.pharo.org>>
>> 
>> 
>> Pharo 8 on Mac.
>> 
>> I used Pharo Project Catalog to install Moose.
>> 
>> 
>> But, it looks like there were maybe some errors.
>> When I search for Moose in the system browser I find these packages:
>> 
>> ConfigurationOfMoose
>> ConfigurationOfMooseAlgos
>> Moose-Algos-Graph
>> Mose-Algos-Graph-Tests
>> 
>> However, in the Transcript I found a number of  is Undeclared.
>>> And at the end: Error: Cannot resolve symbolic version #release1
>> 
>> On the positive side, testRunner says that all Moose*-Tests test cases pass. 
>> 
>> Am I good?  
>> Or is there something else to do here?
>> On the MooseTechnology page it seems to indicate that the latest version 
>> they have runs on Pharo 7.
>> 
>> ...finished 1.0
>> Fetched -> ConfigurationOfMoose-TudorGirba.364 --- 
>> http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ 
>>  --- 
>> http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ 
>> 
>> Loaded -> ConfigurationOfMoose-TudorGirba.364 --- 
>> http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ 
>>  --- 
>> http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ 
>> 
>> Loading 5.0 of ConfigurationOfMoose...
>> Fetched -> ConfigurationOfPastell-TorstenBergmann.13 --- 
>> http://smalltalkhub.com/mc/PharoExtras/Pastell/main/ 
>>  --- 
>> http://smalltalkhub.com/mc/PharoExtras/Pastell/main/ 
>> 
>> Loaded -> ConfigurationOfPastell-TorstenBergmann.13 --- 
>> http://smalltalkhub.com/mc/PharoExtras/Pastell/main/ 
>>  --- 
>> http://smalltalkhub.com/mc/PharoExtras/Pastell/main/ 
>> 
>> Fetched -> ConfigurationOfPetitParser-AndreiChis.82 --- 
>> http://smalltalkhub.com/mc/Moose/PetitParser/main/ 
>>  --- 
>> http://smalltalkhub.com/mc/Moose/PetitParser/main/ 
>> 
>> Loaded -> ConfigurationOfPetitParser-AndreiChis.82 --- 
>> http://smalltalkhub.com/mc/Moose/PetitParser/main/ 
>>  --- 
>> /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit 
>> (stable)/pharo-local/package-cache
>> Fetched -> ConfigurationOfMetanool-GeorgeGanea.21 --- 
>> http://smalltalkhub.com/mc/Moose/Metanool/main/ 
>>  --- 
>> http://smalltalkhub.com/mc/Moose/Metanool/main/ 
>> 
>> Loaded -> ConfigurationOfMetanool-GeorgeGanea.21 --- 
>> http://smalltalkhub.com/mc/Moose/Metanool/main/ 
>>  --- 
>> /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit 
>> (stable)/pharo-local/package-cache
>> Fetched -> ConfigurationOfGlamour-TudorGirba.225 --- 
>> http://smalltalkhub.com/mc/Moose/Glamour/main/ 
>>  --- 
>> http://smalltalkhub.com/mc/Moose/Glamour/main/ 
>> 
>> Loaded -> ConfigurationOfGlamour-TudorGirba.225 --- 
>> http://smalltalkhub.com/mc/Moose/Glamour/main/ 
>>  --- 
>> /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit 
>> (stable)/pharo-local/package-cache
>> Fetched -> ConfigurationOfGToolkit-GeorgeGanea.97 --- 
>> http://smalltalkhub.com/mc/Moose/GToolkit/main/ 
>>  --- 
>> http://smalltalkhub.com/mc/Moose/GToolkit/main/ 
>> 
>> Loaded -> ConfigurationOfGToolkit-GeorgeGanea.97 --- 
>>

[Pharo-users] Moose install

2020-06-03 Thread Michael Burns via Pharo-users 
--- Begin Message ---
Pharo 8 on Mac.

I used Pharo Project Catalog to install Moose.


But, it looks like there were maybe some errors.
When I search for Moose in the system browser I find these packages:

ConfigurationOfMoose
ConfigurationOfMooseAlgos
Moose-Algos-Graph
Mose-Algos-Graph-Tests

However, in the Transcript I found a number of  is Undeclared.
> And at the end: Error: Cannot resolve symbolic version #release1

On the positive side, testRunner says that all Moose*-Tests test cases pass. 

Am I good?  
Or is there something else to do here?
On the MooseTechnology page it seems to indicate that the latest version they 
have runs on Pharo 7.

...finished 1.0
Fetched -> ConfigurationOfMoose-TudorGirba.364 --- 
http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ --- 
http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/
Loaded -> ConfigurationOfMoose-TudorGirba.364 --- 
http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ --- 
http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/
Loading 5.0 of ConfigurationOfMoose...
Fetched -> ConfigurationOfPastell-TorstenBergmann.13 --- 
http://smalltalkhub.com/mc/PharoExtras/Pastell/main/ --- 
http://smalltalkhub.com/mc/PharoExtras/Pastell/main/
Loaded -> ConfigurationOfPastell-TorstenBergmann.13 --- 
http://smalltalkhub.com/mc/PharoExtras/Pastell/main/ --- 
http://smalltalkhub.com/mc/PharoExtras/Pastell/main/
Fetched -> ConfigurationOfPetitParser-AndreiChis.82 --- 
http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- 
http://smalltalkhub.com/mc/Moose/PetitParser/main/
Loaded -> ConfigurationOfPetitParser-AndreiChis.82 --- 
http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- 
/Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit 
(stable)/pharo-local/package-cache
Fetched -> ConfigurationOfMetanool-GeorgeGanea.21 --- 
http://smalltalkhub.com/mc/Moose/Metanool/main/ --- 
http://smalltalkhub.com/mc/Moose/Metanool/main/
Loaded -> ConfigurationOfMetanool-GeorgeGanea.21 --- 
http://smalltalkhub.com/mc/Moose/Metanool/main/ --- 
/Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit 
(stable)/pharo-local/package-cache
Fetched -> ConfigurationOfGlamour-TudorGirba.225 --- 
http://smalltalkhub.com/mc/Moose/Glamour/main/ --- 
http://smalltalkhub.com/mc/Moose/Glamour/main/
Loaded -> ConfigurationOfGlamour-TudorGirba.225 --- 
http://smalltalkhub.com/mc/Moose/Glamour/main/ --- 
/Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit 
(stable)/pharo-local/package-cache
Fetched -> ConfigurationOfGToolkit-GeorgeGanea.97 --- 
http://smalltalkhub.com/mc/Moose/GToolkit/main/ --- 
http://smalltalkhub.com/mc/Moose/GToolkit/main/
Loaded -> ConfigurationOfGToolkit-GeorgeGanea.97 --- 
http://smalltalkhub.com/mc/Moose/GToolkit/main/ --- 
/Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit 
(stable)/pharo-local/package-cache
Fetched -> ConfigurationOfXMLParser-monty.353 --- 
http://smalltalkhub.com/mc/PharoExtras/XMLParser/main/ --- 
http://smalltalkhub.com/mc/PharoExtras/XMLParser/main/
ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 
(DTDCachingExternalEntityResolver is Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 (XMLAbstractFactory 
is Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 (XMLFileHandle is 
Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 (XMLParserLimits is 
Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 (XMLStreamConverter 
is Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 (XMLClassFinder is 
Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 (XMLClassFinder is 
Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 
(DTDCachingExternalEntityResolver is Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (XMLAbstractFactory 
is Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (XMLFileHandle is 
Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (XMLParserLimits is 
Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 
(XMLStatelessStreamConverter is Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (XMLStreamConverter 
is Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (XMLClassFinder is 
Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (XMLClassFinder is 
Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline321 
(DTDCachingExternalEntityResolver is Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline321 (XMLAbstractFactory 
is Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline321 (XMLFileHandle is 
Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline321 (XMLParserLimits is 
Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline321 
(XMLStatelessStreamConverter is Undeclared)
ConfigurationOfXMLParser>>initializeClassesForGSBaseline321

Re: [Pharo-users] Moose install

2020-06-04 Thread Michael Burns via Pharo-users 
--- Begin Message ---
Are there specific instructions describing how exactly to import a project from 
github?
It may already be there but I have not found it.

My Mac and Centos Pharo images have issues importing repositories from github. 
I can clone it to my machines, but don’t know how to import that repo. 

I’ve tried a lot of different ways and often find that I’m doing it right. 

I’ve tried Iceberg, and the Pharo catalog. 

Sent from my iPad

> On Jun 4, 2020, at 16:35, Stéphane Ducasse  wrote:
> 
> Moose is running on all three platforms. 
> The team is using Pharo 80. 
> Would be good that they reply but there are more on discord. 
> 
> S.
> 
>> On 4 Jun 2020, at 21:30, Michael Burns  wrote:
>> 
>> 
>> From: Michael Burns 
>> Subject: Re: Moose install
>> Date: 4 June 2020 at 21:30:51 CEST
>> To: Stéphane Ducasse 
>> Cc: Michael Burns , "pharo-users@lists.pharo.org" 
>> 
>> 
>> 
>> Three questions:
>> 
>> 1) What is the proper way to undo the Moose that I installed incorrectly?  
>> 
>> 2) I’ve found (I think) the GitHub repo for Moose.   
>> https://github.com/moosetechnology/Moose 
>> 
>> Looking closely at the .travis.yml file:
>> 
>> smalltalk:
>>   - Pharo64-9.0
>>   - Pharo64-8.0
>> It looks like it is supported on Pharo 8 or 9.   I’m using 8
>> 
>> 3) However, I also see this:
>> 
>> 
>> os:
>>   - linux
>> 
>> Does this mean it only is supported on linux?  
>> 
>> 
>>> On Jun 4, 2020, at 3:08 AM, Stéphane Ducasse  
>>> wrote:
>>> 
>>> I do not think that Moose should be loaded like that. 
>>> you can obtain a build from the launcher and all the code should be hosted 
>>> on github now. 
>>> 
>>> S. 
>>> 
 On 3 Jun 2020, at 22:52, Michael Burns  wrote:
 
 
 From: Michael Burns 
 Subject: Moose install
 Date: 3 June 2020 at 22:52:10 CEST
 To: "pharo-users@lists.pharo.org" 
 
 
 Pharo 8 on Mac.
 
 I used Pharo Project Catalog to install Moose.
 
 
 But, it looks like there were maybe some errors.
 When I search for Moose in the system browser I find these packages:
 
 ConfigurationOfMoose
 ConfigurationOfMooseAlgos
 Moose-Algos-Graph
 Mose-Algos-Graph-Tests
 
 However, in the Transcript I found a number of  is Undeclared.
> And at the end: Error: Cannot resolve symbolic version #release1
 
 On the positive side, testRunner says that all Moose*-Tests test cases 
 pass. 
 
 Am I good?  
 Or is there something else to do here?
 On the MooseTechnology page it seems to indicate that the latest version 
 they have runs on Pharo 7.
 
 ...finished 1.0
 Fetched -> ConfigurationOfMoose-TudorGirba.364 --- 
 http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ --- 
 http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/
 Loaded -> ConfigurationOfMoose-TudorGirba.364 --- 
 http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ --- 
 http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/
 Loading 5.0 of ConfigurationOfMoose...
 Fetched -> ConfigurationOfPastell-TorstenBergmann.13 --- 
 http://smalltalkhub.com/mc/PharoExtras/Pastell/main/ --- 
 http://smalltalkhub.com/mc/PharoExtras/Pastell/main/
 Loaded -> ConfigurationOfPastell-TorstenBergmann.13 --- 
 http://smalltalkhub.com/mc/PharoExtras/Pastell/main/ --- 
 http://smalltalkhub.com/mc/PharoExtras/Pastell/main/
 Fetched -> ConfigurationOfPetitParser-AndreiChis.82 --- 
 http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- 
 http://smalltalkhub.com/mc/Moose/PetitParser/main/
 Loaded -> ConfigurationOfPetitParser-AndreiChis.82 --- 
 http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- 
 /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit 
 (stable)/pharo-local/package-cache
 Fetched -> ConfigurationOfMetanool-GeorgeGanea.21 --- 
 http://smalltalkhub.com/mc/Moose/Metanool/main/ --- 
 http://smalltalkhub.com/mc/Moose/Metanool/main/
 Loaded -> ConfigurationOfMetanool-GeorgeGanea.21 --- 
 http://smalltalkhub.com/mc/Moose/Metanool/main/ --- 
 /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit 
 (stable)/pharo-local/package-cache
 Fetched -> ConfigurationOfGlamour-TudorGirba.225 --- 
 http://smalltalkhub.com/mc/Moose/Glamour/main/ --- 
 http://smalltalkhub.com/mc/Moose/Glamour/main/
 Loaded -> ConfigurationOfGlamour-TudorGirba.225 --- 
 http://smalltalkhub.com/mc/Moose/Glamour/main/ --- 
 /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit 
 (stable)/pharo-local/package-cache
 Fetched -> ConfigurationOfGToolkit-GeorgeGanea.97 --- 
 http://smalltalkhub.com/mc/Moose/GToolkit/main/ --- 
 http://smalltalkhub.com/mc/Moose/GToolkit/main/
 Loaded -> ConfigurationOfGToolkit-GeorgeGanea.97 --- 
 http://smalltalkhub.com/mc/Moose/GToolkit/main/ --- 
 /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit 
 (stable)/pharo-local/package-cache

[Pharo-users] Problems installing pharo-launcher or pharo on RaspberryPi

2020-06-02 Thread Michael Burns via Pharo-users 
--- Begin Message ---
Raspberry Pi 4.

I went to pharo.org/download 

And downloaded both PharoLauncher-linux-2.0-x64.zip and pharo-linux-stable.zip.

I extracted them into separate directories.

I believe Pi 4 B is indeed 64 bit, but read somewhere that the Raspian 
installer installs a 32 bit O/S.
I would expect uname to tell me which.
It just says Linux pi 4.19.97-v7l+ #1294 SMP Thu Jan 30 13:21:14 GMT 2020 
armv7l GNU/Linux

Both of these these files extracted say the same thing when I try to run them:

64 bit:
pi@pi:~/Pharo/pharolauncher $ ./pharo-l* 
Error. Could not determine platform's libc path for VM. 
Try forcing $PLATFORMLIBDIR in /home/pi/Pharo/pharolauncher/pharo-vm/pharo, 
based on LIBC_SO.
Please report what works to pharo [vm-dev] mail list.
LIBC_SO=
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
UNAME=Linux pi 4.19.97-v7l+ #1294 SMP Thu Jan 30 13:21:14 GMT 2020 armv7l 
GNU/Linux


 32 bit:
pi@pi:~/Pharo/32 bit/pharo-linux-stable/bin $ ./pharo
Error. Could not determine platform's libc path for VM. 
Try forcing $PLATFORMLIBDIR in ./pharo, based on LIBC_SO.
Please report what works to pharo [vm-dev] mail list.
LIBC_SO=
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
UNAME=Linux pi 4.19.97-v7l+ #1294 SMP Thu Jan 30 13:21:14 GMT 2020 armv7l 
GNU/Linux


Any clues? 


--- End Message ---

[Pharo-users] Creating tests for the TinyBlog tutorial

2021-05-24 Thread Michael Burns via Pharo-users 
In TinyBlogEn-gitc55a88d.pdf on page 11 (2.7 Post Queries):


TestCase subclass: #TBPostTest
   instanceVariableNames: ''
   classVariableNames: ''
   package: 'TinyBlog-Tests'

Every time I save this new class, it ends up in the TinyBlog package, not 
TinyBlog-Tests.

I see that many other packages have *-Tests packages where their tests live.

It seems to test OK so it’s not a stopper for me, but I get an error:
“Test class not in a package with name ending with ‘-Tests’"

I’d like to understand.


I’m running:

Pharo8.0.0
build: 1124, commit: 0932da8

On MacOS 11.3.1. M1 MbPro