It's unfortunately beyond our control. Those are third-party dependencies.
Another option is to take each dependency and generate wheel packages from
those outside of the container, copy them in, and install from there. Or
put them on a custom PyPI or something and install from that.
Christian
-
I've solved it by installing the compiler and some other packages, and
uninstalling the compiler and it's dependencies after installing
ReviewBoard. Not particularly happy about this solution...
--
Supercharge your Review Board with Power Pack:
https://www.reviewboard.org/powerpack/
Want us to
Sorry, I missread. It's *cffi* that fails. But, if I understand this
correctly, *cffi* is already compiled, from what I can see here:
http://pythonwheels.com/
marți, 28 iunie 2016, 14:03:13 UTC+3, Ovidiu-Florin BOGDAN a scris:
>
> I've changed and now using pip. It still fails and asking for a c
I've changed and now using pip. It still fails and asking for a compiler
for cryptography.
Here is my new Dockerfile:
FROM debian:8
MAINTAINER Ovidiu-Florin Bogdan (ovidiu.bog...@foo.com)
ENV DEBIAN_FRONTEND noninteractive
RUN apt update && apt install -y \
patch \
subversion \
mem
Hi,
Some of our dependencies themselves have dependencies that need
compilation. In this case, my guess is the version of the module from the
apt repository is just too old.
Can you show the entire easy_install log? That'll help me see what package
might be depending on this.
In general, I'd sug
Hello,
I'm trying to set up the latest ReviewBoard in a Docker container and I'm
getting a error while it's installing the cryptography python module:
Searching for cryptography>=1.1
Reading https://pypi.python.org/simple/cryptography/
Best match: cryptography 1.4
Downloading https:
//pypi.pytho
