[Pharo-project] ssl fails on build CI
The FileSystem-Git builds on CI generate many test failures because the SSL plugin is missing (apparently) here's the output: https://ci.inria.fr/pharo-contribution/job/FileSystem-Git/6/PHARO=20,VERSION.... Is that to be expected? I gathered from a recent thread that at least libssl should be present on the CI servers. Or do I need to change something in the configuration? Max
I just discovered that this only affects Pharo20 builds and older Pharo30 On 28.04.2013, at 21:07, Max Leske <maxleske@gmail.com> wrote:
The FileSystem-Git builds on CI generate many test failures because the SSL plugin is missing (apparently) here's the output: https://ci.inria.fr/pharo-contribution/job/FileSystem-Git/6/PHARO=20,VERSION....
Is that to be expected? I gathered from a recent thread that at least libssl should be present on the CI servers. Or do I need to change something in the configuration?
Max
fixed it: aptitude install libssl0.9.8:i386 On 2013-04-28, at 21:17, Max Leske <maxleske@gmail.com> wrote:
I just discovered that this only affects Pharo20 builds and older Pharo30
On 28.04.2013, at 21:07, Max Leske <maxleske@gmail.com> wrote:
The FileSystem-Git builds on CI generate many test failures because the SSL plugin is missing (apparently) here's the output: https://ci.inria.fr/pharo-contribution/job/FileSystem-Git/6/PHARO=20,VERSION....
Is that to be expected? I gathered from a recent thread that at least libssl should be present on the CI servers. Or do I need to change something in the configuration?
Max
what you think shall we retarget linux VM to build with newer ssl version? On 28 April 2013 23:30, Camillo Bruni <camillobruni@gmail.com> wrote:
fixed it: aptitude install libssl0.9.8:i386
On 2013-04-28, at 21:17, Max Leske <maxleske@gmail.com> wrote:
I just discovered that this only affects Pharo20 builds and older Pharo30
On 28.04.2013, at 21:07, Max Leske <maxleske@gmail.com> wrote:
The FileSystem-Git builds on CI generate many test failures because the SSL plugin is missing (apparently) here's the output: https://ci.inria.fr/pharo-contribution/job/FileSystem-Git/6/PHARO=20,VERSION....
Is that to be expected? I gathered from a recent thread that at least libssl should be present on the CI servers. Or do I need to change something in the configuration?
Max
-- Best regards, Igor Stasenko.
On 2013-04-29, at 00:21, Igor Stasenko <siguctua@gmail.com> wrote:
what you think shall we retarget linux VM to build with newer ssl version?
that's gonna be the same mess again and we do not care for the slaves as we manage them by ourselves. for user-level experience we have to advocate the deb package which solves this issue properly.
Thanks! On 29.04.2013, at 00:28, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-04-29, at 00:21, Igor Stasenko <siguctua@gmail.com> wrote:
what you think shall we retarget linux VM to build with newer ssl version?
that's gonna be the same mess again and we do not care for the slaves as we manage them by ourselves.
for user-level experience we have to advocate the deb package which solves this issue properly.
On Mon, Apr 29, 2013 at 12:28 AM, Camillo Bruni <camillobruni@gmail.com> wrote:
that's gonna be the same mess again and we do not care for the slaves as we manage them by ourselves
for not so old slaves, we should use the .deb files as well -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
participants (4)
-
Camillo Bruni -
Damien Cassou -
Igor Stasenko -
Max Leske