Hi Chris:

> Without redis installed there are now just 4 xfailures:

Those are expected failures. So the tests all pass.

My open questions are:

  1) We are using:

    pip install setuptools && pip install gpg --no-build-isolation

  do you have any idea what changed to require a new setuptools to be
installed?

  My assumption is that whatever setuptools version is in use in the
newest docker
  image is newer than or the same as a prior docker image where gpg
2.0.0 built ok.

  What does --no-build-isolation (NBI) do in this case? I am not
installing into a virtual
  environment where I thought that was a useful flag. Does NBI prevent
gpg from building
  in a virtual environment where it could be missing some components?

  2) Do we expect the install to work in a venv?

  The docker image as it currently exists does not install/run Roundup
in a venv. However,
  I have been experimenting with installing Roundup and its supporting
modules in a venv.
  The base image sometimes has older versions of packages installed.
While a newer release
  of the base image fixed this, I was using a newer version of these
packages on the
  older base image and just hoped I didn't break any tools. By
installing in a venv I isolate
  upgraded packages from the base image. Also I am adopting venv as the
standard way to install
  Roundup. By using a venv in the Docker container I hope to reduce the
documentation needed
  for other layouts by ignoring them 8-).

Thanks for your help on this.

-- rouilj