Comment 9 for bug 701545

Revision history for this message
Martin Pool (mbp) wrote :

This is too hard. Here's where I got to; maybe somebody else can work it out.

As part of <http://pad.lv/701545-oauth>, I want to get Launchpad to use Ubuntu's python-oauth package.

In <https://code.launchpad.net/~mbp/meta-lp-deps/701545-add-dependency/+merge/49536> I added python-oauth as a dependency of launchpad-dependencies, and I have built and installed that package within my vm. So:

% python -c 'import oauth;print oauth'
<module 'oauth' from '/usr/lib/python2.6/dist-packages/oauth/__init__.pyc'>

works as I'd expect.

Even after deleting oauth from download-cache and deleting everything from eggs/, buildout still fails like so:

utilities/shhh.py PYTHONPATH= ./bin/buildout \
                configuration:instance_name=development -c buildout.cfg
While:
  Installing scripts.
  Getting distribution for 'oauth'.
Error: Couldn't find a distribution for 'oauth'.
Develop: '/home/mbp/launchpad/lp-branches/work/.'
Installing scripts.
Couldn't find index page for 'oauth' (maybe misspelled?)
Getting distribution for 'oauth'.

I've removed oauth from versions.cfg and setup.py, so the tree itself shouldn't require it. It looks like buildout is trying to install it as a requirement for some of the packages pulled in through eggs. How do I tell it not to? Surely there must be a way for it to satisfy those dependencies from OS-distributed packages?