Your message dated Mon, 21 Nov 2005 15:02:06 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#340096: fixed in postgresql-common 33
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 20 Nov 2005 22:00:57 +0000
>From [EMAIL PROTECTED] Sun Nov 20 14:00:57 2005
Return-path: <[EMAIL PROTECTED]>
Received: from node1.usercenter.de ([62.112.158.193])
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1EdxF3-00063r-4i
        for [EMAIL PROTECTED]; Sun, 20 Nov 2005 14:00:57 -0800
Received: from Hb (unknown [212.117.84.97])
        (using TLSv1 with cipher AES256-SHA (256/256 bits))
        (No client certificate requested)
        by node1.UserCenter.de (Postfix) with ESMTP id 0CF17344147;
        Sun, 20 Nov 2005 23:00:25 +0100 (CET)
Received: from coricelesti ([192.168.42.23] helo=localhost.localdomain)
        by Hb with esmtp (Exim 4.50)
        id 1EdxBz-0004Zy-5M; Sun, 20 Nov 2005 22:57:47 +0100
Received: from gunter by localhost.localdomain with local (Exim 4.54)
        id 1EdxBy-0003yo-0F; Sun, 20 Nov 2005 22:57:46 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Gunter Ohrner <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: typo: recommends to drop V8.0 cluster before upgrading to 8.1...
Reply-To: [EMAIL PROTECTED]
X-Mailer: reportbug 3.17
Date: Sun, 20 Nov 2005 22:57:45 +0100
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: postgresql-common
Version: 32
Severity: normal

At least using the German localisation postgresql-common recommends to

  pg_dropcluster --stop-server 8.0 main

before running pg_upgradecluster - in which case there won't be much to
upgrade if I'm not mistaken... ;) Let#s just hope noone is
copy-n-pasting this recommendation into his system console...

Greetings,

  Gunter

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.3.cc.20051007.1-skas3-v8.2
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages postgresql-common depends on:
ii  adduser                       3.79       Add and remove users and groups
ii  debconf [debconf-2.0]         1.4.59     Debian configuration management sy

Versions of packages postgresql-common recommends:
ii  openssl                       0.9.8a-4   Secure Socket Layer (SSL) binary a

-- debconf information:
* postgresql-common/obsolete-major:

---------------------------------------
Received: (at 340096-close) by bugs.debian.org; 21 Nov 2005 23:11:24 +0000
>From [EMAIL PROTECTED] Mon Nov 21 15:11:24 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
        id 1EeKfm-0007w5-8U; Mon, 21 Nov 2005 15:02:06 -0800
From: Martin Pitt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#340096: fixed in postgresql-common 33
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Mon, 21 Nov 2005 15:02:06 -0800
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 3

Source: postgresql-common
Source-Version: 33

We believe that the bug you reported is fixed in the latest version of
postgresql-common, which is due to be installed in the Debian FTP archive:

postgresql-common_33.dsc
  to pool/main/p/postgresql-common/postgresql-common_33.dsc
postgresql-common_33.tar.gz
  to pool/main/p/postgresql-common/postgresql-common_33.tar.gz
postgresql-common_33_all.deb
  to pool/main/p/postgresql-common/postgresql-common_33_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Pitt <[EMAIL PROTECTED]> (supplier of updated postgresql-common package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 21 Nov 2005 23:30:34 +0100
Source: postgresql-common
Binary: postgresql-common
Architecture: source all
Version: 33
Distribution: unstable
Urgency: low
Maintainer: Martin Pitt <[EMAIL PROTECTED]>
Changed-By: Martin Pitt <[EMAIL PROTECTED]>
Description: 
 postgresql-common - manager for PostgreSQL database clusters
Closes: 338025 340096 340187
Changes: 
 postgresql-common (33) unstable; urgency=low
 .
   * pg_wrapper: Instead of checking $0 against a static list, just check
     whether the program is available in postgresql's bin dir. This allows
     other packages which provide stuff in pg_bin to install additional
     symlinks and get pg_wrapper support for free.
   * pg_checksystem, pg_createcluster, pg_dropcluster, pg_upgradecluster: Check
     that effective user is root before doing anything to avoid confusing error
     messages.
   * pg_ctlcluster: Enhance the check if cluster is up and running to make it
     more reliable. This should fix the 'Database system is starting up' errors
     on autovacuum startup.
   * debian/init.d-functions: Remove legacy init script output and always use
     LSB functions. Add lsb-base dependency.
   * debian/po/de.po: Fix cluster version in German translation.
     Closes: #340096
   * debian/postgresql-common.postrm: Check if /etc/postgresql-common exists
     before trying to remove it. Closes: #340187
   * pg_upgradecluster:
     - Fix error message for nonexisting cluster.
     - Use pg_dump/pg_restore with custom format to support BLOBs.
     - Upgrade databases with disabled connection.
     - Execute ANALYZE after upgrade instead of pg_maintenance.
     - Set correct autovacuum option in postgresql.conf when
       upgrading to 8.1, depending on whether autovacuuming was used for the
       old cluster.
     - Restrict access to the clusters to the cluster owner and to the local
       Unix socket during upgrade. Closes: #338025
     - Convert to 'strict' Perl mode.
Files: 
 531fc4b919d0da764955c2a46c431bd6 578 misc optional postgresql-common_33.dsc
 2fe3ee91c0321612af778a56d45b991a 56421 misc optional 
postgresql-common_33.tar.gz
 6351cc739de210eaadcc0a406bcd006c 78366 misc optional 
postgresql-common_33_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDglCDDecnbV4Fd/IRAqcHAKDCOGPdYw9hEiM2HL4Pjd6tGPdObACfTrG4
eOl1V7WhzvQ+BhKtpgYmEZs=
=ZtBA
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to