Awesome! That sounds about right.
We're just hosting our eggs on a webserver, but have been considering
devpi.. sounds like it's been working out well for you so I might give it a
try sooner than later :)
Thanks!
Joe
On Wed, Sep 17, 2014 at 9:58 AM, Stephan Erb
wrote:
> Hi Joe,
>
> we got the
Hi Joe,
we got the build running by following your suggestions!
What did:
* download the proper egg from mesosphere
* convert the egg to a python wheel
* upload the wheel to a local devpi server
(http://doc.devpi.net/latest/) which is started at the beginning of the
build process and killed a
At first I was going to say we should fix up the eggs on PyPI, however the
pypa has sort of side-stepped the 'linux-distro' problem, so if we were to
'fix' the eggs to work on debian, they probably would not work on CentOS or
Fedora anymore.
Can you indeed try patching
https://github.com/apache/in
Stephan,
We sidestepped this problem by upgrading our vagrant image to Ubuntu 14.04
LTS which ships with GLIBC 2.16. I suspect to fix this properly we need to
file a bug against Apache Mesos.
On Tue, Sep 16, 2014 at 10:05 AM, Stephan Erb
wrote:
> Did you find a solution for your question?
>
> I
Did you find a solution for your question?
I am currently having similar issues when trying to run the thermos
executor on Debian 7, which doesn't ship GLIBC 2.16 either. Seems like
we have to patch the Aurora build process (probably in
3rdparty/python/BUILD) to download the correct eggs form
