Remove various pip-requirements versions

[rgrp]

We can just use the branch name to pull down specific versions of pip requirements so we don't need all the different versions in head.

Remove them and update any client systems.

Cost: 20m

[anonymous]

Well we could transfer all the dependencies and version numbers to a config file for the fabfile, but we don't achieve much.

[rgrp]

I don't think i understand why this has been closed (and it would surely be wontfix rather than invalid ...).

Let me explain in more detail: we would move to having one and only one pip-requirements.txt in the repo at any given revision and it would simply have the correct info for whatever branch/revision it was on. At the moment we are having extra pip-requirements-....txt for labelling branch pip-requirements when we could just the branching facility of mercurial.

You'd do

wget http://bitbucket.org/okfn/ckan/src/metastable/pip-requirements.txt

rather than

wget http://bitbucket.org/okfn/ckan/src/default/pip-requirements-metastable.txt

[anonymous]

This is now rolled into #963. Marking as duplicate.

People can get the pip from a branch over HTTP like this:

​https://bitbucket.org/okfn/ckan/src/<branch-name>/path/to/file/you/want

[dread]

Need to do this for older branches which isn't subject to #963.

[dread]

Buildbot scripts now fixed.