Martin,
thanks for the reply
have made template0 connectable:
srv:/etc/logrotate.d# su - postgres
[EMAIL PROTECTED]:~$ psql template0
Welcome to psql 7.4.7, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slash commands
\g or terminate with semicolon to execute query
\q to quit
template0=# \q
--/snip
now reconfiguring postgresql package
srv:/etc/logrotate.d# dpkg --configure -a
--snip
Setting up postgresql (7.4.7-6sarge1) ...
Applying security update in database gforge...success
Applying security update in database pcic...success
Applying security update in database template1...success
Applying security update in database template0...
--/snip
As you can see the reconfiguration does not fail now, but a "success"
message is not given for template0. Is the security update ok then ?
/Per
2005/9/25, Debian Bug Tracking System <[EMAIL PROTECTED]>:
> This is an automatic notification regarding your Bug report
> #329214: postgresql: Security update on template0 fails,
> which was filed against the postgresql package.
>
> It has been closed by one of the developers, namely
> Martin Pitt <[EMAIL PROTECTED]>.
>
> Their explanation is attached below. If this explanation is
> unsatisfactory and you have not received a better one in a separate
> message then please contact the developer, by replying to this email.
>
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
>
> Received: (at 329214-done) by bugs.debian.org; 25 Sep 2005 15:24:02 +0000
> From [EMAIL PROTECTED] Sun Sep 25 08:24:02 2005
> Return-path: <[EMAIL PROTECTED]>
> Received: from box79162.elkhouse.de [213.9.79.162]
> by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
> id 1EJYMD-0004Ng-00; Sun, 25 Sep 2005 08:24:02 -0700
> Received: from localhost.localdomain (unknown [195.227.105.180])
> (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
> (Client CN "Martin Pitt (workstation)", Issuer "piware CA" (verified
> OK))
> by box79162.elkhouse.de (Postfix) with ESMTP id EBFA61F847D;
> Sun, 25 Sep 2005 17:23:28 +0200 (CEST)
> Received: by localhost.localdomain (Postfix, from userid 1000)
> id 3DE0012F71; Sun, 25 Sep 2005 17:23:39 +0200 (CEST)
> Date: Sun, 25 Sep 2005 17:23:39 +0200
> From: Martin Pitt <[EMAIL PROTECTED]>
> To: Per Jensen <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: Bug#329214: postgresql: Security update on template0 fails
> Message-ID: <[EMAIL PROTECTED]>
> References: <[EMAIL PROTECTED]>
> Mime-Version: 1.0
> Content-Type: multipart/signed; micalg=pgp-sha1;
> protocol="application/pgp-signature"; boundary="jq0ap7NbKX2Kqbes"
> Content-Disposition: inline
> In-Reply-To: <[EMAIL PROTECTED]>
> User-Agent: Mutt/1.5.9i
> 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=-11.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
> HAS_PACKAGE autolearn=ham version=2.60-bugs.debian.org_2005_01_02
>
>
> --jq0ap7NbKX2Kqbes
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> Package: postgresql-common
> Version: 20
>
> Hi Per!
>
> Per Jensen [2005-09-20 16:19 +0200]:
> > Applying security update in database gforge...success
> > Applying security update in database pcic...success
> > Applying security update in database template1...success
> > Applying security update in database template0...
> > dpkg: error processing postgresql (--configure):
> > subprocess post-installation script returned error exit status 2
> > Errors were encountered while processing:
> > postgresql
> >=20
> >=20
> > Is seems the update is being applied to template0. It is not possible=20
> > to connect to template0. That might explain the missing "success" message
> > on template0.
>
> Actually the post installation script makes an effort to temporarily
> enable connection to template0, apply the update, and revert the
> "enable connection" change. This works for the common case.
>
> The packages in sid are more robust against that, will print a better
> error message, and not cause the whole package installation to fail,
> so I'm closing this bug in sid.
>
> Since we can not fix such bugs in stable releases, can you please
> temporarily change your ACLs/configuration to allow template0
> connection to user "postgres" in your setup, reconfigure the
> postgresql package (dpkg --configure -a) and check whether it succeeds
> then?
>
> Thanks,
>
> Martin
>
> --=20
> Martin Pitt http://www.piware.de
> Ubuntu Developer http://www.ubuntu.com
> Debian Developer http://www.debian.org
>
> --jq0ap7NbKX2Kqbes
> Content-Type: application/pgp-signature; name="signature.asc"
> Content-Description: Digital signature
> Content-Disposition: inline
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFDNsD7DecnbV4Fd/IRAqR9AJ4tI6kro8nFAkk2xE257plb7JIJFQCgpGMY
> i6XBQTYRj4XNzrMUidrC7Oo=
> =nUxt
> -----END PGP SIGNATURE-----
>
> --jq0ap7NbKX2Kqbes--
>
--
--
Dårlige volt er noget skidt !
