That VM is (was) a 6.0 alpha.

I tried to update and got this:

jpfersich@ubuntu64-001:~/pharo64-6.0$ curl get.pharo.org/64 | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time
Current
                                 Dload  Upload   Total   Spent    Left
Speed
100   232  100   232    0     0    581      0 --:--:-- --:--:-- --:--:--
582
bash: line 1: syntax error near unexpected token `newline'
bash: line 1: `<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">'


Then I tried the Custom installs, downloaded
pharo64-linux-threaded-stable.zip and sources.zip
and when I tried to run it, I got

'Pharo cannot locate the sources file named
/home/jpfersich/pharo64-6.0/pharo-vm/lib/pharo/5.0-201705310241/PharoV50.sources.

The sources file I downloaded is PharoV60.sources.

So I finally did
curl get.pharo.org/64/stable | bash
and
curl get.pharo.org/64/vmT60 | bash
and got a usable system.


On Fri, Jun 9, 2017 at 5:13 AM, Ben Coman <b...@openinworld.com> wrote:

> You seem to be using an old VM.
> /home/jpfersich/pharo64-6.0/pharo-vm/lib/pharo/5.0-201704181925/pharo
> Pharo VM version: 5.0-201704181925
>
> Can you try with one of these...
> http://pharo.org/download
> i.e. Pharo6.0-linux.zip/pharo6.0/bin/lib/pharo/5.0-201705310241/pharo
>
> So actually yours is not so out of date that first glance at the "5.0" in
> your path implies.
> @Esteban, can this packaging be corrected?
>
> cheers -ben
>
>
>
> On Fri, Jun 9, 2017 at 12:21 PM, john pfersich <jpfers...@gmail.com>
> wrote:
>
>> I got a seg fault when I tried to execute some OSSubProcess code in Pharo
>> 6.0.
>>
>> Namely,
>>
>> | process |
>> process := OSSUnixSubprocess new
>>                 command: '/bin/cat';
>>                 redirectStdin;
>>                 redirectStdout;
>>                 run.
>> process stdinStream
>>         nextPutAll: 'we are testing!';
>>         nextPutAll: 'we again!';
>>         close.
>> process waitForExit.
>> process stdoutStream upToEndOfFile inspect.
>> process closeAndCleanStreams.
>>
>> Attached is the crash.dmp file
>>
>
>

Reply via email to