[Sugar-devel] error building sugar-build

[Gonzalo Odiard]

And no, I am not behind a proxy :)

On Mon, Nov 4, 2013 at 3:20 PM, Gonzalo Odiard <gonzalo at laptop.org> wrote:
> When I check if the site is available with chrome,
> show a error about like something is wrong with the certificate.
>
> I can download using:
>
>  wget --no-check-certificate
> http://registry.npmjs.org/istanbul/-/istanbul-0.1.22
>
> Do you know if is possible change any configuration in our side to do the same?
>
> Gonzalo
>
> On Mon, Nov 4, 2013 at 3:16 PM, Manuel Quiñones <manuq at laptop.org> wrote:
>> 2013/11/4 Gonzalo Odiard <gonzalo at laptop.org>:
>>> Anybody knows what can be the source and solution of this error?
>>>
>>> Building in F18, default options, tried several times
>>>
>>> * Building karma
>>>
>>> Command failed: npm install -g --prefix
>>> /home/broot/sugar-build/build/out/install
>>>
>>> npm http 200 https://registry.npmjs.org/estraverse
>>> npm http GET https://registry.npmjs.org/estraverse/-/estraverse-1.3.2.tgz
>>> npm ERR! fetch failed
>>> https://registry.npmjs.org/estraverse/-/estraverse-1.3.2.tgz
>>> npm ERR! fetch failed https://registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz
>>> npm http GET https://registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz
>>> npm ERR! fetch failed https://registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz
>>> npm http GET https://registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz
>>> npm ERR! fetch failed https://registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz
>>> npm WARN optional dep failed, continuing source-map at 0.1.31
>>
>> Looks like a temporary problem with your network. Fetching from
>> registry.npmjs.org has failed for several dependencies. And the
>> following error message is quite descriptive:
>>
>>> npm ERR! network socket hang up
>>> npm ERR! network This is most likely not a problem with npm itself
>>> npm ERR! network and is related to network connectivity.
>>> npm ERR! network In most cases you are behind a proxy or have bad
>>> network settings.
>>> npm ERR! network
>>> npm ERR! network If you are behind a proxy, please make sure that the
>>> npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
>>
>> --
>> .. manuq ..