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 <stephan....@blue-yonder.com> wrote: > 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 at the end > * patch the pants.ini to use the devpi server > > Best Regards, > Stephan > > > On 16.09.2014 20:27, Joe Smith wrote: > > 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 > patchinghttps://github.com/apache/incubator-aurora/blob/master/pants.ini#L89 > to a > local mirror where you've built eggs for your version of Debian? If you > decide to go that route, I'd be very interested to hear if you bump into > any build issues! > > On Tue, Sep 16, 2014 at 10:07 AM, Zameer Manji <zma...@twopensource.com> > <zma...@twopensource.com> > wrote: > > > 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 <stephan....@blue-yonder.com > > wrote: > > 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 mesosphere.io instead of using the > default ones on pypi. > > Does anyone have experience in how to do this? > > Thanks, > Stephan > > > > On Sa 30 Aug 2014 08:08:24 CEST, Joe Smith wrote: > > > Howdy all, > > I'm to migrating Apache Aurora<http://aurora.incubator.apache.org/> > <http://aurora.incubator.apache.org/> to mesos 0.20.0[1][2], but am > having an issue using the published dist on > PyPI<https://pypi.python.org/pypi/mesos.native/0.20.0> > <https://pypi.python.org/pypi/mesos.native/0.20.0>. I also gave the > mesosphere-provided (thank you!) > egg<http://mesosphere.io/downloads/#apache-mesos-0.20.0> > <http://mesosphere.io/downloads/#apache-mesos-0.20.0> for Ubuntu > 12.04, and am getting the same stack trace: > > vagrant@192:~$ > PYTHONPATH=/home/vagrant/.pex/install/mesos.native-0.20.0- > py2.7-linux-x86_64.egg.be6632b790cd03172f858e7f875cda > b4ef415ca5/mesos.native-0.20.0-py2.7-linux-x86_64.egg/mesos/ > python2.7 > Python 2.7.3 (default, Feb 27 2014, 19:58:35) > [GCC 4.6.3] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > > import mesos > > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > ImportError: No module named mesos > > import native > > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File > "/home/vagrant/.pex/install/mesos.native-0.20.0-py2.7-linux-x86_64.egg. > be6632b790cd03172f858e7f875cdab4ef415ca5/mesos.native-0.20. > 0-py2.7-linux-x86_64.egg/mesos/native/__init__.py", > line 17, in <module> > from ._mesos import MesosExecutorDriverImpl > ImportError: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.16' not > found (required by > /home/vagrant/.pex/install/mesos.native-0.20.0-py2.7-linux-x86_64.egg. > be6632b790cd03172f858e7f875cdab4ef415ca5/mesos.native-0.20. > 0-py2.7-linux-x86_64.egg/mesos/native/_mesos.so) > > It looks like the issue is it was built with a non-standard glibc (if > I'm following right): > vagrant@192:~/mesos-0.20.0$ /lib/x86_64-linux-gnu/libc.so.6 | grep > release\ version > GNU C Library (Ubuntu EGLIBC 2.15-0ubuntu10) stable release version > 2.15, by Roland McGrath et al. > > Any feedback or suggestions would be greatly appreciated! > > Thanks, > Joe > > [1] https://reviews.apache.org/r/25208/ > [2] https://issues.apache.org/jira/browse/AURORA-674 > > > > > > -- > Zameer Manji > > > > > -- > > Stephan Erb > Software Engineer > *Blue Yonder GmbH* > Ohiostrasse 8 > D-76149 Karlsruhe > > Tel +49 (0)721 383 117 6243 > Fax +49 (0)721 383 117 69 > stephan....@blue-yonder.com > www.blue-yonder.com > Registergericht Mannheim, HRB 704547 > USt-IdNr. DE DE 277 091 535 > Geschäftsführer: Jochen Bossert, Uwe Weiss (CEO) > > <http://www.datalympics.com> >
