New bug fix releases: 9.1.3, 8.4.11, 8.3.18
Bug #941912 reported by
Martin Pitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql-8.3 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Fix Released
|
Undecided
|
Unassigned | ||
postgresql-8.4 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned | ||
Natty |
Fix Released
|
Undecided
|
Unassigned | ||
postgresql-9.1 (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Oneiric |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Martin Pitt |
Bug Description
PostgreSQL published new microreleases today: http://
These include three security fixes and thus should go via -security.
no longer affects: | postgresql-9.1 (Ubuntu Hardy) |
no longer affects: | postgresql-9.1 (Ubuntu Lucid) |
no longer affects: | postgresql-9.1 (Ubuntu Maverick) |
no longer affects: | postgresql-9.1 (Ubuntu Natty) |
To post a comment you must log in.
I am just uploading 9.3.1-1 to Debian unstable and will sync it after the Beta-1 release.