desktop-packages team mailing list archive

[Chris J Arges <1461425@xxxxxxxxxxxxxxxxxx>]

Hello Martin, or anyone else affected,

Accepted postgresql-9.4 into utopic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/postgresql-9.4/9.4.3-0ubuntu0.14.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 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!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1461425

Title:
  New upstream microreleases 9.1.17, 9.3.8, 9.4.3 - fixes regression in
  previous update

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.4 package in Ubuntu:
  In Progress
Status in postgresql-9.1 source package in Precise:
  Fix Committed
Status in postgresql-9.1 source package in Trusty:
  Fix Committed
Status in postgresql-9.3 source package in Trusty:
  Fix Committed
Status in postgresql-9.4 source package in Utopic:
  Fix Committed
Status in postgresql-9.4 source package in Vivid:
  In Progress
Status in postgresql-9.4 source package in Wily:
  In Progress
Status in postgresql-9.1 package in Debian:
  Unknown

Bug description:
  Upstream will push out new microreleases tomorrow after a pretty
  severe regression in the previous rounds of updates:

  https://wiki.postgresql.org/wiki/May_2015_Fsync_Permissions_Bug#I.27ve_hit_this_bug_and_I_can.27t_restart_Postgres._What_do_I_do.3F

  This particularly affects 9.1 due to the way we handle SSL
  certificates, i. e. Ubuntu 12.04. Later releases are much less
  affected as we don't have to symlink the certificate there any more.

  SRU TEST CASE:

    * install postgresql-9.1
    * pkill -SEGV postgres
    * service postgresql start

  With 9.1.16 this will fail with

  The PostgreSQL server failed to start. Please check the log output:
  2015-06-03 09:16:35 CEST LOG:  database system was interrupted; last known up at 2015-06-03 09:15:27 CEST
  2015-06-03 09:16:35 CEST FATAL:  could not open file "/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
  2015-06-03 09:16:35 CEST LOG:  startup process (PID 10527) exited with exit code 1
  2015-06-03 09:16:35 CEST LOG:  aborting startup due to startup process failure

  With 9.1.17 (or earlier versions than 9.1.16) this should succeed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1461425/+subscriptions