Arvados

Answers to outstanding questions:

Brett Smith wrote:

Fix this one way or another. I'm surprised fpm isn't picking them up; it might be worth spending a little time to investigate why that is.

virtualenv's setup.py can work with either setuptools or distutils. It assumes you're running it on the same system you're building it, so when it builds with setuptools, it doesn't declare its own dependency on setuptools. The bug is virtualenv's.

We only backport the virtualenv package for debian7, debian8 and ubuntu1204. Looks like this backport was introduced in the very first checkin of the run-build-packages.sh script. Do we even need this backport?

The Arvados code itself needs virtualenv 1.7. crunch-job uses the --system-site-packages switch, which was added then. At least 1.7 is shipped with all of the distros we support, so a backport doesn't seem to be necessary.

run-tests.sh uses the --setuptools switch, which was added in 1.8.3, which is newer than what's in Debian 7 or Ubuntu 12.04. But this is more of a development dependency than a runtime dependency. We might want to install an fpm-built package on, e.g., our ci server, but I don't see much reason to publish it through our package repositories.

Brett Smith wrote:

run-tests.sh uses the --setuptools switch, which was added in 1.8.3, which is newer than what's in Debian 7 or Ubuntu 12.04.

What I said about versions is true, but it looks like Debian patched this switch in earlier and then upstreamed it. Both distros have that --setuptools switch, so the versions of virtualenv they include are good enough for our purposes. Since that means virtualenv works for both running and developing Arvados out of the box, we can just pull the packages without, e.g., testing for this feature in run-tests, or configuring a specific version on our ci server.