add psycopg2 to launchpad-dependencies

Bug #206471 reported by James Henstridge
2
Affects Status Importance Assigned to Milestone
Launchpad Dependencies
Fix Released
Undecided
Guilherme Salgado

Bug Description

When we integrate Storm, we'll need psycopg2 as a dependency of launchpad-dependencies and an up to date version of psycopg2 in the lpdebs archive.

Unfortunately we require an unreleased version of psycopg2 (I am working towards getting it released, but am not there yet).

I've put together some pre-release packages in my PPA for gutsy and hardy, but haven't looked at backporting them to dapper:

    https://launchpad.net/~jamesh/+archive

We'll want 2.0.7 packages once they're released.

Changed in meta-lp-deps:
assignee: nobody → salgado
status: New → Confirmed
Revision history for this message
Guilherme Salgado (salgado) wrote :

Can I add psycopg2 as a dependency before we switch to storm or do I need to wait for the switch?

As for dapper's psycopg2, can't you use PPA to build the gutsy one in dapper and see if it works?

Revision history for this message
James Henstridge (jamesh) wrote :

There won't be any problem adding it to launchpad-dependencies before the switch. Psycopg1 and psycopg2 have different Python module names, so won't conflict with each other.

As for a dapper package, I got a failed build when I submitted a PPA build. I think the Python infrastructure has changed a bit in the last year or so.

Revision history for this message
Guilherme Salgado (salgado) wrote :

The most recent version of launchpad-dependencies in hardy should fix this. I didn't fix the gutsy package because at the point this becomes necessary I expect everybody to be running hardy.

Changed in meta-lp-deps:
status: Confirmed → In Progress
Changed in meta-lp-deps:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.