New upstream microreleases 9.3.17, 9.5.7 and 9.6.3

[Christian Ehrhardt]

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

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

[Christian Ehrhardt (paelzer)]

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

[Christian Ehrhardt (paelzer)]

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.

[Christian Ehrhardt (paelzer)]

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.

[Brian Murray (brian-murray)]

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

[Brian Murray (brian-murray)]

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)]

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)]

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!

[Christian Ehrhardt (paelzer)]

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.

[Christian Ehrhardt (paelzer)]

Still missing Trusty to be releases as the others - ping

[Christian Ehrhardt (paelzer)]

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)]

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!

[Christian Ehrhardt (paelzer)]

Thanks Brian for also accepting Trusty.

Ok, following up on tests to get this migrating - excluding known acceptable cases as outlined in comment #10.

1. Trusty - ok (only accepted cases)
2. Xenial - ok (only accepted cases)
3. Yakkety
  3.1 armhf postgresql - accepted known case
  3.2 linux - just crashing because it compiles slowly and times out.
      It seems to be unrelated to postgresql, see [1]
  3.3 mongodb - as with Linux above this seems not postgresql-related.
      Checking [2] one can see that this is an transient issue that occurs all too often.
4. Zesty - all ok

I opened [3] and [4] for the issues above at packages they belong to, but for this MRE IMHO we look good.

That said, setting verification-done.

[1]: http://autopkgtest.ubuntu.com/packages/linux/yakkety/armhf
[2]: http://autopkgtest.ubuntu.com/packages/mongodb/yakkety/armhf
[3]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694237
[4]: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1694253

[Launchpad Janitor (janitor)]

This bug was fixed in the package postgresql-9.6 - 9.6.3-0ubuntu0.17.04

---------------
postgresql-9.6 (9.6.3-0ubuntu0.17.04) zesty; urgency=medium

  * New upstream release (LP: #1690730)
    - Restrict visibility of pg_user_mappings.umoptions, to protect passwords
      stored as user mapping options (CVE-2017-7486)
    - Prevent exposure of statistical information via leaky operators
      (CVE-2017-7484)
    - Restore libpq's recognition of the PGREQUIRESSL environment variable
      (CVE-2017-7485)

    - A dump/restore is not required for those running 9.6.X.
    - However, if you use foreign data servers that make use of user passwords
      for authentication, see the first changelog entry.
    - Also, if you are using third-party replication tools that depend on
      "logical decoding", see the fourth changelog entry.

    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.6/static/release-9-6-3.html

 -- Christian Ehrhardt <email address hidden> Mon, 15 May 2017 08:46:09 +0200

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for postgresql-9.6 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Łukasz Zemczak (sil2100)]

Ok, I see the mimeo armhf failure is something that's been around since every postgresql version in yakkety [1]. Would be nice if someone finally had a look at that though!

[1] http://autopkgtest.ubuntu.com/packages/m/mimeo/yakkety/armhf

[Launchpad Janitor (janitor)]

This bug was fixed in the package postgresql-9.5 - 9.5.7-0ubuntu0.16.10

---------------
postgresql-9.5 (9.5.7-0ubuntu0.16.10) yakkety; urgency=medium

  * New upstream release (LP: #1690730)
    - Restrict visibility of pg_user_mappings.umoptions, to protect passwords
      stored as user mapping options (CVE-2017-7486)
    - Prevent exposure of statistical information via leaky operators
      (CVE-2017-7484)
    - Restore libpq's recognition of the PGREQUIRESSL environment variable
      (CVE-2017-7485)

    - A dump/restore is not required for those running 9.5.X.
    - However, if you use foreign data servers that make use of user passwords
      for authentication, see the first changelog entry.
    - Also, if you are using third-party replication tools that depend on
      "logical decoding", see the fourth changelog entry.

    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.5/static/release-9-5-7.html

 -- Christian Ehrhardt <email address hidden> Mon, 15 May 2017 08:46:09 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package postgresql-9.5 - 9.5.7-0ubuntu0.16.04

---------------
postgresql-9.5 (9.5.7-0ubuntu0.16.04) xenial; urgency=medium

  * New upstream release (LP: #1690730)
    - Restrict visibility of pg_user_mappings.umoptions, to protect passwords
      stored as user mapping options (CVE-2017-7486)
    - Prevent exposure of statistical information via leaky operators
      (CVE-2017-7484)
    - Restore libpq's recognition of the PGREQUIRESSL environment variable
      (CVE-2017-7485)

    - A dump/restore is not required for those running 9.5.X.
    - However, if you use foreign data servers that make use of user passwords
      for authentication, see the first changelog entry.
    - Also, if you are using third-party replication tools that depend on
      "logical decoding", see the fourth changelog entry.

    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.5/static/release-9-5-7.html

 -- Christian Ehrhardt <email address hidden> Mon, 15 May 2017 08:46:07 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package postgresql-9.3 - 9.3.17-0ubuntu0.14.04

---------------
postgresql-9.3 (9.3.17-0ubuntu0.14.04) trusty; urgency=medium

  * New upstream release (LP: #1690730)
    - Restrict visibility of pg_user_mappings.umoptions, to protect passwords
      stored as user mapping options (CVE-2017-7486)
    - Prevent exposure of statistical information via leaky operators
      (CVE-2017-7484)
    - Restore libpq's recognition of the PGREQUIRESSL environment variable
      (CVE-2017-7485)

    - A dump/restore is not required for those running 9.3.X.
    - However, if you use foreign data servers that make use of user passwords
      for authentication, see the first changelog entry.

    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.3/static/release-9-3-17.html

 -- Christian Ehrhardt <email address hidden> Mon, 15 May 2017 08:45:01 +0200