You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2015/05/15 10:06:59 UTC
[jira] [Commented] (MESOS-2699) Unable to build on debian jessie
[ https://issues.apache.org/jira/browse/MESOS-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545122#comment-14545122 ]
Adam B commented on MESOS-2699:
-------------------------------
[~tpitluga] Try `./configure --disable-bundled-pip`, maybe with an optional `--with-pip=DIR` if pip is not already in PYTHONPATH.
That said, we should also consider upgrading our bundled pip version.
> Unable to build on debian jessie
> --------------------------------
>
> Key: MESOS-2699
> URL: https://issues.apache.org/jira/browse/MESOS-2699
> Project: Mesos
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.22.0
> Environment: here is a dockerfile to reproduce:
> FROM debian:jessie
>
> RUN DEBIAN_FRONTEND=noninteractive apt-get -y update
> RUN DEBIAN_FRONTEND=noninteractive apt-get -y install \
> apt-utils \
> build-essential \
> autoconf \
> libtool \
> libcurl4-nss-dev \
> libsasl2-dev \
> libapr1-dev \
> libsvn-dev \
> zlib1g-dev \
> git
>
> RUN DEBIAN_FRONTEND=noninteractive apt-get -y install \
> openjdk-7-jdk \
> python-dev \
> python-boto \
> maven \
> ruby2.1 \
> ruby2.1-dev
>
> RUN update-alternatives --install /usr/bin/gem gem /usr/bin/gem2.1 1 && \
> update-alternatives --install /usr/bin/ruby ruby /usr/bin/ruby2.1 1
>
> RUN mkdir /build
>
> WORKDIR /build
>
> RUN gem install fpm
>
> ENV MAINTAINER="devs+cosmos@getbraintree.com"
>
> RUN git clone https://github.com/mesosphere/mesos-deb-packaging.git
> RUN cd mesos-deb-packaging && \
> ./build_mesos
> Reporter: Tony Pitluga
> Priority: Minor
>
> Debian Jessie deprecated SSLV3 and has removed support for it in python's urllib. The version of requests (2.3) vendored into mesos inside of the 3rdparty/pip-1.5.6.tar.gz bombs out with this error:
> Traceback (most recent call last):
> File "<string>", line 1, in <module>
> File "/build/mesos-deb-packaging/mesos-repo/build/3rdparty/pip-1.5.6/pip/__init__.py", line 11, in <module>
> from pip.vcs import git, mercurial, subversion, bazaar # noqa
> File "/build/mesos-deb-packaging/mesos-repo/build/3rdparty/pip-1.5.6/pip/vcs/mercurial.py", line 9, in <module>
> from pip.download import path_to_url
> File "/build/mesos-deb-packaging/mesos-repo/build/3rdparty/pip-1.5.6/pip/download.py", line 22, in <module>
> from pip._vendor import requests, six
> File "/build/mesos-deb-packaging/mesos-repo/build/3rdparty/pip-1.5.6/pip/_vendor/requests/__init__.py", line 53, in <module>
> from .packages.urllib3.contrib import pyopenssl
> File "/build/mesos-deb-packaging/mesos-repo/build/3rdparty/pip-1.5.6/pip/_vendor/requests/packages/urllib3/contrib/pyopenssl.py", line 70, in <module>
> ssl.PROTOCOL_SSLv3: OpenSSL.SSL.SSLv3_METHOD,
> AttributeError: 'module' object has no attribute 'PROTOCOL_SSLv3'
> This post on stack overflow seems to indicate this is fixed in requests 2.6.
> http://stackoverflow.com/questions/28987891/patch-pyopenssl-for-sslv3-issue
> Is there a script somewhere to build the pip tarball or a flag I can pass to use the system version of pip?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)