New upstream microreleases 9.1.9, 8.4.17
Bug #1163184 reported by
Martin Pitt
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql-8.3 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Raring |
Fix Released
|
Medium
|
Unassigned | ||
postgresql-8.4 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Medium
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
postgresql-9.1 (Ubuntu) |
Fix Released
|
Critical
|
Martin Pitt | ||
Oneiric |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned | ||
Raring |
Fix Released
|
Critical
|
Martin Pitt |
Bug Description
PostgreSQL will announce new upstream microreleases in two days which include three security issues for 9.1 and one for 8.4. I'll update the description with the official annoucement once it goes public. One of the 9.1 ones is a remote data corruption vulnerability, so we need to take special care to not prematurely leak this, as well as push out the updates in timely manner.
Coordinated release time: Thursday, 2013-04-04 15:00 UTC
I cannot add a hardy task to 8.3, so I'll misuse the raring task for the 8.3/hardy update.