"curl https://get.pharo.org/64 | bash" does not work (on Mac)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
bpi
Reply | Threaded
Open this post in threaded view
|

"curl https://get.pharo.org/64 | bash" does not work (on Mac)

bpi
Hi all,

Here is the output:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   237  100   237    0     0    899      0 --:--:-- --:--:-- --:--:--   901
bash: line 1: syntax error near unexpected token `newline'
bash: line 1: `<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">'

"curl https://get.pharo.org/64/ | bash" does work, though. It is just that in the documentation (https://get.pharo.org/64/) the link has no trailing slash.

I am on macOS Sierra 10.12.6.

Bernhard
Reply | Threaded
Open this post in threaded view
|

Re: "curl https://get.pharo.org/64 | bash" does not work (on Mac)

K K Subbu
On Sunday 25 February 2018 09:54 PM, Bernhard Pieber wrote:

> Hi all,
>
> Here is the output:
>    % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
>                                   Dload  Upload   Total   Spent    Left  Speed
> 100   237  100   237    0     0    899      0 --:--:-- --:--:-- --:--:--   901
> bash: line 1: syntax error near unexpected token `newline'
> bash: line 1: `<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">'
>
> "curl https://get.pharo.org/64/ | bash" does work, though. It is just that in the documentation (https://get.pharo.org/64/) the link has no trailing slash.

The URL https://get.pharo.org/64 will return a 301 (Moved permanently)
redirect reply. Unlike wget, curl will follow the redirect only if -L
option is given, so

     curl -L https://get.pharo.org/64 | bash

will also work fine. The document needs to be updated to use -L option
for curl.

HTH .. Subbu

Reply | Threaded
Open this post in threaded view
|

Re: "curl https://get.pharo.org/64 | bash" does not work (on Mac)

Stephane Ducasse-3
which page?

https://pharo.fogbugz.com/f/cases/21407/should-update-curl-L-https-get-pharo-org-64-bash-to-have-the-L

On Sun, Feb 25, 2018 at 5:49 PM, K K Subbu <[hidden email]> wrote:

> On Sunday 25 February 2018 09:54 PM, Bernhard Pieber wrote:
>>
>> Hi all,
>>
>> Here is the output:
>>    % Total    % Received % Xferd  Average Speed   Time    Time     Time
>> Current
>>                                   Dload  Upload   Total   Spent    Left
>> Speed
>> 100   237  100   237    0     0    899      0 --:--:-- --:--:-- --:--:--
>> 901
>> bash: line 1: syntax error near unexpected token `newline'
>> bash: line 1: `<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">'
>>
>> "curl https://get.pharo.org/64/ | bash" does work, though. It is just that
>> in the documentation (https://get.pharo.org/64/) the link has no trailing
>> slash.
>
>
> The URL https://get.pharo.org/64 will return a 301 (Moved permanently)
> redirect reply. Unlike wget, curl will follow the redirect only if -L option
> is given, so
>
>     curl -L https://get.pharo.org/64 | bash
>
> will also work fine. The document needs to be updated to use -L option for
> curl.
>
> HTH .. Subbu
>

Reply | Threaded
Open this post in threaded view
|

Re: "curl https://get.pharo.org/64 | bash" does not work (on Mac)

Guillermo Polito

On Sun, Feb 25, 2018 at 9:36 PM, Stephane Ducasse <[hidden email]> wrote:
which page?

https://pharo.fogbugz.com/f/cases/21407/should-update-curl-L-https-get-pharo-org-64-bash-to-have-the-L

On Sun, Feb 25, 2018 at 5:49 PM, K K Subbu <[hidden email]> wrote:
> On Sunday 25 February 2018 09:54 PM, Bernhard Pieber wrote:
>>
>> Hi all,
>>
>> Here is the output:
>>    % Total    % Received % Xferd  Average Speed   Time    Time     Time
>> Current
>>                                   Dload  Upload   Total   Spent    Left
>> Speed
>> 100   237  100   237    0     0    899      0 --:--:-- --:--:-- --:--:--
>> 901
>> bash: line 1: syntax error near unexpected token `newline'
>> bash: line 1: `<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">'
>>
>> "curl https://get.pharo.org/64/ | bash" does work, though. It is just that
>> in the documentation (https://get.pharo.org/64/) the link has no trailing
>> slash.
>
>
> The URL https://get.pharo.org/64 will return a 301 (Moved permanently)
> redirect reply. Unlike wget, curl will follow the redirect only if -L option
> is given, so
>
>     curl -L https://get.pharo.org/64 | bash
>
> will also work fine. The document needs to be updated to use -L option for
> curl.
>
> HTH .. Subbu
>




--

   

Guille Polito

Research Engineer

Centre de Recherche en Informatique, Signal et Automatique de Lille

CRIStAL - UMR 9189

French National Center for Scientific Research - http://www.cnrs.fr


Web: http://guillep.github.io

Phone: +33 06 52 70 66 13