New upstream microreleases 9.3.17, 9.5.7 and 9.6.3

Bug #1690730 reported by ChristianEhrhardt on 2017-05-15
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
postgresql-9.3 (Ubuntu)
High
Unassigned
Trusty
High
Unassigned
postgresql-9.5 (Ubuntu)
High
Unassigned
Xenial
High
Unassigned
Yakkety
High
Unassigned
postgresql-9.6 (Ubuntu)
High
Unassigned
Zesty
High
Unassigned

Bug Description

https://www.postgresql.org/about/news/1746/

As per the standing micro-release exception these should land in stable Ubuntu releases.

ChristianEhrhardt (paelzer) wrote :

Artful already synced, T,X,Y,Z to go

Changed in postgresql-9.5 (Ubuntu):
status: New → Triaged
importance: Undecided → High
Changed in postgresql-9.5 (Ubuntu Trusty):
status: New → Triaged
Changed in postgresql-9.5 (Ubuntu Xenial):
status: New → Triaged
Changed in postgresql-9.5 (Ubuntu Yakkety):
status: New → Triaged
Changed in postgresql-9.5 (Ubuntu Zesty):
status: New → Triaged
Changed in postgresql-9.5 (Ubuntu Trusty):
importance: Undecided → High
Changed in postgresql-9.5 (Ubuntu Xenial):
importance: Undecided → High
Changed in postgresql-9.5 (Ubuntu Yakkety):
importance: Undecided → High
Changed in postgresql-9.5 (Ubuntu Zesty):
importance: Undecided → High
ChristianEhrhardt (paelzer) wrote :

Ok, all bileto runs are good, except the known issues on armhf tests - but these are fixed in >=zesty and known - Quoting Pitti on that from the last few stable updates:

"These are fallout from moving from LXC to LXD. For devel I fixed the latter in https://anonscm.debian.org/cgit/pkg-postgresql/postgresql-common.git/commit/?id=fc40fc34ce -- functionally everything is correct, the test just failed on unexpected stderr output from a warning in netstat."

Note related bileto tickets:
https://bileto.ubuntu.com/#/ticket/2762
https://bileto.ubuntu.com/#/ticket/2763

So we are all set and pre-confirmed - pushing to SRU queue now.

ChristianEhrhardt (paelzer) wrote :

The X/Y/Z ticket didn't want to publish from bileto so I uploaded directly - but it is the same changes file so the results should apply still.

Waiting for SRU processing now.

Changed in postgresql-9.5 (Ubuntu Trusty):
status: Triaged → Fix Committed
Changed in postgresql-9.5 (Ubuntu Xenial):
status: Triaged → Fix Committed
Changed in postgresql-9.5 (Ubuntu Yakkety):
status: Triaged → Fix Committed
Changed in postgresql-9.5 (Ubuntu Zesty):
status: Triaged → Fix Committed
Brian Murray (brian-murray) wrote :

This needs a postrgresql-9.6, since that is a different source package, for Zesty.

Changed in postgresql-9.6 (Ubuntu Zesty):
status: New → Fix Committed
tags: added: verification-needed

Hello ChristianEhrhardt, or anyone else affected,

Accepted postgresql-9.6 into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.6/9.6.3-0ubuntu0.17.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Brian Murray (brian-murray) wrote :

Hello ChristianEhrhardt, or anyone else affected,

Accepted postgresql-9.5 into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.5/9.5.7-0ubuntu0.16.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Brian Murray (brian-murray) wrote :

Hello ChristianEhrhardt, or anyone else affected,

Accepted postgresql-9.5 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.5/9.5.7-0ubuntu0.16.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in postgresql-9.3 (Ubuntu Trusty):
status: New → Fix Committed
no longer affects: postgresql-9.3 (Ubuntu Xenial)
no longer affects: postgresql-9.3 (Ubuntu Yakkety)
no longer affects: postgresql-9.3 (Ubuntu Zesty)
no longer affects: postgresql-9.5 (Ubuntu Trusty)
no longer affects: postgresql-9.5 (Ubuntu Zesty)
no longer affects: postgresql-9.6 (Ubuntu Yakkety)
no longer affects: postgresql-9.6 (Ubuntu Trusty)
no longer affects: postgresql-9.6 (Ubuntu Xenial)
Changed in postgresql-9.6 (Ubuntu):
status: New → Triaged
Changed in postgresql-9.3 (Ubuntu):
status: New → Triaged
importance: Undecided → High
Changed in postgresql-9.3 (Ubuntu Trusty):
importance: Undecided → High
Changed in postgresql-9.6 (Ubuntu):
importance: Undecided → High
Changed in postgresql-9.6 (Ubuntu Zesty):
importance: Undecided → High
ChristianEhrhardt (paelzer) wrote :

Updated the status to match status correctly per-PG-version.
Note: Trusty is not yet accepted - the others are so far fine, I just retriggered a few known to be shaky tests and will look deeper if some of them appear not to resolve.

ChristianEhrhardt (paelzer) wrote :

Still missing Trusty to be releases as the others - ping

ChristianEhrhardt (paelzer) wrote :

Checking in on tests:

Not listing the known and acceptable issues on
- known armhf failure (ok)
- mimeo on armhf

0. Trusty (still blocked in unapproved)
1. Xenial ok
2. Yakkety ok
  2.1 there is one odd kernel issue
3. Zesty
  3.1 the same kernel issue as on yakkety, seems to be a timeout on rebuilding the kernel - it doesn't really seem triggered by the postgres update (I polled the kernel Team on any experience on that - the answer was "likely transient please retrigger").
  3.2 now here something is going on:
  - cockpit, csync, diaspora-installer, mbuffer, python, ruby: Of those most where timeouts or connection issues - for now we should store the logs and retrigger to see if they resolve.

Since I lack the powers (triggers are bound to upload rights) I'll ask Nish

Brian Murray (brian-murray) wrote :

Hello ChristianEhrhardt, or anyone else affected,

Accepted postgresql-9.3 into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.3/9.3.17-0ubuntu0.14.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers