CKAN: Ticket #982: Remove various pip-requirements versions

status changed; resolution set

anonymous — Sat, 12 Feb 2011 13:46:26 GMT

status changed from new to closed
resolution set to invalid

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

status changed; resolution deleted

rgrp — Sat, 12 Feb 2011 15:44:37 GMT

status changed from closed to reopened
resolution invalid deleted

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

status changed; resolution set

anonymous — Wed, 16 Feb 2011 10:05:32 GMT

status changed from reopened to closed
resolution set to duplicate

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

status changed; resolution deleted

dread — Wed, 23 Feb 2011 17:33:14 GMT

status changed from closed to reopened
resolution duplicate deleted

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

status changed

dread — Wed, 23 Feb 2011 17:34:01 GMT

status changed from reopened to new

status changed; resolution set

dread — Mon, 28 Feb 2011 10:13:00 GMT

status changed from new to closed
resolution set to fixed

Buildbot scripts now fixed.