pygresql ftbfs due to postgresql upstream changes
Bug #79116 reported by
Matthias Klose
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| postgresql-8.2 (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
| pygresql (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Bug Description
postgres changes seem to be the cause, not python changes.
| Changed in pygresql: | |
| assignee: | nobody → pitti |
| importance: | Undecided → Medium |
| status: | Unconfirmed → Confirmed |
| Changed in pygresql: | |
| importance: | Medium → High |
| status: | Confirmed → In Progress |
Revision history for this message
| Martin Pitt (pitti) wrote | #1 |
| Changed in postgresql-8.2: | |
| assignee: | nobody → pitti |
| importance: | Undecided → High |
| status: | Unconfirmed → In Progress |
| status: | In Progress → Fix Released |
Revision history for this message
| Martin Pitt (pitti) wrote | #2 |
| Changed in pygresql: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Martin Pitt (pitti) wrote | #3 |
| Changed in pygresql: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
postgresql-8.2 (8.2.1-1ubuntu1) feisty; urgency=low
.
* debian/