[ubuntu/zesty-proposed] postgresql-plproxy 2.7-1ubuntu1 (Accepted)

[Nishanth Aravamudan]

postgresql-plproxy (2.7-1ubuntu1) zesty; urgency=medium

  * d/t/installcheck fixes:
    - Passing a port to pg_virtualenv even with newnet does not avoid
      port collisions, as pg_virtualenv (via pg_createcluster) is only
      looking at the configured clusters on the filesystem, not what is
      running in the current network namespace. Set an alternative
      PG_CLUSTER_CONF_ROOT instead, and set it before we call
      pg_virtualenv.
    - Set the socket directory for pg_createcluster, as we are using the
      standard port and that can lead to conflicts. This also requires
      making the AUTOPKGTEST_TMP directory world-writeable so the
      postgres user can write socket information there.

Date: Tue, 28 Feb 2017 10:19:53 -0800
Changed-By: Nishanth Aravamudan <nish.aravamudan at canonical.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/postgresql-plproxy/2.7-1ubuntu1
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 28 Feb 2017 10:19:53 -0800
Source: postgresql-plproxy
Binary: postgresql-9.6-plproxy
Architecture: source
Version: 2.7-1ubuntu1
Distribution: zesty
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Nishanth Aravamudan <nish.aravamudan at canonical.com>
Description:
 postgresql-9.6-plproxy - database partitioning system for PostgreSQL 9.6
Changes:
 postgresql-plproxy (2.7-1ubuntu1) zesty; urgency=medium
 .
   * d/t/installcheck fixes:
     - Passing a port to pg_virtualenv even with newnet does not avoid
       port collisions, as pg_virtualenv (via pg_createcluster) is only
       looking at the configured clusters on the filesystem, not what is
       running in the current network namespace. Set an alternative
       PG_CLUSTER_CONF_ROOT instead, and set it before we call
       pg_virtualenv.
     - Set the socket directory for pg_createcluster, as we are using the
       standard port and that can lead to conflicts. This also requires
       making the AUTOPKGTEST_TMP directory world-writeable so the
       postgres user can write socket information there.
Checksums-Sha1:
 b599b400701c53f5f1edc31840db36d85a51a4cd 1981 postgresql-plproxy_2.7-1ubuntu1.dsc
 5d41ad0e1cf21337cdd989045358c39439a2363c 4448 postgresql-plproxy_2.7-1ubuntu1.debian.tar.xz
Checksums-Sha256:
 aca4596bf6ec152c24d00aea4924e6b4f9c593ba4f7882e9df3f85fbc7d7ad74 1981 postgresql-plproxy_2.7-1ubuntu1.dsc
 0a5f13bfafb9af0291f5fc531df09c06ca678f07003ba141ec4425bbf9f86ea9 4448 postgresql-plproxy_2.7-1ubuntu1.debian.tar.xz
Files:
 01a0453b1f515eae7efa1af640a10928 1981 database optional postgresql-plproxy_2.7-1ubuntu1.dsc
 c95de342bff0f3933a116727dc8bb082 4448 database optional postgresql-plproxy_2.7-1ubuntu1.debian.tar.xz
Original-Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public at lists.alioth.debian.org>

-----BEGIN PGP SIGNATURE-----

iQE7BAEBCAAlBQJYtfB2HhxuaXNoLmFyYXZhbXVkYW5AY2Fub25pY2FsLmNvbQAK
CRADRGyeZjIE+AFmB/9qOF/BYZ2i2ZUFb5++Eft524Z5RaDwyNZivQy0AzNQHgn1
CbkwLTcW0HFT45m8hQFe+AqC6D2p/0m4qEBLNjy+5xPOCifc2Eatlt0N/IKhBHFQ
eX42oMZzr1+QNfJB4HKLfteLoW0uTgqJ/6fVJCBEmGOVcaFQJv1c5zPsclCyW1do
1wydOx829z0j8WIovlOHmkHg4R/XJ5ZEt4J5MZwLTW6WlhbBCWKZxtiSbPwJDdCO
3jFkFVf3t6j2Kgxhn3JO1Yr1kuQN/5TqLrAukTSxVCah7TO78tyJKcU753FS7W+P
x+pzYBLJjcL/7vOFzcnaX1bPETfxomOF1Fk+PD1V
=rYF1
-----END PGP SIGNATURE-----