New upstream microreleases 9.1.16, 9.3.7, 9.4.2
Bug #1457093 reported by
Martin Pitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql-9.1 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Marc Deslauriers | ||
Trusty |
Fix Released
|
Undecided
|
Marc Deslauriers | ||
postgresql-9.3 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Marc Deslauriers | ||
postgresql-9.4 (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Utopic |
Fix Released
|
Undecided
|
Marc Deslauriers | ||
Vivid |
Fix Released
|
Undecided
|
Marc Deslauriers | ||
Wily |
Fix Released
|
High
|
Martin Pitt |
Bug Description
PostgreSQL will push out new microreleases on Friday, 2015-05-22. The tarballs for the updates are not public yet, but the fixes are visible in the upstream git, so there's no need to treat this as embargoed, but there should still be a coordinated release. These fix a couple of security issues, as well as the usual set of bug fixes.
Upstream announcement: http://
Changed in postgresql-9.4 (Ubuntu Vivid): | |
assignee: | nobody → Martin Pitt (pitti) |
Changed in postgresql-9.4 (Ubuntu Vivid): | |
status: | New → In Progress |
description: | updated |
Changed in postgresql-9.4 (Ubuntu Wily): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
As usual, wily will be fixed via syncing from Debian unstable. Christoph already prepared 9.4.2-1 in git.