Resolve conflicting dependencies from source swift and docker registry

[ghost]

12. Swift installed by source docker-registry dependency causes overwrite:
    This was another tricky one to debug, essentially half way through the script the SWIFT client stopped working all together. After a lot of digging (and some help from Eran) the root cause was once of the dependencies, namely docker-registry, which has the following requirements file:
    boto==2.19.0
    backports.lzma==0.0.2
    Flask==0.9
    PyYAML==3.10
    simplejson==3.1.3
    requests==1.2.0
    gunicorn==18.0
    gevent==0.13.8
    newrelic==1.13.1.31
    blinker==1.3
    python-glanceclient==0.10.0
    python-keystoneclient==0.3.1
    python-swiftclient==1.8.0
    redis==2.8.0
    rsa==3.1.2
    These are all pretty old but the main issue is for an install from source, we'll still go ahead and grab the package above, which is quite a bit older, and many of its dependencies will not exist, implying it can't be executed.
    So I believe docker-registry has actually been depreciated, the newer variant doesn't seem to have these dependencies, essentially you need to pull in whatever client you want. Anyway this is something for us to look at further.