Re: [Pharo-users] What's wrong with latest Pharo?

[Tim Mackinnon]

Oh well - even after modifying that method and trying the remoteTypeSelector: 
trick it insists on giving the iceAuthenticationError - so maybe the libcurl2 
install didn’t work (he said he had to install "libcurl-gnutls” to get that 
far).

Interestingly - my osx setup has suddenly starting giving me an 
IceAuthenticationError in a fresh image (I can’t imagine its related is it? 
Could that repo suddenly have some issue? I had the same error yesterday and 
had to clear out the iceberg-local). It seems that iceberg is still not quite 
as rock solid as we would like.

Tim

> On 30 Apr 2019, at 17:15, Tim Mackinnon  wrote:
> 
> Guille - it looks like modifying that method and :
> "I installed some other package (`libcurl-gnutls`) which is an "addon" to the 
> regular `libcurl`.”
> 
> Got us further - now he’s getting IceAuthenticationError- which could be down 
> to git vs https. (I can use the #remoteTypeSelector: trick to hopefully fix 
> that).
> 
> When I confirm everything, I will report back the magic syntax (at least for 
> Arch) - as well as the desire to back port that fix to 7.
> 
> Thanks for chipping in (and this is the thread that keeps on giving…)
> 
> Tim
> 
>> On 30 Apr 2019, at 16:08, Tim Mackinnon > > wrote:
>> 
>> Actually - the user has confirmed a bit more (which sounds like your hunch 
>> Guille):
>> 
>> Hmm… Just loading the image without `eval`ing something seems to boot up 
>> well. But then I also realise, that there is a warning:
>> 
>> ```ioLoadModule(/opt/pharo/bin/../lib/pharo/5.0-201901231209/libgit2.so):
>>   libcurl-gnutls.so.4: cannot open shared object file: No such file or 
>> directory```
>> (edited)
>> 
>> So this looks like pharo tries to load a bundled libgit2 first during bootup 
>> which fails and only later, when trying to call into it, system resolves 
>> into the system installed one.
>> Which then causes the segfault for some reason.
>> 
>> I’ll see if I can guide him through changing that method.
>> 
>> Tim
>> 
>>> On 30 Apr 2019, at 15:53, Tim Mackinnon >> > wrote:
>>> 
>>> Hi Guille - I’m not using Arch Linux myself - this was a seasoned exercism 
>>> contributor trying to give pharo a spin - and sadly it hasn’t gone well 
>>> (shame as they might have been an advocate) They also commented:
>>> 
>>> "I'm not quite sure though if I really want to continue from here. As 
>>> someone new to pharo, I basically can't find any installation instructions 
>>> that go beyond that evil `curl`. I'm happy to play this to the end with 
>>> you, that at least exercism gets proper instructions, but the pharo 
>>> community really should change their mind and provide more and better 
>>> documentation about systemwide installation and packages. I have a hard 
>>> time seeing something used at my compnay that does not provide an RPM out 
>>> of the box…”
>>> 
>>> Which is fair play.
>>> 
>>> However I did get some details which might salvage something (and maybe 
>>> they can try)
>>> 
>>> Its ArchLinux (apparently there are no versions in Arch, its always the 
>>> latest).
>>> Pharo wa installed via AUR (looks like a bit old - 2019-01-24 18:18) - not 
>>> sure that is the issue though
>>> AUR does give an image so they downloaded the latest 64 bit one from here - 
>>> https://files.pharo.org/image/70/ 
>>> Libgit2 was missing - that was installed (not clear on how - could ask)
>>> 
>>> After all of this - it did launch - they saw a welcome screen then it 
>>> crashed (I think they were doing our eval string to metacello load exercism 
>>> - so it would then use libgit2)
>>> 
>>> They then got this error:
>>> https://pastebin.com/W2D86ZS4 
>>> 
>>> I’ve pasted the error below - for prosperity.
>>> 
>>> Tim
>>> 
>>> Pharo VM version: 5.0-201901231209  Wed Jan 23 12:32:13 UTC 2019 gcc 4.8 
>>> [Production Spur 64-bit VM]
>>> Built from: CoInterpreter VMMaker.oscog-eem.2509 uuid: 
>>> 91e81f64-95de-4914-a960-8f842be3a194 Jan 23 2019
>>> With: StackToRegisterMappingCogit VMMaker.oscog-eem.2509 uuid: 
>>> 91e81f64-95de-4914-a960-8f842be3a194 Jan 23 2019
>>> Revision: VM: 201901231209 
>>> https://github.com/OpenSmalltalk/opensmalltalk-vm.git 
>>>  Date: Wed Jan 23 
>>> 07:09:49 2019 CommitHash: a4b2dfa6 Plugins: 201901231209 
>>> https://github.com/OpenSmalltalk/opensmalltalk-vm.git 
>>> 
>>> Build host: Linux travis-job-3a8f8935-e791-48da-aa41-2eccc2452870 
>>> 4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017 
>>> x86_64 x86_64 x86_64 GNU/Linux
>>> plugin path: /opt/pharo/bin [default: 
>>> /opt/pharo/lib/pharo/5.0-201901231209/]
>>> 
>>> 
>>> C stack backtrace & registers:
>>> rax 0x rbx 0x7f4aacbce700 rcx 0x rdx 0x0014
>>> rdi 0x rsi 0x rbp 0x rsp 0x7fffdc831d00
>>> r8  0x

Re: [Pharo-users] What's wrong with latest Pharo?

[Tim Mackinnon]

Guille - it looks like modifying that method and :
"I installed some other package (`libcurl-gnutls`) which is an "addon" to the 
regular `libcurl`.”

Got us further - now he’s getting IceAuthenticationError- which could be down 
to git vs https. (I can use the #remoteTypeSelector: trick to hopefully fix 
that).

When I confirm everything, I will report back the magic syntax (at least for 
Arch) - as well as the desire to back port that fix to 7.

Thanks for chipping in (and this is the thread that keeps on giving…)

Tim

> On 30 Apr 2019, at 16:08, Tim Mackinnon  wrote:
> 
> Actually - the user has confirmed a bit more (which sounds like your hunch 
> Guille):
> 
> Hmm… Just loading the image without `eval`ing something seems to boot up 
> well. But then I also realise, that there is a warning:
> 
> ```ioLoadModule(/opt/pharo/bin/../lib/pharo/5.0-201901231209/libgit2.so):
>   libcurl-gnutls.so.4: cannot open shared object file: No such file or 
> directory```
> (edited)
> 
> So this looks like pharo tries to load a bundled libgit2 first during bootup 
> which fails and only later, when trying to call into it, system resolves into 
> the system installed one.
> Which then causes the segfault for some reason.
> 
> I’ll see if I can guide him through changing that method.
> 
> Tim
> 
>> On 30 Apr 2019, at 15:53, Tim Mackinnon > > wrote:
>> 
>> Hi Guille - I’m not using Arch Linux myself - this was a seasoned exercism 
>> contributor trying to give pharo a spin - and sadly it hasn’t gone well 
>> (shame as they might have been an advocate) They also commented:
>> 
>> "I'm not quite sure though if I really want to continue from here. As 
>> someone new to pharo, I basically can't find any installation instructions 
>> that go beyond that evil `curl`. I'm happy to play this to the end with you, 
>> that at least exercism gets proper instructions, but the pharo community 
>> really should change their mind and provide more and better documentation 
>> about systemwide installation and packages. I have a hard time seeing 
>> something used at my compnay that does not provide an RPM out of the box…”
>> 
>> Which is fair play.
>> 
>> However I did get some details which might salvage something (and maybe they 
>> can try)
>> 
>> Its ArchLinux (apparently there are no versions in Arch, its always the 
>> latest).
>> Pharo wa installed via AUR (looks like a bit old - 2019-01-24 18:18) - not 
>> sure that is the issue though
>> AUR does give an image so they downloaded the latest 64 bit one from here - 
>> https://files.pharo.org/image/70/ 
>> Libgit2 was missing - that was installed (not clear on how - could ask)
>> 
>> After all of this - it did launch - they saw a welcome screen then it 
>> crashed (I think they were doing our eval string to metacello load exercism 
>> - so it would then use libgit2)
>> 
>> They then got this error:
>> https://pastebin.com/W2D86ZS4 
>> 
>> I’ve pasted the error below - for prosperity.
>> 
>> Tim
>> 
>> Pharo VM version: 5.0-201901231209  Wed Jan 23 12:32:13 UTC 2019 gcc 4.8 
>> [Production Spur 64-bit VM]
>> Built from: CoInterpreter VMMaker.oscog-eem.2509 uuid: 
>> 91e81f64-95de-4914-a960-8f842be3a194 Jan 23 2019
>> With: StackToRegisterMappingCogit VMMaker.oscog-eem.2509 uuid: 
>> 91e81f64-95de-4914-a960-8f842be3a194 Jan 23 2019
>> Revision: VM: 201901231209 
>> https://github.com/OpenSmalltalk/opensmalltalk-vm.git 
>>  Date: Wed Jan 23 
>> 07:09:49 2019 CommitHash: a4b2dfa6 Plugins: 201901231209 
>> https://github.com/OpenSmalltalk/opensmalltalk-vm.git 
>> 
>> Build host: Linux travis-job-3a8f8935-e791-48da-aa41-2eccc2452870 
>> 4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017 
>> x86_64 x86_64 x86_64 GNU/Linux
>> plugin path: /opt/pharo/bin [default: /opt/pharo/lib/pharo/5.0-201901231209/]
>> 
>> 
>> C stack backtrace & registers:
>>  rax 0x rbx 0x7f4aacbce700 rcx 0x rdx 0x0014
>>  rdi 0x rsi 0x rbp 0x rsp 0x7fffdc831d00
>>  r8  0x r9  0x7f4aacbbce22 r10 0x0006 r11 0x7fffdc831d08
>>  r12 0x0040 r13 0x0014 r14 0x r15 0x7f4aacbbce22
>>  rip 0x7f4aac72f3b9
>> */lib/libcrypto.so.1.1(BN_num_bits+0x9)[0x7f4aac72f3b9]
>> /opt/pharo/bin/../lib/pharo/5.0-201901231209/pharo[0x41b0d3]
>> /opt/pharo/bin/../lib/pharo/5.0-201901231209/pharo[0x41cb2e]
>> /lib/libpthread.so.0(+0x124d0)[0x7f4aaeb2d4d0]
>> /lib/libcrypto.so.1.1(BN_num_bits+0x9)[0x7f4aac72f3b9]
>> /lib/libcrypto.so.1.1(RSA_size+0xe)[0x7f4aac81fa5e]
>> /lib/libcrypto.so.1.1(+0x1b43b6)[0x7f4aac8273b6]
>> /lib/libcrypto.so.1.1(RSA_verify+0x2b)[0x7f4aac82777b]
>> /opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0x2c2df)[0x7f4aac4672df]
>> /opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0xabbf)[0x7f4aac445bbf]
>> /opt/

Re: [Pharo-users] What's wrong with latest Pharo?

[Tim Mackinnon]

Actually - the user has confirmed a bit more (which sounds like your hunch 
Guille):

Hmm… Just loading the image without `eval`ing something seems to boot up well. 
But then I also realise, that there is a warning:

```ioLoadModule(/opt/pharo/bin/../lib/pharo/5.0-201901231209/libgit2.so):
  libcurl-gnutls.so.4: cannot open shared object file: No such file or 
directory```
(edited)

So this looks like pharo tries to load a bundled libgit2 first during bootup 
which fails and only later, when trying to call into it, system resolves into 
the system installed one.
Which then causes the segfault for some reason.

I’ll see if I can guide him through changing that method.

Tim

> On 30 Apr 2019, at 15:53, Tim Mackinnon  wrote:
> 
> Hi Guille - I’m not using Arch Linux myself - this was a seasoned exercism 
> contributor trying to give pharo a spin - and sadly it hasn’t gone well 
> (shame as they might have been an advocate) They also commented:
> 
> "I'm not quite sure though if I really want to continue from here. As someone 
> new to pharo, I basically can't find any installation instructions that go 
> beyond that evil `curl`. I'm happy to play this to the end with you, that at 
> least exercism gets proper instructions, but the pharo community really 
> should change their mind and provide more and better documentation about 
> systemwide installation and packages. I have a hard time seeing something 
> used at my compnay that does not provide an RPM out of the box…”
> 
> Which is fair play.
> 
> However I did get some details which might salvage something (and maybe they 
> can try)
> 
> Its ArchLinux (apparently there are no versions in Arch, its always the 
> latest).
> Pharo wa installed via AUR (looks like a bit old - 2019-01-24 18:18) - not 
> sure that is the issue though
> AUR does give an image so they downloaded the latest 64 bit one from here - 
> https://files.pharo.org/image/70/ 
> Libgit2 was missing - that was installed (not clear on how - could ask)
> 
> After all of this - it did launch - they saw a welcome screen then it crashed 
> (I think they were doing our eval string to metacello load exercism - so it 
> would then use libgit2)
> 
> They then got this error:
> https://pastebin.com/W2D86ZS4 
> 
> I’ve pasted the error below - for prosperity.
> 
> Tim
> 
> Pharo VM version: 5.0-201901231209  Wed Jan 23 12:32:13 UTC 2019 gcc 4.8 
> [Production Spur 64-bit VM]
> Built from: CoInterpreter VMMaker.oscog-eem.2509 uuid: 
> 91e81f64-95de-4914-a960-8f842be3a194 Jan 23 2019
> With: StackToRegisterMappingCogit VMMaker.oscog-eem.2509 uuid: 
> 91e81f64-95de-4914-a960-8f842be3a194 Jan 23 2019
> Revision: VM: 201901231209 
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git 
>  Date: Wed Jan 23 
> 07:09:49 2019 CommitHash: a4b2dfa6 Plugins: 201901231209 
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git 
> 
> Build host: Linux travis-job-3a8f8935-e791-48da-aa41-2eccc2452870 
> 4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017 x86_64 
> x86_64 x86_64 GNU/Linux
> plugin path: /opt/pharo/bin [default: /opt/pharo/lib/pharo/5.0-201901231209/]
> 
> 
> C stack backtrace & registers:
>   rax 0x rbx 0x7f4aacbce700 rcx 0x rdx 0x0014
>   rdi 0x rsi 0x rbp 0x rsp 0x7fffdc831d00
>   r8  0x r9  0x7f4aacbbce22 r10 0x0006 r11 0x7fffdc831d08
>   r12 0x0040 r13 0x0014 r14 0x r15 0x7f4aacbbce22
>   rip 0x7f4aac72f3b9
> */lib/libcrypto.so.1.1(BN_num_bits+0x9)[0x7f4aac72f3b9]
> /opt/pharo/bin/../lib/pharo/5.0-201901231209/pharo[0x41b0d3]
> /opt/pharo/bin/../lib/pharo/5.0-201901231209/pharo[0x41cb2e]
> /lib/libpthread.so.0(+0x124d0)[0x7f4aaeb2d4d0]
> /lib/libcrypto.so.1.1(BN_num_bits+0x9)[0x7f4aac72f3b9]
> /lib/libcrypto.so.1.1(RSA_size+0xe)[0x7f4aac81fa5e]
> /lib/libcrypto.so.1.1(+0x1b43b6)[0x7f4aac8273b6]
> /lib/libcrypto.so.1.1(RSA_verify+0x2b)[0x7f4aac82777b]
> /opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0x2c2df)[0x7f4aac4672df]
> /opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0xabbf)[0x7f4aac445bbf]
> /opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0xe377)[0x7f4aac449377]
> /opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0xffbe)[0x7f4aac44afbe]
> /opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0x11cb6)[0x7f4aac44ccb6]
> /opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0x1ad00)[0x7f4aac455d00]
> /opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(libssh2_session_handshake+0x2e)[0x7f4aac455f8f]
> /lib/libgit2.so(+0xc3265)[0x7f4aacb33265]
> /lib/libgit2.so(+0xbf06b)[0x7f4aacb2f06b]
> /lib/libgit2.so(git_remote_connect+0x166)[0x7f4aacb0bf66]
> /lib/libgit2.so(git_remote_fetch+0x97)[0x7f4aacb0d417]
> /lib/libgit2.so(git_clone+0x36a)[0x7f4aaca9c4ea]
> /opt/pharo/bin/../lib/pharo/5.0-201901231209/pharo[

Re: [Pharo-users] What's wrong with latest Pharo?

[Tim Mackinnon]

Hi Guille - I’m not using Arch Linux myself - this was a seasoned exercism 
contributor trying to give pharo a spin - and sadly it hasn’t gone well (shame 
as they might have been an advocate) They also commented:

"I'm not quite sure though if I really want to continue from here. As someone 
new to pharo, I basically can't find any installation instructions that go 
beyond that evil `curl`. I'm happy to play this to the end with you, that at 
least exercism gets proper instructions, but the pharo community really should 
change their mind and provide more and better documentation about systemwide 
installation and packages. I have a hard time seeing something used at my 
compnay that does not provide an RPM out of the box…”

Which is fair play.

However I did get some details which might salvage something (and maybe they 
can try)

Its ArchLinux (apparently there are no versions in Arch, its always the latest).
Pharo wa installed via AUR (looks like a bit old - 2019-01-24 18:18) - not sure 
that is the issue though
AUR does give an image so they downloaded the latest 64 bit one from here - 
https://files.pharo.org/image/70/
Libgit2 was missing - that was installed (not clear on how - could ask)

After all of this - it did launch - they saw a welcome screen then it crashed 
(I think they were doing our eval string to metacello load exercism - so it 
would then use libgit2)

They then got this error:
https://pastebin.com/W2D86ZS4

I’ve pasted the error below - for prosperity.

Tim

Pharo VM version: 5.0-201901231209  Wed Jan 23 12:32:13 UTC 2019 gcc 4.8 
[Production Spur 64-bit VM]
Built from: CoInterpreter VMMaker.oscog-eem.2509 uuid: 
91e81f64-95de-4914-a960-8f842be3a194 Jan 23 2019
With: StackToRegisterMappingCogit VMMaker.oscog-eem.2509 uuid: 
91e81f64-95de-4914-a960-8f842be3a194 Jan 23 2019
Revision: VM: 201901231209 
https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Wed Jan 23 07:09:49 
2019 CommitHash: a4b2dfa6 Plugins: 201901231209 
https://github.com/OpenSmalltalk/opensmalltalk-vm.git
Build host: Linux travis-job-3a8f8935-e791-48da-aa41-2eccc2452870 
4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
plugin path: /opt/pharo/bin [default: /opt/pharo/lib/pharo/5.0-201901231209/]


C stack backtrace & registers:
rax 0x rbx 0x7f4aacbce700 rcx 0x rdx 0x0014
rdi 0x rsi 0x rbp 0x rsp 0x7fffdc831d00
r8  0x r9  0x7f4aacbbce22 r10 0x0006 r11 0x7fffdc831d08
r12 0x0040 r13 0x0014 r14 0x r15 0x7f4aacbbce22
rip 0x7f4aac72f3b9
*/lib/libcrypto.so.1.1(BN_num_bits+0x9)[0x7f4aac72f3b9]
/opt/pharo/bin/../lib/pharo/5.0-201901231209/pharo[0x41b0d3]
/opt/pharo/bin/../lib/pharo/5.0-201901231209/pharo[0x41cb2e]
/lib/libpthread.so.0(+0x124d0)[0x7f4aaeb2d4d0]
/lib/libcrypto.so.1.1(BN_num_bits+0x9)[0x7f4aac72f3b9]
/lib/libcrypto.so.1.1(RSA_size+0xe)[0x7f4aac81fa5e]
/lib/libcrypto.so.1.1(+0x1b43b6)[0x7f4aac8273b6]
/lib/libcrypto.so.1.1(RSA_verify+0x2b)[0x7f4aac82777b]
/opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0x2c2df)[0x7f4aac4672df]
/opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0xabbf)[0x7f4aac445bbf]
/opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0xe377)[0x7f4aac449377]
/opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0xffbe)[0x7f4aac44afbe]
/opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0x11cb6)[0x7f4aac44ccb6]
/opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(+0x1ad00)[0x7f4aac455d00]
/opt/pharo/lib/pharo/5.0-201901231209/libssh2.so.1(libssh2_session_handshake+0x2e)[0x7f4aac455f8f]
/lib/libgit2.so(+0xc3265)[0x7f4aacb33265]
/lib/libgit2.so(+0xbf06b)[0x7f4aacb2f06b]
/lib/libgit2.so(git_remote_connect+0x166)[0x7f4aacb0bf66]
/lib/libgit2.so(git_remote_fetch+0x97)[0x7f4aacb0d417]
/lib/libgit2.so(git_clone+0x36a)[0x7f4aaca9c4ea]
/opt/pharo/bin/../lib/pharo/5.0-201901231209/pharo[0x4cacb6]
/opt/pharo/bin/../lib/pharo/5.0-201901231209/pharo[0x4585f7]
/opt/pharo/bin/../lib/pharo/5.0-201901231209/pharo[0x45a667]
/opt/pharo/bin/../lib/pharo/5.0-201901231209/pharo(ceSendsupertonumArgs+0x265)[0x45c4b5]
[0x1f00100]
[0x7f4aacbcc7b0]


Smalltalk stack dump:
0x7fffdc85b750 M LGitRepository>clone:url:local_path:options: 0x246e7f0: 
a(n) LGitRepository
0x7fffdc85b7d0 I FFICalloutAPI>function:module: 0x25189e8: a(n) 
FFICalloutAPI
0x7fffdc85b820 I LGitRepository(LGitExternalObject)>callUnchecked:options: 
0x246e7f0: a(n) LGitRepository
0x7fffdc85b870 I LGitRepository>clone:url:local_path:options: 0x246e7f0: 
a(n) LGitRepository
0x7fffdc85b8e8 I [] in LGitRepository>clone:options:to: 0x246e7f0: a(n) 
LGitRepository
0x7fffdc85b928 I LGitRepository(LGitExternalObject)>withReturnHandlerDo: 
0x246e7f0: a(n) LGitRepository
0x7fffdc85b970 I LGitRepository>clone:options:to: 0x246e7f0: a(n) 
LGitRepository
0x7fffdc85b9c8 I LGitRepository>clone:options: 0x246e7f0: a(n) 
LGitRepository
0x7fffdc85ba10 M [] in IceGitClo

Re: [Pharo-users] What's wrong with latest Pharo?

[Guillermo Polito]

Hi Tim,

Looking at the resolution of the libgit library, I see that in pharo7 the
following:

LGitLibrary >> unixModuleName
| pluginDir |
pluginDir := Smalltalk vm binary parent.
#('libgit2.so' 'libgit2.so.0')
detect: [ :each | (pluginDir / each) exists ]
ifFound: [ :libName | ^ libName ].

self error: 'Module not found.'

That definition may be the root of the problem in linux because it is
returning the unqualified library name without the VM path.
Then, the order of resolution of libraries is the one in the operating
system, which is in your case probably searching in /usr/lib or something
like that.
I'd bet that you have in your system (/usr/lib/something) another libgit
version but probably not matching the expected version in pharo or the
architecture of pharo (32/64 bits).
Thus, pharo finds the library but cannot load it...

If you check in Pharo8, the same method reads slightly different:

LGitLibrary >> unixModuleName
| pluginDir |
pluginDir := Smalltalk vm binary parent.
#('libgit2.so' 'libgit2.so.0')
detect: [ :each | (pluginDir / each) exists ]
ifFound: [ :libName | ^ (pluginDir / libName) fullName ].

self error: 'Module not found.'

Can you check that patching the method like that works in your case?
This maybe deserves a backporting as it may make it super complicated to
work with Iceberg in some linuxes...

On Tue, Apr 30, 2019 at 3:08 PM Tim Mackinnon  wrote:

> Did we ever get the bottom of installing Pharo on linux? I have a user on
> Arch linux who installed pharo from AUR (this is new stuff to me) - and
> once they downloaded an image - they now get an error that looks
> suspiciously like this libgit2 debacle - so I’m wondering what the solution
> was?
>
> The error is:
>
> External module not found
> ExternalLibraryFunction(Object)>>error:
> ExternalLibraryFunction(Object)>>externalCallFailed
> ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments:
> LGitLibrary>>libgit2_init
> FFICalloutAPI>>function:module:
> LGitLibrary(Object)>>ffiCall:
> LGitLibrary>>libgit2_init
> [ self libgit2_init.
> self recordInitializationSuccess ] in LGitLibrary>>initializeLibGit2 in
> Block: [ self libgit2_init
> BlockClosure>>on:do:
>
> ...
>
> On 4 Apr 2019, at 15:07, Vitor Medina Cruz  wrote:
>
> No, you can't install libcurl3 with libcurl4. There is a known conflict
> between them: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294,
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900511
>
> Ubuntu 18.4 don't come with curl, but I think it comes with libcurl3 (I
> don't have means to verify it now), but when you install curl, it installs
> libcurl4 and removes libcurl3.
>
> On Thu, Apr 4, 2019 at 11:00 AM Richard O'Keefe  wrote:
>
>> apt-cache search
>> reports everything it knows about, not just things that are INSTALLED.
>> For example, apt-cache search reports lua-curl-dev, but it is not
>> installed.
>> apt list | grep lua-curl-dev
>>
>> The fact that neither libcurl3 nor libcurl4 is initially installed
>> means that either of them can be installed without conflict.
>>
>> On Thu, 4 Apr 2019 at 01:34, Ben Coman  wrote:
>>
>>>
>>> On Wed, 3 Apr 2019 at 05:09, Richard O'Keefe  wrote:
>>>
 I just did a complete reinstall of Ubuntu 18.4 on this
 laptop yesterday,

>>>
>>>
>>>
 and it did not come with any version of curl.

>>>
>>> What do you mean? Under WSL I have installed Ubuntu 18.4 and for...
>>> $ apt-cache search libcurl | less
>>> I see libcurl3 and libcurl4
>>>
>>> cheers -ben
>>>
>>>
 uname -a =>
 Linux Inspiron 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12
 13:35:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux



 On Wed, 3 Apr 2019 at 01:27, Vitor Medina Cruz 
 wrote:

> Installing curl don't work because there is a conflict between curl
> version name used on Ubuntu and that used by Pharo, you can't install
> libcurl 3 and libcru4 together. Ubuntu 18 comes with libcurl4 and older
> software depending on libcurl3 broke with it. I tested with minidebian and
> it also failed.
>
> Richard, was you able to use Iceberg? It should only work if either
> Ubuntu fix this dependency problem with libcurl or Pharo started to use
> libcrl4.
>
>
>
> On Tue, Apr 2, 2019 at 5:50 AM Richard O'Keefe 
> wrote:
>
>> I have Pharo 6.1 and Pharo 7.0 working in Ubuntu 18.04
>> with no trouble so far.  I just downloaded the launcher
>> from pharo.org and pulled the images down that way.
>>
>> One thing I do find annoying in Ubuntu 18.04 is the
>> number of programs (like okular) that spew warning
>> messages out the terminal.  Pharo, sadly, is one of
>> them.  Whenever a debugger window comes up in Pharo
>> there is spewage on the terminal.  But it works.
>>
>>
>> On Tue, 2 Apr 2019 at 13:07, john pfersich 
>> wrote:
>>
>>> Ubuntu 18.04 LTS is, IMHO, is royal piece of crap. Ubuntu seems to
>>> have abandone

Re: [Pharo-users] What's wrong with latest Pharo?

[Tim Mackinnon]

Did we ever get the bottom of installing Pharo on linux? I have a user on Arch 
linux who installed pharo from AUR (this is new stuff to me) - and once they 
downloaded an image - they now get an error that looks suspiciously like this 
libgit2 debacle - so I’m wondering what the solution was?

The error is:

External module not found
ExternalLibraryFunction(Object)>>error:
ExternalLibraryFunction(Object)>>externalCallFailed
ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments:
LGitLibrary>>libgit2_init
FFICalloutAPI>>function:module:
LGitLibrary(Object)>>ffiCall:
LGitLibrary>>libgit2_init
[ self libgit2_init.
self recordInitializationSuccess ] in LGitLibrary>>initializeLibGit2 in Block: 
[ self libgit2_init
BlockClosure>>on:do:

...

> On 4 Apr 2019, at 15:07, Vitor Medina Cruz  wrote:
> 
> No, you can't install libcurl3 with libcurl4. There is a known conflict 
> between them: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294 
> , 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900511 
> 
> 
> Ubuntu 18.4 don't come with curl, but I think it comes with libcurl3 (I don't 
> have means to verify it now), but when you install curl, it installs libcurl4 
> and removes libcurl3.
> 
> On Thu, Apr 4, 2019 at 11:00 AM Richard O'Keefe  > wrote:
> apt-cache search
> reports everything it knows about, not just things that are INSTALLED.
> For example, apt-cache search reports lua-curl-dev, but it is not
> installed.
> apt list | grep lua-curl-dev
> 
> The fact that neither libcurl3 nor libcurl4 is initially installed
> means that either of them can be installed without conflict.
> 
> On Thu, 4 Apr 2019 at 01:34, Ben Coman  > wrote:
> 
> On Wed, 3 Apr 2019 at 05:09, Richard O'Keefe  > wrote:
> I just did a complete reinstall of Ubuntu 18.4 on this
> laptop yesterday,
> 
>  
> and it did not come with any version of curl. 
> 
> What do you mean? Under WSL I have installed Ubuntu 18.4 and for...
> $ apt-cache search libcurl | less
> I see libcurl3 and libcurl4
> 
> cheers -ben
>  
> uname -a =>
> Linux Inspiron 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12 13:35:51 
> UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
> 
> 
> 
> On Wed, 3 Apr 2019 at 01:27, Vitor Medina Cruz  > wrote:
> Installing curl don't work because there is a conflict between curl version 
> name used on Ubuntu and that used by Pharo, you can't install libcurl 3 and 
> libcru4 together. Ubuntu 18 comes with libcurl4 and older software depending 
> on libcurl3 broke with it. I tested with minidebian and it also failed. 
> 
> Richard, was you able to use Iceberg? It should only work if either Ubuntu 
> fix this dependency problem with libcurl or Pharo started to use libcrl4.
> 
> 
> 
> On Tue, Apr 2, 2019 at 5:50 AM Richard O'Keefe  > wrote:
> I have Pharo 6.1 and Pharo 7.0 working in Ubuntu 18.04
> with no trouble so far.  I just downloaded the launcher
> from pharo.org  and pulled the images down that way.
> 
> One thing I do find annoying in Ubuntu 18.04 is the
> number of programs (like okular) that spew warning
> messages out the terminal.  Pharo, sadly, is one of
> them.  Whenever a debugger window comes up in Pharo
> there is spewage on the terminal.  But it works.
> 
> 
> On Tue, 2 Apr 2019 at 13:07, john pfersich  > wrote:
> Ubuntu 18.04 LTS is, IMHO, is royal piece of crap. Ubuntu seems to have 
> abandoned programmers tools almost completely in 18.04. I’ve had more 
> problems with support of programming tools in 18.04, more than even Windows. 
> I have run ‘sudo apt install’ maybe 80 times to install tools and libraries. 
> Ubuntu 18.04’s hardware support is also lame compared to 16.04. 
> Personally , I’m not surprised that Pharo doesn’t run on 18.04. I stopped 
> installing 18.04 on my new machines, after all 16.04 still has a few years of 
> support going for it, and at least it works without hours of upgrading. 
> 
> /*—-*/
> Sent from my iPhone
> https://boincstats.com/signature/-1/user/51616339056/sig.png 
> 
> See https://objectnets.net  and 
> https://objectnets.org 
> 
> > On Apr 1, 2019, at 06:06, horrido  > > wrote:
> > 
> > This issue bit me in the ass before, but I forgot. Yes, I had a senior
> > moment.
> > 
> > The issue is this: When I tried to run Pharo under Ubuntu Server 18.04 at
> > OVH last year, it failed. I had to fall back to Ubuntu Server 16.04.
> > 
> > This week, I tried to run Pharo under Ubuntu Server 18.04 at Google Cloud
> > Platform and it failed. Again, I had to fall back to Ubuntu Server 16.04.
> > 
> > Why does this issue

Re: [Pharo-users] What's wrong with latest Pharo?

[Vitor Medina Cruz]

No, you can't install libcurl3 with libcurl4. There is a known conflict
between them: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900511

Ubuntu 18.4 don't come with curl, but I think it comes with libcurl3 (I
don't have means to verify it now), but when you install curl, it installs
libcurl4 and removes libcurl3.

On Thu, Apr 4, 2019 at 11:00 AM Richard O'Keefe  wrote:

> apt-cache search
> reports everything it knows about, not just things that are INSTALLED.
> For example, apt-cache search reports lua-curl-dev, but it is not
> installed.
> apt list | grep lua-curl-dev
>
> The fact that neither libcurl3 nor libcurl4 is initially installed
> means that either of them can be installed without conflict.
>
> On Thu, 4 Apr 2019 at 01:34, Ben Coman  wrote:
>
>>
>> On Wed, 3 Apr 2019 at 05:09, Richard O'Keefe  wrote:
>>
>>> I just did a complete reinstall of Ubuntu 18.4 on this
>>> laptop yesterday,
>>>
>>
>>
>>
>>> and it did not come with any version of curl.
>>>
>>
>> What do you mean? Under WSL I have installed Ubuntu 18.4 and for...
>> $ apt-cache search libcurl | less
>> I see libcurl3 and libcurl4
>>
>> cheers -ben
>>
>>
>>> uname -a =>
>>> Linux Inspiron 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12
>>> 13:35:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
>>>
>>>
>>>
>>> On Wed, 3 Apr 2019 at 01:27, Vitor Medina Cruz 
>>> wrote:
>>>
 Installing curl don't work because there is a conflict between curl
 version name used on Ubuntu and that used by Pharo, you can't install
 libcurl 3 and libcru4 together. Ubuntu 18 comes with libcurl4 and older
 software depending on libcurl3 broke with it. I tested with minidebian and
 it also failed.

 Richard, was you able to use Iceberg? It should only work if either
 Ubuntu fix this dependency problem with libcurl or Pharo started to use
 libcrl4.



 On Tue, Apr 2, 2019 at 5:50 AM Richard O'Keefe 
 wrote:

> I have Pharo 6.1 and Pharo 7.0 working in Ubuntu 18.04
> with no trouble so far.  I just downloaded the launcher
> from pharo.org and pulled the images down that way.
>
> One thing I do find annoying in Ubuntu 18.04 is the
> number of programs (like okular) that spew warning
> messages out the terminal.  Pharo, sadly, is one of
> them.  Whenever a debugger window comes up in Pharo
> there is spewage on the terminal.  But it works.
>
>
> On Tue, 2 Apr 2019 at 13:07, john pfersich 
> wrote:
>
>> Ubuntu 18.04 LTS is, IMHO, is royal piece of crap. Ubuntu seems to
>> have abandoned programmers tools almost completely in 18.04. I’ve had 
>> more
>> problems with support of programming tools in 18.04, more than even
>> Windows. I have run ‘sudo apt install’ maybe 80 times to install tools 
>> and
>> libraries. Ubuntu 18.04’s hardware support is also lame compared to 
>> 16.04.
>> Personally , I’m not surprised that Pharo doesn’t run on 18.04. I
>> stopped installing 18.04 on my new machines, after all 16.04 still has a
>> few years of support going for it, and at least it works without hours of
>> upgrading.
>>
>> /*—-*/
>> Sent from my iPhone
>> https://boincstats.com/signature/-1/user/51616339056/sig.png
>> See https://objectnets.net and https://objectnets.org
>>
>> > On Apr 1, 2019, at 06:06, horrido 
>> wrote:
>> >
>> > This issue bit me in the ass before, but I forgot. Yes, I had a
>> senior
>> > moment.
>> >
>> > The issue is this: When I tried to run Pharo under Ubuntu Server
>> 18.04 at
>> > OVH last year, it failed. I had to fall back to Ubuntu Server 16.04.
>> >
>> > This week, I tried to run Pharo under Ubuntu Server 18.04 at Google
>> Cloud
>> > Platform and it failed. Again, I had to fall back to Ubuntu Server
>> 16.04.
>> >
>> > Why does this issue keep biting me in the ass??? Because I'm 65 and
>> my brain
>> > is dying.
>> >
>> > The bigger issue is this: Hosting services like Digital Ocean, OVH,
>> and
>> > Google Cloud Platform are becoming increasingly important in the
>> enterprise
>> > space. If Pharo can't run on these server operating systems, it's
>> going to
>> > be a black eye for the language. We can get away with not
>> supporting this
>> > for now, but it will eventually catch up with us.
>> >
>> > At Google Cloud Platform, for example, the user can choose from
>> this list of
>> > hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various
>> versions of
>> > CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu
>> 18.04 LTS
>> > Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various
>> versions
>> > of SUSE, various versions of Window, and so on. It's a long list. *I
>> > strongly

Re: [Pharo-users] What's wrong with latest Pharo?

[Richard O'Keefe]

apt-cache search
reports everything it knows about, not just things that are INSTALLED.
For example, apt-cache search reports lua-curl-dev, but it is not
installed.
apt list | grep lua-curl-dev

The fact that neither libcurl3 nor libcurl4 is initially installed
means that either of them can be installed without conflict.

On Thu, 4 Apr 2019 at 01:34, Ben Coman  wrote:

>
> On Wed, 3 Apr 2019 at 05:09, Richard O'Keefe  wrote:
>
>> I just did a complete reinstall of Ubuntu 18.4 on this
>> laptop yesterday,
>>
>
>
>
>> and it did not come with any version of curl.
>>
>
> What do you mean? Under WSL I have installed Ubuntu 18.4 and for...
> $ apt-cache search libcurl | less
> I see libcurl3 and libcurl4
>
> cheers -ben
>
>
>> uname -a =>
>> Linux Inspiron 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12
>> 13:35:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
>>
>>
>>
>> On Wed, 3 Apr 2019 at 01:27, Vitor Medina Cruz 
>> wrote:
>>
>>> Installing curl don't work because there is a conflict between curl
>>> version name used on Ubuntu and that used by Pharo, you can't install
>>> libcurl 3 and libcru4 together. Ubuntu 18 comes with libcurl4 and older
>>> software depending on libcurl3 broke with it. I tested with minidebian and
>>> it also failed.
>>>
>>> Richard, was you able to use Iceberg? It should only work if either
>>> Ubuntu fix this dependency problem with libcurl or Pharo started to use
>>> libcrl4.
>>>
>>>
>>>
>>> On Tue, Apr 2, 2019 at 5:50 AM Richard O'Keefe  wrote:
>>>
 I have Pharo 6.1 and Pharo 7.0 working in Ubuntu 18.04
 with no trouble so far.  I just downloaded the launcher
 from pharo.org and pulled the images down that way.

 One thing I do find annoying in Ubuntu 18.04 is the
 number of programs (like okular) that spew warning
 messages out the terminal.  Pharo, sadly, is one of
 them.  Whenever a debugger window comes up in Pharo
 there is spewage on the terminal.  But it works.


 On Tue, 2 Apr 2019 at 13:07, john pfersich  wrote:

> Ubuntu 18.04 LTS is, IMHO, is royal piece of crap. Ubuntu seems to
> have abandoned programmers tools almost completely in 18.04. I’ve had more
> problems with support of programming tools in 18.04, more than even
> Windows. I have run ‘sudo apt install’ maybe 80 times to install tools and
> libraries. Ubuntu 18.04’s hardware support is also lame compared to 16.04.
> Personally , I’m not surprised that Pharo doesn’t run on 18.04. I
> stopped installing 18.04 on my new machines, after all 16.04 still has a
> few years of support going for it, and at least it works without hours of
> upgrading.
>
> /*—-*/
> Sent from my iPhone
> https://boincstats.com/signature/-1/user/51616339056/sig.png
> See https://objectnets.net and https://objectnets.org
>
> > On Apr 1, 2019, at 06:06, horrido  wrote:
> >
> > This issue bit me in the ass before, but I forgot. Yes, I had a
> senior
> > moment.
> >
> > The issue is this: When I tried to run Pharo under Ubuntu Server
> 18.04 at
> > OVH last year, it failed. I had to fall back to Ubuntu Server 16.04.
> >
> > This week, I tried to run Pharo under Ubuntu Server 18.04 at Google
> Cloud
> > Platform and it failed. Again, I had to fall back to Ubuntu Server
> 16.04.
> >
> > Why does this issue keep biting me in the ass??? Because I'm 65 and
> my brain
> > is dying.
> >
> > The bigger issue is this: Hosting services like Digital Ocean, OVH,
> and
> > Google Cloud Platform are becoming increasingly important in the
> enterprise
> > space. If Pharo can't run on these server operating systems, it's
> going to
> > be a black eye for the language. We can get away with not supporting
> this
> > for now, but it will eventually catch up with us.
> >
> > At Google Cloud Platform, for example, the user can choose from this
> list of
> > hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various
> versions of
> > CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu
> 18.04 LTS
> > Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various
> versions
> > of SUSE, various versions of Window, and so on. It's a long list. *I
> > strongly suspect that many of these are unusable with Pharo.*
> >
> > How to address this? I don't know. But if it's not a major problem
> now, it
> > will be. It's bitten me in the ass twice, and I can't be alone.
> >
> > I'm giving a fair warning to everyone. Don't lash back at me – I'm
> just the
> > canary in the coal mine.
> >
> >
> >
> >
> > Tim Mackinnon wrote
> >> Come on, let’s try not to be dismissive , we’ve all had that
> annoying
> >> moment where something doesn’t work.
> >>
> >> Richard, was this installed with zero conf or La

Re: [Pharo-users] What's wrong with latest Pharo?

[Ben Coman]

On Wed, 3 Apr 2019 at 05:09, Richard O'Keefe  wrote:

> I just did a complete reinstall of Ubuntu 18.4 on this
> laptop yesterday,
>



> and it did not come with any version of curl.
>

What do you mean? Under WSL I have installed Ubuntu 18.4 and for...
$ apt-cache search libcurl | less
I see libcurl3 and libcurl4

cheers -ben


> uname -a =>
> Linux Inspiron 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12
> 13:35:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
>
>
>
> On Wed, 3 Apr 2019 at 01:27, Vitor Medina Cruz 
> wrote:
>
>> Installing curl don't work because there is a conflict between curl
>> version name used on Ubuntu and that used by Pharo, you can't install
>> libcurl 3 and libcru4 together. Ubuntu 18 comes with libcurl4 and older
>> software depending on libcurl3 broke with it. I tested with minidebian and
>> it also failed.
>>
>> Richard, was you able to use Iceberg? It should only work if either
>> Ubuntu fix this dependency problem with libcurl or Pharo started to use
>> libcrl4.
>>
>>
>>
>> On Tue, Apr 2, 2019 at 5:50 AM Richard O'Keefe  wrote:
>>
>>> I have Pharo 6.1 and Pharo 7.0 working in Ubuntu 18.04
>>> with no trouble so far.  I just downloaded the launcher
>>> from pharo.org and pulled the images down that way.
>>>
>>> One thing I do find annoying in Ubuntu 18.04 is the
>>> number of programs (like okular) that spew warning
>>> messages out the terminal.  Pharo, sadly, is one of
>>> them.  Whenever a debugger window comes up in Pharo
>>> there is spewage on the terminal.  But it works.
>>>
>>>
>>> On Tue, 2 Apr 2019 at 13:07, john pfersich  wrote:
>>>
 Ubuntu 18.04 LTS is, IMHO, is royal piece of crap. Ubuntu seems to have
 abandoned programmers tools almost completely in 18.04. I’ve had more
 problems with support of programming tools in 18.04, more than even
 Windows. I have run ‘sudo apt install’ maybe 80 times to install tools and
 libraries. Ubuntu 18.04’s hardware support is also lame compared to 16.04.
 Personally , I’m not surprised that Pharo doesn’t run on 18.04. I
 stopped installing 18.04 on my new machines, after all 16.04 still has a
 few years of support going for it, and at least it works without hours of
 upgrading.

 /*—-*/
 Sent from my iPhone
 https://boincstats.com/signature/-1/user/51616339056/sig.png
 See https://objectnets.net and https://objectnets.org

 > On Apr 1, 2019, at 06:06, horrido  wrote:
 >
 > This issue bit me in the ass before, but I forgot. Yes, I had a senior
 > moment.
 >
 > The issue is this: When I tried to run Pharo under Ubuntu Server
 18.04 at
 > OVH last year, it failed. I had to fall back to Ubuntu Server 16.04.
 >
 > This week, I tried to run Pharo under Ubuntu Server 18.04 at Google
 Cloud
 > Platform and it failed. Again, I had to fall back to Ubuntu Server
 16.04.
 >
 > Why does this issue keep biting me in the ass??? Because I'm 65 and
 my brain
 > is dying.
 >
 > The bigger issue is this: Hosting services like Digital Ocean, OVH,
 and
 > Google Cloud Platform are becoming increasingly important in the
 enterprise
 > space. If Pharo can't run on these server operating systems, it's
 going to
 > be a black eye for the language. We can get away with not supporting
 this
 > for now, but it will eventually catch up with us.
 >
 > At Google Cloud Platform, for example, the user can choose from this
 list of
 > hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various
 versions of
 > CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu
 18.04 LTS
 > Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various
 versions
 > of SUSE, various versions of Window, and so on. It's a long list. *I
 > strongly suspect that many of these are unusable with Pharo.*
 >
 > How to address this? I don't know. But if it's not a major problem
 now, it
 > will be. It's bitten me in the ass twice, and I can't be alone.
 >
 > I'm giving a fair warning to everyone. Don't lash back at me – I'm
 just the
 > canary in the coal mine.
 >
 >
 >
 >
 > Tim Mackinnon wrote
 >> Come on, let’s try not to be dismissive , we’ve all had that annoying
 >> moment where something doesn’t work.
 >>
 >> Richard, was this installed with zero conf or Launcher, and as
 mentioned -
 >> a Linux distro is going to be helpful.
 >>
 >> I’m assuming it worked before at some point for you right? But was
 that v6
 >> and now you’re trying v7?
 >>
 >> Tim
 >>
 >>
 >> Sent from my iPhone
 >>
 >>> On 31 Mar 2019, at 23:46, john pfersich <
 >
 >> jpfersich@
 >
 >> > wrote:
 >>>
 >>> What Linux (distro and version) and which version of Pharo. You
 couldn’t
 >>> supply less information if y

Re: [Pharo-users] What's wrong with latest Pharo?

[Richard O'Keefe]

I just did a complete reinstall of Ubuntu 18.4 on this
laptop yesterday, and it did not come with any version
of curl.  uname -a =>
Linux Inspiron 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12 13:35:51
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux



On Wed, 3 Apr 2019 at 01:27, Vitor Medina Cruz  wrote:

> Installing curl don't work because there is a conflict between curl
> version name used on Ubuntu and that used by Pharo, you can't install
> libcurl 3 and libcru4 together. Ubuntu 18 comes with libcurl4 and older
> software depending on libcurl3 broke with it. I tested with minidebian and
> it also failed.
>
> Richard, was you able to use Iceberg? It should only work if either Ubuntu
> fix this dependency problem with libcurl or Pharo started to use libcrl4.
>
>
>
> On Tue, Apr 2, 2019 at 5:50 AM Richard O'Keefe  wrote:
>
>> I have Pharo 6.1 and Pharo 7.0 working in Ubuntu 18.04
>> with no trouble so far.  I just downloaded the launcher
>> from pharo.org and pulled the images down that way.
>>
>> One thing I do find annoying in Ubuntu 18.04 is the
>> number of programs (like okular) that spew warning
>> messages out the terminal.  Pharo, sadly, is one of
>> them.  Whenever a debugger window comes up in Pharo
>> there is spewage on the terminal.  But it works.
>>
>>
>> On Tue, 2 Apr 2019 at 13:07, john pfersich  wrote:
>>
>>> Ubuntu 18.04 LTS is, IMHO, is royal piece of crap. Ubuntu seems to have
>>> abandoned programmers tools almost completely in 18.04. I’ve had more
>>> problems with support of programming tools in 18.04, more than even
>>> Windows. I have run ‘sudo apt install’ maybe 80 times to install tools and
>>> libraries. Ubuntu 18.04’s hardware support is also lame compared to 16.04.
>>> Personally , I’m not surprised that Pharo doesn’t run on 18.04. I
>>> stopped installing 18.04 on my new machines, after all 16.04 still has a
>>> few years of support going for it, and at least it works without hours of
>>> upgrading.
>>>
>>> /*—-*/
>>> Sent from my iPhone
>>> https://boincstats.com/signature/-1/user/51616339056/sig.png
>>> See https://objectnets.net and https://objectnets.org
>>>
>>> > On Apr 1, 2019, at 06:06, horrido  wrote:
>>> >
>>> > This issue bit me in the ass before, but I forgot. Yes, I had a senior
>>> > moment.
>>> >
>>> > The issue is this: When I tried to run Pharo under Ubuntu Server 18.04
>>> at
>>> > OVH last year, it failed. I had to fall back to Ubuntu Server 16.04.
>>> >
>>> > This week, I tried to run Pharo under Ubuntu Server 18.04 at Google
>>> Cloud
>>> > Platform and it failed. Again, I had to fall back to Ubuntu Server
>>> 16.04.
>>> >
>>> > Why does this issue keep biting me in the ass??? Because I'm 65 and my
>>> brain
>>> > is dying.
>>> >
>>> > The bigger issue is this: Hosting services like Digital Ocean, OVH, and
>>> > Google Cloud Platform are becoming increasingly important in the
>>> enterprise
>>> > space. If Pharo can't run on these server operating systems, it's
>>> going to
>>> > be a black eye for the language. We can get away with not supporting
>>> this
>>> > for now, but it will eventually catch up with us.
>>> >
>>> > At Google Cloud Platform, for example, the user can choose from this
>>> list of
>>> > hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various
>>> versions of
>>> > CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu
>>> 18.04 LTS
>>> > Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various
>>> versions
>>> > of SUSE, various versions of Window, and so on. It's a long list. *I
>>> > strongly suspect that many of these are unusable with Pharo.*
>>> >
>>> > How to address this? I don't know. But if it's not a major problem
>>> now, it
>>> > will be. It's bitten me in the ass twice, and I can't be alone.
>>> >
>>> > I'm giving a fair warning to everyone. Don't lash back at me – I'm
>>> just the
>>> > canary in the coal mine.
>>> >
>>> >
>>> >
>>> >
>>> > Tim Mackinnon wrote
>>> >> Come on, let’s try not to be dismissive , we’ve all had that annoying
>>> >> moment where something doesn’t work.
>>> >>
>>> >> Richard, was this installed with zero conf or Launcher, and as
>>> mentioned -
>>> >> a Linux distro is going to be helpful.
>>> >>
>>> >> I’m assuming it worked before at some point for you right? But was
>>> that v6
>>> >> and now you’re trying v7?
>>> >>
>>> >> Tim
>>> >>
>>> >>
>>> >> Sent from my iPhone
>>> >>
>>> >>> On 31 Mar 2019, at 23:46, john pfersich <
>>> >
>>> >> jpfersich@
>>> >
>>> >> > wrote:
>>> >>>
>>> >>> What Linux (distro and version) and which version of Pharo. You
>>> couldn’t
>>> >>> supply less information if you tried.
>>> >>>
>>> >>>
>>> >>> /*—-*/
>>> >>> Sent from my iPhone
>>> >>> https://boincstats.com/signature/-1/user/51616339056/sig.png
>>> >>> See https://objectnets.net and https://objectnets.org
>>> >>>
>>>  On Mar 31, 2019, at 14:21, Richard Kenneth Eng <
>>> >
>>> >> horrido.hobbies@
>>> >
>>> >> > wrote:
>>> 
>>>  I 

Re: [Pharo-users] What's wrong with latest Pharo?

[Vitor Medina Cruz]

Installing curl don't work because there is a conflict between curl version
name used on Ubuntu and that used by Pharo, you can't install libcurl 3 and
libcru4 together. Ubuntu 18 comes with libcurl4 and older software
depending on libcurl3 broke with it. I tested with minidebian and it also
failed.

Richard, was you able to use Iceberg? It should only work if either Ubuntu
fix this dependency problem with libcurl or Pharo started to use libcrl4.



On Tue, Apr 2, 2019 at 5:50 AM Richard O'Keefe  wrote:

> I have Pharo 6.1 and Pharo 7.0 working in Ubuntu 18.04
> with no trouble so far.  I just downloaded the launcher
> from pharo.org and pulled the images down that way.
>
> One thing I do find annoying in Ubuntu 18.04 is the
> number of programs (like okular) that spew warning
> messages out the terminal.  Pharo, sadly, is one of
> them.  Whenever a debugger window comes up in Pharo
> there is spewage on the terminal.  But it works.
>
>
> On Tue, 2 Apr 2019 at 13:07, john pfersich  wrote:
>
>> Ubuntu 18.04 LTS is, IMHO, is royal piece of crap. Ubuntu seems to have
>> abandoned programmers tools almost completely in 18.04. I’ve had more
>> problems with support of programming tools in 18.04, more than even
>> Windows. I have run ‘sudo apt install’ maybe 80 times to install tools and
>> libraries. Ubuntu 18.04’s hardware support is also lame compared to 16.04.
>> Personally , I’m not surprised that Pharo doesn’t run on 18.04. I stopped
>> installing 18.04 on my new machines, after all 16.04 still has a few years
>> of support going for it, and at least it works without hours of upgrading.
>>
>> /*—-*/
>> Sent from my iPhone
>> https://boincstats.com/signature/-1/user/51616339056/sig.png
>> See https://objectnets.net and https://objectnets.org
>>
>> > On Apr 1, 2019, at 06:06, horrido  wrote:
>> >
>> > This issue bit me in the ass before, but I forgot. Yes, I had a senior
>> > moment.
>> >
>> > The issue is this: When I tried to run Pharo under Ubuntu Server 18.04
>> at
>> > OVH last year, it failed. I had to fall back to Ubuntu Server 16.04.
>> >
>> > This week, I tried to run Pharo under Ubuntu Server 18.04 at Google
>> Cloud
>> > Platform and it failed. Again, I had to fall back to Ubuntu Server
>> 16.04.
>> >
>> > Why does this issue keep biting me in the ass??? Because I'm 65 and my
>> brain
>> > is dying.
>> >
>> > The bigger issue is this: Hosting services like Digital Ocean, OVH, and
>> > Google Cloud Platform are becoming increasingly important in the
>> enterprise
>> > space. If Pharo can't run on these server operating systems, it's going
>> to
>> > be a black eye for the language. We can get away with not supporting
>> this
>> > for now, but it will eventually catch up with us.
>> >
>> > At Google Cloud Platform, for example, the user can choose from this
>> list of
>> > hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various
>> versions of
>> > CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu
>> 18.04 LTS
>> > Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various
>> versions
>> > of SUSE, various versions of Window, and so on. It's a long list. *I
>> > strongly suspect that many of these are unusable with Pharo.*
>> >
>> > How to address this? I don't know. But if it's not a major problem now,
>> it
>> > will be. It's bitten me in the ass twice, and I can't be alone.
>> >
>> > I'm giving a fair warning to everyone. Don't lash back at me – I'm just
>> the
>> > canary in the coal mine.
>> >
>> >
>> >
>> >
>> > Tim Mackinnon wrote
>> >> Come on, let’s try not to be dismissive , we’ve all had that annoying
>> >> moment where something doesn’t work.
>> >>
>> >> Richard, was this installed with zero conf or Launcher, and as
>> mentioned -
>> >> a Linux distro is going to be helpful.
>> >>
>> >> I’m assuming it worked before at some point for you right? But was
>> that v6
>> >> and now you’re trying v7?
>> >>
>> >> Tim
>> >>
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On 31 Mar 2019, at 23:46, john pfersich <
>> >
>> >> jpfersich@
>> >
>> >> > wrote:
>> >>>
>> >>> What Linux (distro and version) and which version of Pharo. You
>> couldn’t
>> >>> supply less information if you tried.
>> >>>
>> >>>
>> >>> /*—-*/
>> >>> Sent from my iPhone
>> >>> https://boincstats.com/signature/-1/user/51616339056/sig.png
>> >>> See https://objectnets.net and https://objectnets.org
>> >>>
>>  On Mar 31, 2019, at 14:21, Richard Kenneth Eng <
>> >
>> >> horrido.hobbies@
>> >
>> >> > wrote:
>> 
>>  I just installed Pharo under Linux and when I start it up, I get:
>> 
>>  Error: External module not found
>> 
>>  It doesn't matter how I install Pharo.
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>> >
>>
>>

Re: [Pharo-users] What's wrong with latest Pharo?

[Richard O'Keefe]

I have Pharo 6.1 and Pharo 7.0 working in Ubuntu 18.04
with no trouble so far.  I just downloaded the launcher
from pharo.org and pulled the images down that way.

One thing I do find annoying in Ubuntu 18.04 is the
number of programs (like okular) that spew warning
messages out the terminal.  Pharo, sadly, is one of
them.  Whenever a debugger window comes up in Pharo
there is spewage on the terminal.  But it works.


On Tue, 2 Apr 2019 at 13:07, john pfersich  wrote:

> Ubuntu 18.04 LTS is, IMHO, is royal piece of crap. Ubuntu seems to have
> abandoned programmers tools almost completely in 18.04. I’ve had more
> problems with support of programming tools in 18.04, more than even
> Windows. I have run ‘sudo apt install’ maybe 80 times to install tools and
> libraries. Ubuntu 18.04’s hardware support is also lame compared to 16.04.
> Personally , I’m not surprised that Pharo doesn’t run on 18.04. I stopped
> installing 18.04 on my new machines, after all 16.04 still has a few years
> of support going for it, and at least it works without hours of upgrading.
>
> /*—-*/
> Sent from my iPhone
> https://boincstats.com/signature/-1/user/51616339056/sig.png
> See https://objectnets.net and https://objectnets.org
>
> > On Apr 1, 2019, at 06:06, horrido  wrote:
> >
> > This issue bit me in the ass before, but I forgot. Yes, I had a senior
> > moment.
> >
> > The issue is this: When I tried to run Pharo under Ubuntu Server 18.04 at
> > OVH last year, it failed. I had to fall back to Ubuntu Server 16.04.
> >
> > This week, I tried to run Pharo under Ubuntu Server 18.04 at Google Cloud
> > Platform and it failed. Again, I had to fall back to Ubuntu Server 16.04.
> >
> > Why does this issue keep biting me in the ass??? Because I'm 65 and my
> brain
> > is dying.
> >
> > The bigger issue is this: Hosting services like Digital Ocean, OVH, and
> > Google Cloud Platform are becoming increasingly important in the
> enterprise
> > space. If Pharo can't run on these server operating systems, it's going
> to
> > be a black eye for the language. We can get away with not supporting this
> > for now, but it will eventually catch up with us.
> >
> > At Google Cloud Platform, for example, the user can choose from this
> list of
> > hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various
> versions of
> > CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu 18.04
> LTS
> > Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various
> versions
> > of SUSE, various versions of Window, and so on. It's a long list. *I
> > strongly suspect that many of these are unusable with Pharo.*
> >
> > How to address this? I don't know. But if it's not a major problem now,
> it
> > will be. It's bitten me in the ass twice, and I can't be alone.
> >
> > I'm giving a fair warning to everyone. Don't lash back at me – I'm just
> the
> > canary in the coal mine.
> >
> >
> >
> >
> > Tim Mackinnon wrote
> >> Come on, let’s try not to be dismissive , we’ve all had that annoying
> >> moment where something doesn’t work.
> >>
> >> Richard, was this installed with zero conf or Launcher, and as
> mentioned -
> >> a Linux distro is going to be helpful.
> >>
> >> I’m assuming it worked before at some point for you right? But was that
> v6
> >> and now you’re trying v7?
> >>
> >> Tim
> >>
> >>
> >> Sent from my iPhone
> >>
> >>> On 31 Mar 2019, at 23:46, john pfersich <
> >
> >> jpfersich@
> >
> >> > wrote:
> >>>
> >>> What Linux (distro and version) and which version of Pharo. You
> couldn’t
> >>> supply less information if you tried.
> >>>
> >>>
> >>> /*—-*/
> >>> Sent from my iPhone
> >>> https://boincstats.com/signature/-1/user/51616339056/sig.png
> >>> See https://objectnets.net and https://objectnets.org
> >>>
>  On Mar 31, 2019, at 14:21, Richard Kenneth Eng <
> >
> >> horrido.hobbies@
> >
> >> > wrote:
> 
>  I just installed Pharo under Linux and when I start it up, I get:
> 
>  Error: External module not found
> 
>  It doesn't matter how I install Pharo.
> >
> >
> >
> >
> >
> > --
> > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> >
>
>

Re: [Pharo-users] What's wrong with latest Pharo?

[john pfersich]

You need to install curl in Ubuntu 18.04 LTS, it isn’t in the distro you 
download from Ubuntu. 

/*—-*/
Sent from my iPhone
https://boincstats.com/signature/-1/user/51616339056/sig.png
See https://objectnets.net and https://objectnets.org

> On Apr 1, 2019, at 06:47, Vitor Medina Cruz  wrote:
> 
> I am surprised you managed to make it work Sven, I tried some time ago but it 
> wont work because of a problem with libcurl as far as I am concerned 
> (https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754686 and 
> https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294)
> 
> Was libcurl dependency removed from Pharo?
> 
>> On Mon, Apr 1, 2019 at 10:18 AM Sven Van Caekenberghe  wrote:
>> Don't be silly, of course it works. Hundreds of people have these, 99% of 
>> all servers are Linux, as are 99% of all CI jobs.
>> 
>> Running Linux servers requires a certain level of expertise.
>> 
>> $ cat /etc/issue
>> Ubuntu 18.04.2 LTS \n \l
>> 
>> $ uname -a
>> Linux audio359 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
>> x86_64 x86_64 x86_64 GNU/Linux
>> 
>> $ curl get.pharo.org/64/70+vm | bash
>>   % Total% Received % Xferd  Average Speed   TimeTime Time  
>> Current
>>  Dload  Upload   Total   SpentLeft  Speed
>> 100  3054  100  30540 0  32147  0 --:--:-- --:--:-- --:--:-- 
>> 32147
>> Downloading the latest 70 Image:
>> http://files.pharo.org/get-files/70/pharo64.zip
>> Pharo.image
>> Downloading the latest pharoVM:
>> http://files.pharo.org/get-files/70/pharo64-linux-stable.zip
>> pharo-vm/pharo
>> Creating starter scripts pharo and pharo-ui
>> 
>> $ ./pharo Pharo.image printVersion
>> [version] 'Pharo7.0.2' 
>> 'Pharo-7.0.2+build.152.sha.890f474a81f116ead0e68c8de77790aef4e9a752 (64 Bit)'
>> 
>> $ ./pharo Pharo.image eval '42 factorial'
>> 14050061177528798985431426062445115699363840
>> 
>> Many people are about your age, BTW.
>> 
>> > On 1 Apr 2019, at 15:06, horrido  wrote:
>> > 
>> > This issue bit me in the ass before, but I forgot. Yes, I had a senior
>> > moment.
>> > 
>> > The issue is this: When I tried to run Pharo under Ubuntu Server 18.04 at
>> > OVH last year, it failed. I had to fall back to Ubuntu Server 16.04.
>> > 
>> > This week, I tried to run Pharo under Ubuntu Server 18.04 at Google Cloud
>> > Platform and it failed. Again, I had to fall back to Ubuntu Server 16.04.
>> > 
>> > Why does this issue keep biting me in the ass??? Because I'm 65 and my 
>> > brain
>> > is dying.
>> > 
>> > The bigger issue is this: Hosting services like Digital Ocean, OVH, and
>> > Google Cloud Platform are becoming increasingly important in the enterprise
>> > space. If Pharo can't run on these server operating systems, it's going to
>> > be a black eye for the language. We can get away with not supporting this
>> > for now, but it will eventually catch up with us.
>> > 
>> > At Google Cloud Platform, for example, the user can choose from this list 
>> > of
>> > hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various versions 
>> > of
>> > CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu 18.04 
>> > LTS
>> > Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various 
>> > versions
>> > of SUSE, various versions of Window, and so on. It's a long list. *I
>> > strongly suspect that many of these are unusable with Pharo.*
>> > 
>> > How to address this? I don't know. But if it's not a major problem now, it
>> > will be. It's bitten me in the ass twice, and I can't be alone.
>> > 
>> > I'm giving a fair warning to everyone. Don't lash back at me – I'm just the
>> > canary in the coal mine.
>> > 
>> > 
>> > 
>> > 
>> > Tim Mackinnon wrote
>> >> Come on, let’s try not to be dismissive , we’ve all had that annoying
>> >> moment where something doesn’t work.
>> >> 
>> >> Richard, was this installed with zero conf or Launcher, and as mentioned -
>> >> a Linux distro is going to be helpful.
>> >> 
>> >> I’m assuming it worked before at some point for you right? But was that v6
>> >> and now you’re trying v7?
>> >> 
>> >> Tim
>> >> 
>> >> 
>> >> Sent from my iPhone
>> >> 
>> >>> On 31 Mar 2019, at 23:46, john pfersich <
>> > 
>> >> jpfersich@
>> > 
>> >> > wrote:
>> >>> 
>> >>> What Linux (distro and version) and which version of Pharo. You couldn’t
>> >>> supply less information if you tried. 
>> >>> 
>> >>> 
>> >>> /*—-*/
>> >>> Sent from my iPhone
>> >>> https://boincstats.com/signature/-1/user/51616339056/sig.png
>> >>> See https://objectnets.net and https://objectnets.org
>> >>> 
>>  On Mar 31, 2019, at 14:21, Richard Kenneth Eng <
>> > 
>> >> horrido.hobbies@
>> > 
>> >> > wrote:
>>  
>>  I just installed Pharo under Linux and when I start it up, I get:
>>  
>>  Error: External module not found
>>  
>>  It doesn't matter how I install Pharo.
>> > 
>> > 
>> > 
>> > 
>> > 
>> > --
>> > Sent from: http://forum.world.st/Pharo-

Re: [Pharo-users] What's wrong with latest Pharo?

[john pfersich]

Ubuntu 18.04 LTS is, IMHO, is royal piece of crap. Ubuntu seems to have 
abandoned programmers tools almost completely in 18.04. I’ve had more problems 
with support of programming tools in 18.04, more than even Windows. I have run 
‘sudo apt install’ maybe 80 times to install tools and libraries. Ubuntu 
18.04’s hardware support is also lame compared to 16.04. 
Personally , I’m not surprised that Pharo doesn’t run on 18.04. I stopped 
installing 18.04 on my new machines, after all 16.04 still has a few years of 
support going for it, and at least it works without hours of upgrading. 

/*—-*/
Sent from my iPhone
https://boincstats.com/signature/-1/user/51616339056/sig.png
See https://objectnets.net and https://objectnets.org

> On Apr 1, 2019, at 06:06, horrido  wrote:
> 
> This issue bit me in the ass before, but I forgot. Yes, I had a senior
> moment.
> 
> The issue is this: When I tried to run Pharo under Ubuntu Server 18.04 at
> OVH last year, it failed. I had to fall back to Ubuntu Server 16.04.
> 
> This week, I tried to run Pharo under Ubuntu Server 18.04 at Google Cloud
> Platform and it failed. Again, I had to fall back to Ubuntu Server 16.04.
> 
> Why does this issue keep biting me in the ass??? Because I'm 65 and my brain
> is dying.
> 
> The bigger issue is this: Hosting services like Digital Ocean, OVH, and
> Google Cloud Platform are becoming increasingly important in the enterprise
> space. If Pharo can't run on these server operating systems, it's going to
> be a black eye for the language. We can get away with not supporting this
> for now, but it will eventually catch up with us.
> 
> At Google Cloud Platform, for example, the user can choose from this list of
> hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various versions of
> CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu 18.04 LTS
> Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various versions
> of SUSE, various versions of Window, and so on. It's a long list. *I
> strongly suspect that many of these are unusable with Pharo.*
> 
> How to address this? I don't know. But if it's not a major problem now, it
> will be. It's bitten me in the ass twice, and I can't be alone.
> 
> I'm giving a fair warning to everyone. Don't lash back at me – I'm just the
> canary in the coal mine.
> 
> 
> 
> 
> Tim Mackinnon wrote
>> Come on, let’s try not to be dismissive , we’ve all had that annoying
>> moment where something doesn’t work.
>> 
>> Richard, was this installed with zero conf or Launcher, and as mentioned -
>> a Linux distro is going to be helpful.
>> 
>> I’m assuming it worked before at some point for you right? But was that v6
>> and now you’re trying v7?
>> 
>> Tim
>> 
>> 
>> Sent from my iPhone
>> 
>>> On 31 Mar 2019, at 23:46, john pfersich <
> 
>> jpfersich@
> 
>> > wrote:
>>> 
>>> What Linux (distro and version) and which version of Pharo. You couldn’t
>>> supply less information if you tried. 
>>> 
>>> 
>>> /*—-*/
>>> Sent from my iPhone
>>> https://boincstats.com/signature/-1/user/51616339056/sig.png
>>> See https://objectnets.net and https://objectnets.org
>>> 
 On Mar 31, 2019, at 14:21, Richard Kenneth Eng <
> 
>> horrido.hobbies@
> 
>> > wrote:
 
 I just installed Pharo under Linux and when I start it up, I get:
 
 Error: External module not found
 
 It doesn't matter how I install Pharo.
> 
> 
> 
> 
> 
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> 

Re: [Pharo-users] What's wrong with latest Pharo?

[Offray Vladimir Luna Cárdenas]

Hi,

Just install libcurl from your Linux distro package manager. Maybe this 
should be more promptly stated in the Linux install instructions.


Cheers,

Offray

On 1/04/19 8:06 a. m., horrido wrote:

This issue bit me in the ass before, but I forgot. Yes, I had a senior
moment.

The issue is this: When I tried to run Pharo under Ubuntu Server 18.04 at
OVH last year, it failed. I had to fall back to Ubuntu Server 16.04.

This week, I tried to run Pharo under Ubuntu Server 18.04 at Google Cloud
Platform and it failed. Again, I had to fall back to Ubuntu Server 16.04.

Why does this issue keep biting me in the ass??? Because I'm 65 and my brain
is dying.

The bigger issue is this: Hosting services like Digital Ocean, OVH, and
Google Cloud Platform are becoming increasingly important in the enterprise
space. If Pharo can't run on these server operating systems, it's going to
be a black eye for the language. We can get away with not supporting this
for now, but it will eventually catch up with us.

At Google Cloud Platform, for example, the user can choose from this list of
hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various versions of
CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu 18.04 LTS
Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various versions
of SUSE, various versions of Window, and so on. It's a long list. *I
strongly suspect that many of these are unusable with Pharo.*

How to address this? I don't know. But if it's not a major problem now, it
will be. It's bitten me in the ass twice, and I can't be alone.

I'm giving a fair warning to everyone. Don't lash back at me – I'm just the
canary in the coal mine.




Tim Mackinnon wrote

Come on, let’s try not to be dismissive , we’ve all had that annoying
moment where something doesn’t work.

Richard, was this installed with zero conf or Launcher, and as mentioned -
a Linux distro is going to be helpful.

I’m assuming it worked before at some point for you right? But was that v6
and now you’re trying v7?

Tim


Sent from my iPhone


On 31 Mar 2019, at 23:46, john pfersich <

jpfersich@
> wrote:

What Linux (distro and version) and which version of Pharo. You couldn’t
supply less information if you tried.


/*—-*/
Sent from my iPhone
https://boincstats.com/signature/-1/user/51616339056/sig.png
See https://objectnets.net and https://objectnets.org


On Mar 31, 2019, at 14:21, Richard Kenneth Eng <

horrido.hobbies@
> wrote:

I just installed Pharo under Linux and when I start it up, I get:

Error: External module not found

It doesn't matter how I install Pharo.





--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] What's wrong with latest Pharo?

[Hilaire]

Which external module is not found? I personally had a recurring issue
when using the P7 VM+Image.

I have to use Launcher to get a working environment.

Le 31/03/2019 à 23:21, Richard Kenneth Eng a écrit :
> I just installed Pharo under Linux and when I start it up, I get:
>
> *Error: External module not found*
>
> It doesn't matter how I install Pharo.

-- 
Dr. Geo
http://drgeo.eu

Re: [Pharo-users] What's wrong with latest Pharo?

[Sven Van Caekenberghe]

This is basic Pharo I am talking about, not each and every plugin.

$ ldd pharo-vm/lib/pharo/5.0-201901051900/pharo 
linux-vdso.so.1 (0x7fff789b2000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f010c0ee000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f010bd5)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f010bb31000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f010b74)
/lib64/ld-linux-x86-64.so.2 (0x7f010c2f2000)

libgit2 seems to be using libcurl (and many more)

$ ldd pharo-vm/lib/pharo/5.0-201901051900/libgit2.so
linux-vdso.so.1 (0x7ffc8dec3000)
libcurl-gnutls.so.4 => /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 
(0x7f4057393000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f4057176000)
libssl.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 
(0x7f4056f0e000)
libcrypto.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 
(0x7f4056acb000)
libssh2.so.1 => not found
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f40568c3000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f40566a4000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f40562b3000)
libnghttp2.so.14 => /usr/lib/x86_64-linux-gnu/libnghttp2.so.14 
(0x7f405608e000)
libidn2.so.0 => /usr/lib/x86_64-linux-gnu/libidn2.so.0 
(0x7f4055e71000)
librtmp.so.1 => /usr/lib/x86_64-linux-gnu/librtmp.so.1 
(0x7f4055c55000)
libpsl.so.5 => /usr/lib/x86_64-linux-gnu/libpsl.so.5 
(0x7f4055a47000)
libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 
(0x7f4055811000)
libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 
(0x7f40554ac000)
libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 
(0x7f4055261000)
libldap_r-2.4.so.2 => /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 
(0x7f405500f000)
liblber-2.4.so.2 => /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2 
(0x7f4054e01000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f4054bfd000)
/lib64/ld-linux-x86-64.so.2 (0x7f4057953000)
libunistring.so.2 => /usr/lib/x86_64-linux-gnu/libunistring.so.2 
(0x7f405487f000)
libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 
(0x7f405464b000)
libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
(0x7f40543ca000)
libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 
(0x7f405409b000)
libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 
(0x7f4053e88000)
libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 
(0x7f4053bb2000)
libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 
(0x7f405398)
libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 
(0x7f405377c000)
libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 
(0x7f4053571000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f4053356000)
libsasl2.so.2 => /usr/lib/x86_64-linux-gnu/libsasl2.so.2 
(0x7f405313b000)
libgssapi.so.3 => /usr/lib/x86_64-linux-gnu/libgssapi.so.3 
(0x7f4052efa000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 
(0x7f4052cf2000)
libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 
(0x7f4052aee000)
libheimntlm.so.0 => /usr/lib/x86_64-linux-gnu/libheimntlm.so.0 
(0x7f40528e5000)
libkrb5.so.26 => /usr/lib/x86_64-linux-gnu/libkrb5.so.26 
(0x7f4052658000)
libasn1.so.8 => /usr/lib/x86_64-linux-gnu/libasn1.so.8 
(0x7f40523b6000)
libhcrypto.so.4 => /usr/lib/x86_64-linux-gnu/libhcrypto.so.4 
(0x7f405218)
libroken.so.18 => /usr/lib/x86_64-linux-gnu/libroken.so.18 
(0x7f4051f6a000)
libwind.so.0 => /usr/lib/x86_64-linux-gnu/libwind.so.0 
(0x7f4051d41000)
libheimbase.so.1 => /usr/lib/x86_64-linux-gnu/libheimbase.so.1 
(0x7f4051b32000)
libhx509.so.5 => /usr/lib/x86_64-linux-gnu/libhx509.so.5 
(0x7f40518e8000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f40515df000)
libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 
(0x7f40513a7000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f4051009000)

> On 1 Apr 2019, at 15:47, Vitor Medina Cruz  wrote:
> 
> I am surprised you managed to make it work Sven, I tried some time ago but it 
> wont work because of a problem with libcurl as far as I am concerned 
> (https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754686 and 
> https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294)
> 
> Was libcurl dependency removed from Pharo?
> 
> On Mon, Apr 1, 2019 at 10:18 AM Sven Van Caekenberghe  wrote:
> Don't be silly, of course it works. Hundreds of people have these, 99% of all

Re: [Pharo-users] What's wrong with latest Pharo?

[Vitor Medina Cruz]

I am surprised you managed to make it work Sven, I tried some time ago but
it wont work because of a problem with libcurl as far as I am concerned (
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754686 and
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294)


Was libcurl dependency removed from Pharo?

On Mon, Apr 1, 2019 at 10:18 AM Sven Van Caekenberghe  wrote:

> Don't be silly, of course it works. Hundreds of people have these, 99% of
> all servers are Linux, as are 99% of all CI jobs.
>
> Running Linux servers requires a certain level of expertise.
>
> $ cat /etc/issue
> Ubuntu 18.04.2 LTS \n \l
>
> $ uname -a
> Linux audio359 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC
> 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> $ curl get.pharo.org/64/70+vm | bash
>   % Total% Received % Xferd  Average Speed   TimeTime Time
> Current
>  Dload  Upload   Total   SpentLeft
> Speed
> 100  3054  100  30540 0  32147  0 --:--:-- --:--:-- --:--:--
> 32147
> Downloading the latest 70 Image:
> http://files.pharo.org/get-files/70/pharo64.zip
> Pharo.image
> Downloading the latest pharoVM:
> http://files.pharo.org/get-files/70/pharo64-linux-stable.zip
> pharo-vm/pharo
> Creating starter scripts pharo and pharo-ui
>
> $ ./pharo Pharo.image printVersion
> [version] 'Pharo7.0.2'
> 'Pharo-7.0.2+build.152.sha.890f474a81f116ead0e68c8de77790aef4e9a752 (64
> Bit)'
>
> $ ./pharo Pharo.image eval '42 factorial'
> 14050061177528798985431426062445115699363840
>
> Many people are about your age, BTW.
>
> > On 1 Apr 2019, at 15:06, horrido  wrote:
> >
> > This issue bit me in the ass before, but I forgot. Yes, I had a senior
> > moment.
> >
> > The issue is this: When I tried to run Pharo under Ubuntu Server 18.04 at
> > OVH last year, it failed. I had to fall back to Ubuntu Server 16.04.
> >
> > This week, I tried to run Pharo under Ubuntu Server 18.04 at Google Cloud
> > Platform and it failed. Again, I had to fall back to Ubuntu Server 16.04.
> >
> > Why does this issue keep biting me in the ass??? Because I'm 65 and my
> brain
> > is dying.
> >
> > The bigger issue is this: Hosting services like Digital Ocean, OVH, and
> > Google Cloud Platform are becoming increasingly important in the
> enterprise
> > space. If Pharo can't run on these server operating systems, it's going
> to
> > be a black eye for the language. We can get away with not supporting this
> > for now, but it will eventually catch up with us.
> >
> > At Google Cloud Platform, for example, the user can choose from this
> list of
> > hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various
> versions of
> > CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu 18.04
> LTS
> > Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various
> versions
> > of SUSE, various versions of Window, and so on. It's a long list. *I
> > strongly suspect that many of these are unusable with Pharo.*
> >
> > How to address this? I don't know. But if it's not a major problem now,
> it
> > will be. It's bitten me in the ass twice, and I can't be alone.
> >
> > I'm giving a fair warning to everyone. Don't lash back at me – I'm just
> the
> > canary in the coal mine.
> >
> >
> >
> >
> > Tim Mackinnon wrote
> >> Come on, let’s try not to be dismissive , we’ve all had that annoying
> >> moment where something doesn’t work.
> >>
> >> Richard, was this installed with zero conf or Launcher, and as
> mentioned -
> >> a Linux distro is going to be helpful.
> >>
> >> I’m assuming it worked before at some point for you right? But was that
> v6
> >> and now you’re trying v7?
> >>
> >> Tim
> >>
> >>
> >> Sent from my iPhone
> >>
> >>> On 31 Mar 2019, at 23:46, john pfersich <
> >
> >> jpfersich@
> >
> >> > wrote:
> >>>
> >>> What Linux (distro and version) and which version of Pharo. You
> couldn’t
> >>> supply less information if you tried.
> >>>
> >>>
> >>> /*—-*/
> >>> Sent from my iPhone
> >>> https://boincstats.com/signature/-1/user/51616339056/sig.png
> >>> See https://objectnets.net and https://objectnets.org
> >>>
>  On Mar 31, 2019, at 14:21, Richard Kenneth Eng <
> >
> >> horrido.hobbies@
> >
> >> > wrote:
> 
>  I just installed Pharo under Linux and when I start it up, I get:
> 
>  Error: External module not found
> 
>  It doesn't matter how I install Pharo.
> >
> >
> >
> >
> >
> > --
> > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>
>
>

Re: [Pharo-users] What's wrong with latest Pharo?

[Sven Van Caekenberghe]

Don't be silly, of course it works. Hundreds of people have these, 99% of all 
servers are Linux, as are 99% of all CI jobs.

Running Linux servers requires a certain level of expertise.

$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l

$ uname -a
Linux audio359 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ curl get.pharo.org/64/70+vm | bash
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  3054  100  30540 0  32147  0 --:--:-- --:--:-- --:--:-- 32147
Downloading the latest 70 Image:
http://files.pharo.org/get-files/70/pharo64.zip
Pharo.image
Downloading the latest pharoVM:
http://files.pharo.org/get-files/70/pharo64-linux-stable.zip
pharo-vm/pharo
Creating starter scripts pharo and pharo-ui

$ ./pharo Pharo.image printVersion
[version] 'Pharo7.0.2' 
'Pharo-7.0.2+build.152.sha.890f474a81f116ead0e68c8de77790aef4e9a752 (64 Bit)'

$ ./pharo Pharo.image eval '42 factorial'
14050061177528798985431426062445115699363840

Many people are about your age, BTW.

> On 1 Apr 2019, at 15:06, horrido  wrote:
> 
> This issue bit me in the ass before, but I forgot. Yes, I had a senior
> moment.
> 
> The issue is this: When I tried to run Pharo under Ubuntu Server 18.04 at
> OVH last year, it failed. I had to fall back to Ubuntu Server 16.04.
> 
> This week, I tried to run Pharo under Ubuntu Server 18.04 at Google Cloud
> Platform and it failed. Again, I had to fall back to Ubuntu Server 16.04.
> 
> Why does this issue keep biting me in the ass??? Because I'm 65 and my brain
> is dying.
> 
> The bigger issue is this: Hosting services like Digital Ocean, OVH, and
> Google Cloud Platform are becoming increasingly important in the enterprise
> space. If Pharo can't run on these server operating systems, it's going to
> be a black eye for the language. We can get away with not supporting this
> for now, but it will eventually catch up with us.
> 
> At Google Cloud Platform, for example, the user can choose from this list of
> hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various versions of
> CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu 18.04 LTS
> Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various versions
> of SUSE, various versions of Window, and so on. It's a long list. *I
> strongly suspect that many of these are unusable with Pharo.*
> 
> How to address this? I don't know. But if it's not a major problem now, it
> will be. It's bitten me in the ass twice, and I can't be alone.
> 
> I'm giving a fair warning to everyone. Don't lash back at me – I'm just the
> canary in the coal mine.
> 
> 
> 
> 
> Tim Mackinnon wrote
>> Come on, let’s try not to be dismissive , we’ve all had that annoying
>> moment where something doesn’t work.
>> 
>> Richard, was this installed with zero conf or Launcher, and as mentioned -
>> a Linux distro is going to be helpful.
>> 
>> I’m assuming it worked before at some point for you right? But was that v6
>> and now you’re trying v7?
>> 
>> Tim
>> 
>> 
>> Sent from my iPhone
>> 
>>> On 31 Mar 2019, at 23:46, john pfersich <
> 
>> jpfersich@
> 
>> > wrote:
>>> 
>>> What Linux (distro and version) and which version of Pharo. You couldn’t
>>> supply less information if you tried. 
>>> 
>>> 
>>> /*—-*/
>>> Sent from my iPhone
>>> https://boincstats.com/signature/-1/user/51616339056/sig.png
>>> See https://objectnets.net and https://objectnets.org
>>> 
 On Mar 31, 2019, at 14:21, Richard Kenneth Eng <
> 
>> horrido.hobbies@
> 
>> > wrote:
 
 I just installed Pharo under Linux and when I start it up, I get:
 
 Error: External module not found
 
 It doesn't matter how I install Pharo.
> 
> 
> 
> 
> 
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] What's wrong with latest Pharo?

[horrido]

This issue bit me in the ass before, but I forgot. Yes, I had a senior
moment.

The issue is this: When I tried to run Pharo under Ubuntu Server 18.04 at
OVH last year, it failed. I had to fall back to Ubuntu Server 16.04.

This week, I tried to run Pharo under Ubuntu Server 18.04 at Google Cloud
Platform and it failed. Again, I had to fall back to Ubuntu Server 16.04.

Why does this issue keep biting me in the ass??? Because I'm 65 and my brain
is dying.

The bigger issue is this: Hosting services like Digital Ocean, OVH, and
Google Cloud Platform are becoming increasingly important in the enterprise
space. If Pharo can't run on these server operating systems, it's going to
be a black eye for the language. We can get away with not supporting this
for now, but it will eventually catch up with us.

At Google Cloud Platform, for example, the user can choose from this list of
hosts: Debian GNU/Linux 9 (Stretch), CentOS 6, CentOS 7, various versions of
CoreOS, Ubuntu 14.04 LTS Minimal, Ubuntu 16.04 LTS Minimal, Ubuntu 18.04 LTS
Minimal, Ubuntu 18.10 Minimal, various versions of Red Hat, various versions
of SUSE, various versions of Window, and so on. It's a long list. *I
strongly suspect that many of these are unusable with Pharo.*

How to address this? I don't know. But if it's not a major problem now, it
will be. It's bitten me in the ass twice, and I can't be alone.

I'm giving a fair warning to everyone. Don't lash back at me – I'm just the
canary in the coal mine.




Tim Mackinnon wrote
> Come on, let’s try not to be dismissive , we’ve all had that annoying
> moment where something doesn’t work.
> 
> Richard, was this installed with zero conf or Launcher, and as mentioned -
> a Linux distro is going to be helpful.
> 
> I’m assuming it worked before at some point for you right? But was that v6
> and now you’re trying v7?
> 
> Tim
> 
> 
> Sent from my iPhone
> 
>> On 31 Mar 2019, at 23:46, john pfersich <

> jpfersich@

> > wrote:
>> 
>> What Linux (distro and version) and which version of Pharo. You couldn’t
>> supply less information if you tried. 
>> 
>> 
>> /*—-*/
>> Sent from my iPhone
>> https://boincstats.com/signature/-1/user/51616339056/sig.png
>> See https://objectnets.net and https://objectnets.org
>> 
>>> On Mar 31, 2019, at 14:21, Richard Kenneth Eng <

> horrido.hobbies@

> > wrote:
>>> 
>>> I just installed Pharo under Linux and when I start it up, I get:
>>> 
>>> Error: External module not found
>>> 
>>> It doesn't matter how I install Pharo.





--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] What's wrong with latest Pharo?

[Norbert Hartl]

> Am 01.04.2019 um 08:10 schrieb Tim Mackinnon :
> 
> Come on, let’s try not to be dismissive , we’ve all had that annoying moment 
> where something doesn’t work.
> 
Sure and we don‘t put that on a public mailing list. If you want to get help 
you need to provide context. 

Norbert

> Richard, was this installed with zero conf or Launcher, and as mentioned - a 
> Linux distro is going to be helpful.
> 
> I’m assuming it worked before at some point for you right? But was that v6 
> and now you’re trying v7?
> 
> Tim
> 
> 
> Sent from my iPhone
> 
>> On 31 Mar 2019, at 23:46, john pfersich  wrote:
>> 
>> What Linux (distro and version) and which version of Pharo. You couldn’t 
>> supply less information if you tried. 
>> 
>> 
>> /*—-*/
>> Sent from my iPhone
>> https://boincstats.com/signature/-1/user/51616339056/sig.png
>> See https://objectnets.net and https://objectnets.org
>> 
>>> On Mar 31, 2019, at 14:21, Richard Kenneth Eng  
>>> wrote:
>>> 
>>> I just installed Pharo under Linux and when I start it up, I get:
>>> 
>>> Error: External module not found
>>> 
>>> It doesn't matter how I install Pharo.

Re: [Pharo-users] What's wrong with latest Pharo?

[Tim Mackinnon]

Come on, let’s try not to be dismissive , we’ve all had that annoying moment 
where something doesn’t work.

Richard, was this installed with zero conf or Launcher, and as mentioned - a 
Linux distro is going to be helpful.

I’m assuming it worked before at some point for you right? But was that v6 and 
now you’re trying v7?

Tim


Sent from my iPhone

> On 31 Mar 2019, at 23:46, john pfersich  wrote:
> 
> What Linux (distro and version) and which version of Pharo. You couldn’t 
> supply less information if you tried. 
> 
> 
> /*—-*/
> Sent from my iPhone
> https://boincstats.com/signature/-1/user/51616339056/sig.png
> See https://objectnets.net and https://objectnets.org
> 
>> On Mar 31, 2019, at 14:21, Richard Kenneth Eng  
>> wrote:
>> 
>> I just installed Pharo under Linux and when I start it up, I get:
>> 
>> Error: External module not found
>> 
>> It doesn't matter how I install Pharo.

Re: [Pharo-users] What's wrong with latest Pharo?

[john pfersich]

What Linux (distro and version) and which version of Pharo. You couldn’t supply 
less information if you tried. 


/*—-*/
Sent from my iPhone
https://boincstats.com/signature/-1/user/51616339056/sig.png
See https://objectnets.net and https://objectnets.org

> On Mar 31, 2019, at 14:21, Richard Kenneth Eng  
> wrote:
> 
> I just installed Pharo under Linux and when I start it up, I get:
> 
> Error: External module not found
> 
> It doesn't matter how I install Pharo.

[Pharo-users] What's wrong with latest Pharo?

[Richard Kenneth Eng]

I just installed Pharo under Linux and when I start it up, I get:

*Error: External module not found*

It doesn't matter how I install Pharo.

Re: [Pharo-users] What's wrong?

[Ben Coman]

Its not something that I had a clue about.
thanks for the update.
cheers -ben

On Mon, 28 Jan 2019 at 16:40, eftomi  wrote:

> OK, I solved the problem with a complete wipe out of Pharo from the system
> and fresh install. Pharo stored the run-time information in a separate
> image
> folder even if I launched the vm and image without PharoLauncher, directly
> from the console.
>
> Fresh install approach solved the other problem, too
> (
> http://forum.world.st/PrimitiveFailed-primitive-createDirectory-in-WindowsStore-failed-td5094274.html).
>
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>
>

Re: [Pharo-users] What's wrong?

[eftomi]

OK, I solved the problem with a complete wipe out of Pharo from the system
and fresh install. Pharo stored the run-time information in a separate image
folder even if I launched the vm and image without PharoLauncher, directly
from the console.

Fresh install approach solved the other problem, too
(http://forum.world.st/PrimitiveFailed-primitive-createDirectory-in-WindowsStore-failed-td5094274.html).
 



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

[Pharo-users] What's wrong?

[eftomi]

Every time that I start Pharo 7.0.1 32-bit image (it's name is "Pharo 7.0 -
32bit" and it resides in the directory of the same name), a new directory is
created under images directory, with the name "Pharo 7.0 - 64bit
(development version)-01". Within it, Pharo is using directories
"ombu-sessions", "play-cache" to store its run-time information.

I'm using PharoLauncher version: 1.5.1.

The situation is the same if I do this with a fresh 7.0.1 image. System
reporter shows:

Image
-
C:\Users\eftomi.MISKOTI\EFTOMI\PHARO\images\Pharo 7.0 - 32bit\Pharo 7.0 -
32bit.image
Pharo7.0.1
Build information:
Pharo-7.0.1+build.143.sha.eca26da119bccd95e463c7717a44b814453df4e8 (32 Bit)
Unnamed

Virtual Machine
---
C:\Users\eftomi.MISKOTI\EFTOMI\PHARO\vms\70-x86\Pharo.exe
CoInterpreter VMMaker.oscog-eem.2504 uuid:
a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid:
a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date:
Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900
https://github.com/OpenSmalltalk/opensmalltalk-vm.git

Win32 built on Jan  5 2019 20:12:30 GMT Compiler: 7.4.0
VMMaker versionString VM: 201901051900
https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5
20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900
https://github.com/OpenSmalltalk/opensmalltalk-vm.git
CoInterpreter VMMaker.oscog-eem.2504 uuid:
a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid:
a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019 




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] What's wrong with this code?

[Sean P. DeNigris]

Nicolai Hess wrote
> I think the ProgressNotification was only used in

IIRC we use announcements everywhere now for progress and
ProgressNotification is no longer used. You may have found a reference that
we forgot to remove. In general, progress is handled via aBlock asJob. Maybe
all other methods should be outright removed. There were so many access
points, maybe creating more spaghetti than convenience.

Background: one of my major drivers for revamping progress with Cami at ESUG
a few years ago was that I feel that using exceptions for non-exceptional
conditions smells funny. In particular, if you're interested in being
notified of progress, but the exception was handled already in code which
you don't own, you'll never know. With the announcement approach we take
now, all interested parties can register.





-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/What-s-wrong-whith-this-code-tp4749558p4749960.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] What's wrong with this code?

[Ben Coman]

Friedrich Dominicus wrote:

  Bernat Romagosa  writes:

  
  
ouch, I added a . in the middle, sorry!

elements := #('eins' 'zwei' 'drei' 'vier').
elements
do: [ :element | (Delay forSeconds: 2) wait ]
displayingProgress: [ :element | 'Working on', element asString ].

2014-03-18 9:55 GMT+01:00 Bernat Romagosa
:

Without having tried it, I think you're missing a #wait message in
there:



elements := #('eins' 'zwei' 'drei' 'vier').
elements do: [ :element | (Delay forSeconds: 2) wait ].

displayingProgress: [ :element | 'Working on', element asString ].

  
  Sorry even with that I do not see the 'Working on ' message.
It's just a progress bar with nothing else. No "Working on" anywhere.

Regards
Friedrich


  


I'm not sure what the expected result is, but if you debug/step into
that code a few times you find yourself in...
    Array(Collection)>>do:displayingProgress:every:

Looking at _expression_...
 aStringOrBlock isString
I guessed something might be learnt from stepping through...
    elements := #('eins' 'zwei' 'drei' 'vier').
    elements do: [ :element | (Delay forSeconds: 2) wait ]
displayingProgress: 'MyProgress'
and indeed progress bar text is updated by the line...
    bar label: aStringOrBlock.

Now stepping through your original script, #label: never seems to be
executed 
So replacing...
    [ProgressNotification signal: '' extra: (oldLabel := newLabel)]
with...
    [   bar label: newLabel.    
        ProgressNotification signal: '' extra: (oldLabel := newLabel).
    ].
seems to do the trick, although as I said before, I don't know what the
expected behaviour is.  Is that what you need?

I've not looked at this code before so I've learnt something new today.
In particular, for a while I was wondering purpose ProgressNotification
served since tracing through it seemed to do nothing, and then I
realised it might be used something like this...
    elements := #('eins' 'zwei' 'drei' 'vier' ).
    [   elements do: [ :element | (Delay forSeconds: 2) wait ] 
    displayingProgress: [ :element | 'Working on ', element
asString ] 
    ] on: ProgressNotification do: 
    [     :notice | 
          self inform: notice extraParam printString. 
  notice resume 
    ]

I've logged a case
https://pharo.fogbugz.com/f/cases/13101/Progress-bar-progressive-text-update-not-working

cheers -ben

Re: [Pharo-users] What's wrong with this code?

[Ben Coman]

Ben Coman wrote:

  
Friedrich Dominicus wrote:
  
Bernat Romagosa  writes:

  

  ouch, I added a . in the middle, sorry!

elements := #('eins' 'zwei' 'drei' 'vier').
elements
do: [ :element | (Delay forSeconds: 2) wait ]
displayingProgress: [ :element | 'Working on', element asString ].

2014-03-18 9:55 GMT+01:00 Bernat Romagosa
:

Without having tried it, I think you're missing a #wait message in
there:



elements := #('eins' 'zwei' 'drei' 'vier').
elements do: [ :element | (Delay forSeconds: 2) wait ].

displayingProgress: [ :element | 'Working on', element asString ].


Sorry even with that I do not see the 'Working on ' message.
It's just a progress bar with nothing else. No "Working on" anywhere.

Regards
Friedrich


  
  
  
I'm not sure what the expected result is, but if you debug/step into
that code a few times you find yourself in...
    Array(Collection)>>do:displayingProgress:every:
  
Looking at _expression_...
 aStringOrBlock isString
I guessed something might be learnt from stepping through...
    elements := #('eins' 'zwei' 'drei' 'vier').
    elements do: [ :element | (Delay forSeconds: 2) wait ]
displayingProgress: 'MyProgress'
and indeed progress bar text is updated by the line...
    bar label: aStringOrBlock.
  
Now stepping through your original script, #label: never seems to be
executed 
So replacing...
    [ProgressNotification signal: '' extra: (oldLabel := newLabel)]
with...
    [   bar label: newLabel.    
        ProgressNotification signal: '' extra: (oldLabel := newLabel).
    ].
seems to do the trick, although as I said before, I don't know what the
expected behaviour is.  Is that what you need?
  
I've not looked at this code before so I've learnt something new today.
In particular, for a while I was wondering purpose ProgressNotification
served since tracing through it seemed to do nothing, and then I
realised it might be used something like this...
    elements := #('eins' 'zwei' 'drei' 'vier' ).
    [   elements do: [ :element | (Delay forSeconds: 2) wait ] 
    displayingProgress: [ :element | 'Working on ', element
asString ] 
    ] on: ProgressNotification do: 
    [     :notice | 
          self inform: notice extraParam printString. 
  notice resume 
    ]
  
I've logged a case
  https://pharo.fogbugz.com/f/cases/13101/Progress-bar-progressive-text-update-not-working
  
cheers -ben


Friedrich, Peter, Bernat, 
I've uploaded slice 13101 to the Pharo30Inbox.  Could you review and
comment on the issue tracker whether that is satisfactory.
cheers -ben

Re: [Pharo-users] What's wrong with this code?

[Nicolai Hess]

I think the ProgressNotification was only used in
older pharo version (like 1.4, where this displayProgress: ...
with progress title worked)


2014-03-19 16:46 GMT+01:00 Ben Coman :

>  Friedrich Dominicus wrote:
>
> Bernat Romagosa  
>  writes:
>
>
>
>  ouch, I added a . in the middle, sorry!
>
> elements := #('eins' 'zwei' 'drei' 'vier').
> elements
> do: [ :element | (Delay forSeconds: 2) wait ]
> displayingProgress: [ :element | 'Working on', element asString ].
>
> 2014-03-18 9:55 GMT+01:00 Bernat Romagosa 
> :
>
> Without having tried it, I think you're missing a #wait message in
> there:
>
>
>
> elements := #('eins' 'zwei' 'drei' 'vier').
> elements do: [ :element | (Delay forSeconds: 2) wait ].
>
> displayingProgress: [ :element | 'Working on', element asString ].
>
>
>  Sorry even with that I do not see the 'Working on ' message.
> It's just a progress bar with nothing else. No "Working on" anywhere.
>
> Regards
> Friedrich
>
>
>
>
>
> I'm not sure what the expected result is, but if you debug/step into that
> code a few times you find yourself in...
> Array(Collection)>>do:displayingProgress:every:
>
> Looking at expression...
>  aStringOrBlock isString
> I guessed something might be learnt from stepping through...
> elements := #('eins' 'zwei' 'drei' 'vier').
> elements do: [ :element | (Delay forSeconds: 2) wait ]
> displayingProgress: 'MyProgress'
> and indeed progress bar text is updated by the line...
> bar label: aStringOrBlock.
>
> Now stepping through your original script, #label: never seems to be
> executed
> So replacing...
> [ProgressNotification signal: '' extra: (oldLabel := newLabel)]
> with...
> [   bar label: newLabel.
> ProgressNotification signal: '' extra: (oldLabel := newLabel).
> ].
> seems to do the trick, although as I said before, I don't know what the
> expected behaviour is.  Is that what you need?
>
> I've not looked at this code before so I've learnt something new today. In
> particular, for a while I was wondering purpose ProgressNotification served
> since tracing through it seemed to do nothing, and then I realised it might
> be used something like this...
> elements := #('eins' 'zwei' 'drei' 'vier' ).
> [   elements do: [ :element | (Delay forSeconds: 2) wait ]
> displayingProgress: [ :element | 'Working on ', element asString ]
> ] on: ProgressNotification do:
> [ :notice |
>   self inform: notice extraParam printString.
>   notice resume
> ]
>
> I've logged a case
> https://pharo.fogbugz.com/f/cases/13101/Progress-bar-progressive-text-update-not-working
>
> cheers -ben
>

Re: [Pharo-users] What's wrong whith this code?

[PBK Research]

Well I did some experiments, and I seem to have a solution. In the method
Collection>>do:displayingProgress:every:, you will find (three lines from
the end) the line:
 ifFalse: [ProgressNotification
signal: '' extra: (oldLabel := newLabel)].

If you replace that with:

 ifFalse: [bar label: (oldLabel :=
newLabel)].

you will find that the examples of changing labels will work. I haven't
tested this as thoroughly as I should, so there may be other consequences,
but clearly this is where the problem lies. 

 

Peter Kenny


  _  

From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of
PBK Research
Sent: 19 March 2014 09:09
To: nicolaih...@web.de; 'Any question about pharo is welcome'
Subject: Re: [Pharo-users] What's wrong whith this code?


Note however that the first example used in the method comment, which
displays a static label, does work. There is something wrong in the method
of computing the changing label in the second example. I can't follow the
code here, so I can't see the error, but it should be clear where to look.
 
Peter Kenny

  _  

From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of
Nicolai Hess
Sent: 19 March 2014 08:56
To: Any question about pharo is welcome
Subject: Re: [Pharo-users] What's wrong whith this code?


2014-03-19 8:17 GMT+01:00 Friedrich Dominicus
:


Bernat Romagosa  writes:

> ouch, I added a . in the middle, sorry!
>
> elements := #('eins' 'zwei' 'drei' 'vier').
> elements
> do: [ :element | (Delay forSeconds: 2) wait ]
> displayingProgress: [ :element | 'Working on', element asString ].
>
> 2014-03-18 9:55 GMT+01:00 Bernat Romagosa
> :
>
> Without having tried it, I think you're missing a #wait message in
> there:
>
>
>
> elements := #('eins' 'zwei' 'drei' 'vier').
> elements do: [ :element | (Delay forSeconds: 2) wait ].
>
> displayingProgress: [ :element | 'Working on', element asString ].

Sorry even with that I do not see the 'Working on ' message.
It's just a progress bar with nothing else. No "Working on" anywhere.

Regards
Friedrich





It doesn't work anymore. (This worked in Pharo 1.4)
In the comment of Collection>>do:displayingProgress:
is a example, that doesn't work:
Smalltalk allClasses 
do:[:aClass| (Delay forMilliseconds: 1) wait]
displayingProgress:[:aClass| 'Processing ', aClass name].


This should show the class names but it shows
only a single progressbar.

Re: [Pharo-users] What's wrong whith this code?

[PBK Research]

Note however that the first example used in the method comment, which
displays a static label, does work. There is something wrong in the method
of computing the changing label in the second example. I can't follow the
code here, so I can't see the error, but it should be clear where to look.
 
Peter Kenny

  _  

From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of
Nicolai Hess
Sent: 19 March 2014 08:56
To: Any question about pharo is welcome
Subject: Re: [Pharo-users] What's wrong whith this code?


2014-03-19 8:17 GMT+01:00 Friedrich Dominicus
:


Bernat Romagosa  writes:

> ouch, I added a . in the middle, sorry!
>
> elements := #('eins' 'zwei' 'drei' 'vier').
> elements
> do: [ :element | (Delay forSeconds: 2) wait ]
> displayingProgress: [ :element | 'Working on', element asString ].
>
> 2014-03-18 9:55 GMT+01:00 Bernat Romagosa
> :
>
> Without having tried it, I think you're missing a #wait message in
> there:
>
>
>
> elements := #('eins' 'zwei' 'drei' 'vier').
> elements do: [ :element | (Delay forSeconds: 2) wait ].
>
> displayingProgress: [ :element | 'Working on', element asString ].

Sorry even with that I do not see the 'Working on ' message.
It's just a progress bar with nothing else. No "Working on" anywhere.

Regards
Friedrich





It doesn't work anymore. (This worked in Pharo 1.4)
In the comment of Collection>>do:displayingProgress:
is a example, that doesn't work:
Smalltalk allClasses 
do:[:aClass| (Delay forMilliseconds: 1) wait]
displayingProgress:[:aClass| 'Processing ', aClass name].


This should show the class names but it shows
only a single progressbar.

Re: [Pharo-users] What's wrong whith this code?

[Nicolai Hess]

2014-03-19 8:17 GMT+01:00 Friedrich Dominicus :

> Bernat Romagosa  writes:
>
> > ouch, I added a . in the middle, sorry!
> >
> > elements := #('eins' 'zwei' 'drei' 'vier').
> > elements
> > do: [ :element | (Delay forSeconds: 2) wait ]
> > displayingProgress: [ :element | 'Working on', element asString ].
> >
> > 2014-03-18 9:55 GMT+01:00 Bernat Romagosa
> > :
> >
> > Without having tried it, I think you're missing a #wait message in
> > there:
> >
> >
> >
> > elements := #('eins' 'zwei' 'drei' 'vier').
> > elements do: [ :element | (Delay forSeconds: 2) wait ].
> >
> > displayingProgress: [ :element | 'Working on', element asString ].
> Sorry even with that I do not see the 'Working on ' message.
> It's just a progress bar with nothing else. No "Working on" anywhere.
>
> Regards
> Friedrich
>
>

It doesn't work anymore. (This worked in Pharo 1.4)
In the comment of Collection>>do:displayingProgress:
is a example, that doesn't work:
Smalltalk allClasses
do:[:aClass| (Delay forMilliseconds: 1) wait]
displayingProgress:[:aClass| 'Processing ', aClass name].

This should show the class names but it shows
only a single progressbar.

Re: [Pharo-users] What's wrong whith this code?

[Friedrich Dominicus]

Bernat Romagosa  writes:

> ouch, I added a . in the middle, sorry!
>
> elements := #('eins' 'zwei' 'drei' 'vier').
> elements
> do: [ :element | (Delay forSeconds: 2) wait ]
> displayingProgress: [ :element | 'Working on', element asString ].
>
> 2014-03-18 9:55 GMT+01:00 Bernat Romagosa
> :
>
> Without having tried it, I think you're missing a #wait message in
> there:
> 
> 
> 
> elements := #('eins' 'zwei' 'drei' 'vier').
> elements do: [ :element | (Delay forSeconds: 2) wait ].
> 
> displayingProgress: [ :element | 'Working on', element asString ].
Sorry even with that I do not see the 'Working on ' message.
It's just a progress bar with nothing else. No "Working on" anywhere.

Regards
Friedrich

Re: [Pharo-users] What's wrong whith this code?

[Bernat Romagosa]

ouch, I added a . in the middle, sorry!

elements := #('eins' 'zwei' 'drei' 'vier').
elements
   do: [ :element | (Delay forSeconds: 2) wait ]
   displayingProgress: [ :element | 'Working on', element asString ].


2014-03-18 9:55 GMT+01:00 Bernat Romagosa :

> Without having tried it, I think you're missing a #wait message in there:
>
> elements := #('eins' 'zwei' 'drei' 'vier').
>  elements do: [ :element | (Delay forSeconds: 2) wait ].
> displayingProgress: [ :element | 'Working on', element asString ].
>
> Cheers,
> Bernat.
>
>
> 2014-03-18 9:52 GMT+01:00 Friedrich Dominicus <
> fr...@q-software-solutions.de>:
>
> elements := #('eins' 'zwei' 'drei' 'vier').
>> elements do: [ :element | Delay forSeconds: 2.  ]
>> displayingProgress: [ :element | 'Working on', element asString ].
>>
>> Shouldn't it just open a progress bar and iterate through the elements
>> printing 'Working on...?
>>
>> Regards
>> Friedrich
>>
>>
>
>
> --
> Bernat Romagosa.
>



-- 
Bernat Romagosa.

Re: [Pharo-users] What's wrong whith this code?

[Bernat Romagosa]

Without having tried it, I think you're missing a #wait message in there:

elements := #('eins' 'zwei' 'drei' 'vier').
 elements do: [ :element | (Delay forSeconds: 2) wait ].
displayingProgress: [ :element | 'Working on', element asString ].

Cheers,
Bernat.


2014-03-18 9:52 GMT+01:00 Friedrich Dominicus :

> elements := #('eins' 'zwei' 'drei' 'vier').
> elements do: [ :element | Delay forSeconds: 2.  ]
> displayingProgress: [ :element | 'Working on', element asString ].
>
> Shouldn't it just open a progress bar and iterate through the elements
> printing 'Working on...?
>
> Regards
> Friedrich
>
>


-- 
Bernat Romagosa.

[Pharo-users] What's wrong whith this code?

[Friedrich Dominicus]

elements := #('eins' 'zwei' 'drei' 'vier').
elements do: [ :element | Delay forSeconds: 2.  ]
displayingProgress: [ :element | 'Working on', element asString ].

Shouldn't it just open a progress bar and iterate through the elements
printing 'Working on...?

Regards
Friedrich