[ubuntu/lucid-proposed] postgresql-common 106ubuntu1 (Accepted)

Martin Pitt martin.pitt at ubuntu.com
Thu Oct 21 22:37:18 BST 2010


postgresql-common (106ubuntu1) lucid-proposed; urgency=low

  * t/030_errors.t: Check that pg_createcluster leaves the original one
    intact if the cluster already exists, also when the original one is not
    running. This reproduces LP #661061/Debian #597097.
  * pg_createcluster: Be more careful with cleaning up the created cluster if
    an error occurs: Do not start the cleanup until we actually passed our
    sanity checks and created files for the new cluster.  Before, it would
    erroneously remove an already existing cluster on a sanity check fail, if
    that cluster happened to not be running at the time. (LP: #661061)
    Patches cherrypicked from trunk r1024.
  * debian/control: Set Vcs-Bzr to lucid branch.

Date: Mon, 18 Oct 2010 11:04:24 +0200
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Maintainer: Martin Pitt <mpitt at debian.org>
https://launchpad.net/ubuntu/lucid/+source/postgresql-common/106ubuntu1
-------------- next part --------------
Format: 1.8
Date: Mon, 18 Oct 2010 11:04:24 +0200
Source: postgresql-common
Binary: postgresql-common postgresql-client-common
Architecture: source
Version: 106ubuntu1
Distribution: lucid-proposed
Urgency: low
Maintainer: Martin Pitt <mpitt at debian.org>
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Description: 
 postgresql-client-common - manager for multiple PostgreSQL client versions
 postgresql-common - PostgreSQL database-cluster manager
Launchpad-Bugs-Fixed: 661061
Changes: 
 postgresql-common (106ubuntu1) lucid-proposed; urgency=low
 .
   * t/030_errors.t: Check that pg_createcluster leaves the original one
     intact if the cluster already exists, also when the original one is not
     running. This reproduces LP #661061/Debian #597097.
   * pg_createcluster: Be more careful with cleaning up the created cluster if
     an error occurs: Do not start the cleanup until we actually passed our
     sanity checks and created files for the new cluster.  Before, it would
     erroneously remove an already existing cluster on a sanity check fail, if
     that cluster happened to not be running at the time. (LP: #661061)
     Patches cherrypicked from trunk r1024.
   * debian/control: Set Vcs-Bzr to lucid branch.
Checksums-Sha1: 
 3d5b50485ef974841ed3ce07a37d3b36ce288ac3 1576 postgresql-common_106ubuntu1.dsc
 38edcaa176caca760c1cef8ee67838085ee33df9 120874 postgresql-common_106ubuntu1.tar.gz
Checksums-Sha256: 
 4ae0afa788d5c82c6e693807eb7a26c5117ed011674bbb49ce5f50e7934b0cf5 1576 postgresql-common_106ubuntu1.dsc
 646d59f60951e0cfd3e1fac2658fd560213b3d16a4cba9fe9728bc7dd7009916 120874 postgresql-common_106ubuntu1.tar.gz
Files: 
 7d88e5ed702235f8387efd3cf993dc59 1576 database optional postgresql-common_106ubuntu1.dsc
 0718110efbdce995ee54cc99d055f35b 120874 database optional postgresql-common_106ubuntu1.tar.gz


More information about the Lucid-changes mailing list