Error installing sao from source

59 views
Skip to first unread message

Axel Braun

unread,
Mar 6, 2017, 4:19:04 AM3/6/17
to tryton-dev
Hi,
I try to install sao 3.8.12 from source. :

.....
bower resolve       https://github.com/twbs/bootstrap.git#~3.3.4
bower not-cached    https://github.com/moment/moment.git#~2.10.2
bower resolve       https://github.com/moment/moment.git#~2.10.2
bower ECMDERR       Failed to execute "git ls-remote --tags --heads https://github.com/jquery/jquery-dist.git", exit code of #128 fatal: unable to access 'https://github.com/jquery/jquery-dist.git/': SSL certificate problem: unable to get local issuer certificate

Additional error details:
fatal: unable to access 'https://github.com/jquery/jquery-dist.git/': SSL certificate problem: unable to get local issuer certificate

npm ERR! Linux 4.1.38-47-default
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v4.7.3
npm ERR! npm  v2.15.11
npm ERR! code ELIFECYCLE
npm ERR! tryto...@3.8.12 postinstall: `bower install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the tryto...@3.8.12 postinstall script 'bower install'.
npm ERR! This is most likely a problem with the tryton-sao package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     bower install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs tryton-sao
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls tryton-sao
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/gnuhealth/package/npm-debug.log
gnuhealth@linux:~/package>

Seems that the certificate of git is not accepted. From the npm-debug log:
48815 info install tryto...@3.8.12
48816 info postinstall tryto...@3.8.12
48817 verbose unsafe-perm in lifecycle true
48818 info tryto...@3.8.12 Failed to exec postinstall script
48819 verbose stack Error: tryto...@3.8.12 postinstall: `bower install`
48819 verbose stack Exit status 1
48819 verbose stack     at EventEmitter.<anonymous> (/usr/lib64/node_modules/npm/lib/utils/lifecycle.js:217:16)
48819 verbose stack     at emitTwo (events.js:87:13)
48819 verbose stack     at EventEmitter.emit (events.js:172:7)
48819 verbose stack     at ChildProcess.<anonymous> (/usr/lib64/node_modules/npm/lib/utils/spawn.js:24:14)
48819 verbose stack     at emitTwo (events.js:87:13)
48819 verbose stack     at ChildProcess.emit (events.js:172:7)
48819 verbose stack     at maybeClose (internal/child_process.js:854:16)
48819 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)
48820 verbose pkgid tryto...@3.8.12
48821 verbose cwd /home/gnuhealth/package

Can we do some configuration locally that the certificate is accepted?

Thanks!

Cédric Krier

unread,
Mar 6, 2017, 5:30:06 AM3/6/17
to tryton-dev
On 2017-03-06 01:19, Axel Braun wrote:
> Seems that the certificate of git is not accepted. From the npm-debug log:
> 48815 info install tryto...@3.8.12
> 48816 info postinstall tryto...@3.8.12
> 48817 verbose unsafe-perm in lifecycle true
> 48818 info tryto...@3.8.12 Failed to exec postinstall script
> 48819 verbose stack Error: tryto...@3.8.12 postinstall: `bower install`
> 48819 verbose stack Exit status 1
> 48819 verbose stack at EventEmitter.<anonymous>
> (/usr/lib64/node_modules/npm/lib/utils/lifecycle.js:217:16)
> 48819 verbose stack at emitTwo (events.js:87:13)
> 48819 verbose stack at EventEmitter.emit (events.js:172:7)
> 48819 verbose stack at ChildProcess.<anonymous>
> (/usr/lib64/node_modules/npm/lib/utils/spawn.js:24:14)
> 48819 verbose stack at emitTwo (events.js:87:13)
> 48819 verbose stack at ChildProcess.emit (events.js:172:7)
> 48819 verbose stack at maybeClose (internal/child_process.js:854:16)
> 48819 verbose stack at Process.ChildProcess._handle.onexit
> (internal/child_process.js:222:5)
> 48820 verbose pkgid tryto...@3.8.12
> 48821 verbose cwd /home/gnuhealth/package
>
> Can we do some configuration locally that the certificate is accepted?

This is an issue in the configuration of your system which is out of the
realm of Tryton.

--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

Axel Braun

unread,
Mar 6, 2017, 7:22:17 AM3/6/17
to tryton-dev

It is a standard openSUSE Leap 42.1 installation.
Any hint what configuration is needed is appreciated!

Sergi Almacellas Abellana

unread,
Mar 6, 2017, 7:24:56 AM3/6/17
to tryto...@googlegroups.com
El 06/03/17 a les 13:22, Axel Braun ha escrit:
>
> It is a standard openSUSE Leap 42.1 installation.

Indeed i can not reproduce it on Ubuntu. It works as expected.

> Any hint what configuration is needed is appreciated!
It seems that you should add the certificate CA to your system.



--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk

Axel Braun

unread,
Mar 6, 2017, 3:58:44 PM3/6/17
to tryton-dev


Am Montag, 6. März 2017 13:24:56 UTC+1 schrieb Sergi Almacellas Abellana:
El 06/03/17 a les 13:22, Axel Braun ha escrit:
>
> It is a standard openSUSE Leap 42.1 installation.

Indeed i can not reproduce it on Ubuntu. It works as expected.

> Any hint what configuration is needed is appreciated!
It seems that you should add the certificate CA to your system.

 'git config --global http.sslVerify false' did the trick

Cédric Krier

unread,
Mar 6, 2017, 4:20:06 PM3/6/17
to tryton-dev
That makes your system open to mitm attacks.
I do not recommend anyone to do the same.

Axel Braun

unread,
Mar 9, 2017, 8:35:37 AM3/9/17
to tryton-dev


Am Montag, 6. März 2017 22:20:06 UTC+1 schrieb Cédric Krier:
On 2017-03-06 12:58, Axel Braun wrote:
>
>
> Am Montag, 6. März 2017 13:24:56 UTC+1 schrieb Sergi Almacellas Abellana:
> >
> > El 06/03/17 a les 13:22, Axel Braun ha escrit:
> > >
> > > It is a standard openSUSE Leap 42.1 installation.
> >
> > Indeed i can not reproduce it on Ubuntu. It works as expected.
> >
> > > Any hint what configuration is needed is appreciated!
> > It seems that you should add the certificate CA to your system.
> >
>
>  'git config --global http.sslVerify false' did the trick

That makes your system open to mitm attacks.
I do not recommend anyone to do the same. 

I know. Tried the local conf file first, but that did not help.
And as 'my system' is a testing VM, that hardly runs, the workaround is acceptable.

But if anyone has a better solution (except github fixing their certificates), I'm happy to learn....
Reply all
Reply to author
Forward
0 new messages