Your message dated Fri, 25 Nov 2005 19:14:03 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#340744: postgresql-common: 'Unknown Debian release: 3.1'
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; 25 Nov 2005 15:01:38 +0000
>From [EMAIL PROTECTED] Fri Nov 25 07:01:38 2005
Return-path: <[EMAIL PROTECTED]>
Received: from vsmtp14.tin.it ([212.216.176.118])
by spohr.debian.org with esmtp (Exim 4.50)
id 1Eff26-0002jl-1v
for [EMAIL PROTECTED]; Fri, 25 Nov 2005 06:58:38 -0800
Received: from casa (87.0.224.10) by vsmtp14.tin.it (7.2.060.1) (authenticated
as [EMAIL PROTECTED])
id 4379C5D500456D94; Fri, 25 Nov 2005 15:58:08 +0100
Received: from giuseppe by casa with local (Exim 4.50)
id 1Eff12-0003Fr-4g; Fri, 25 Nov 2005 15:57:32 +0100
Date: Fri, 25 Nov 2005 15:57:32 +0100
From: Giuseppe Sacco <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: postgresql-common: 'Unknown Debian release: 3.1'
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
Content-Transfer-Encoding: Quoted-Printable
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=-7.5 required=4.0 tests=BAYES_00,HAS_PACKAGE,
RCVD_IN_SORBS autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: postgresql-common
Version: 34
Severity: important
I am updating my debian unstable and found that postgresql-common
cannot configure since postinst fails. I debugged the problem and it
seems that /usr/share/postgresql-common/supported-versions
does not recognize any debian release different than 'testing/unstable'
while =ABlsb_release -rs=BB give '3.1' on my system.
I added 'set -x' at the start of supported-versions, so now I have this
output:
----------------------------------------------------------
eppesuig3:~# dpkg --configure postgresql-common
Configuro postgresql-common (34) ...
+ type -p lsb_release
++ lsb_release -is
+ DISTRO=3DDebian
++ lsb_release -rs
+ RELEASE=3D3.1
+ case "$DISTRO" in
+ lsb_debian 3.1
+ case "$1" in
+ echo 'Unknown Debian release: 3.1'
+ exit 1
dpkg: errore processando postgresql-common (--configure):
il sottoprocesso post-installation script ha restituito un codice di err=
ore 1
Sono occorsi degli errori processando:
postgresql-common
eppesuig3:~# lsb_release -is
Debian
eppesuig3:~# lsb_release -rs
3.1
eppesuig3:~#=20
----------------------------------------------------------
please note that /etc/debian_version contains 'testing/unstable'
Bye,
Giuseppe
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-1-powerpc
Locale: LANG=3Dit_IT.UTF-8, LC_CTYPE=3Dit_IT.UTF-8 (charmap=3DISO-8859-1)=
(ignored: LC_ALL set to it_IT)
Versions of packages postgresql-common depends on:
ii adduser 3.79 Add and remove users and gro=
ups
ii debconf [debconf-2.0] 1.4.59 Debian configuration managem=
ent sy
ii lsb-base 3.0-11 Linux Standard Base 3.0 init=
scrip
Versions of packages postgresql-common recommends:
ii openssl 0.9.8a-4 Secure Socket Layer (SSL) bi=
nary a
-- debconf information:
* postgresql-common/obsolete-major:
--=20
() ascii ribbon campaign - against html mail
/\ - against ms attachments
Giuseppe Sacco, Unix/Linux/Baan/PostgreSQL/Oracle administrator
GPG Fingerprint: 43AA F8E2 7A0E 57F4 DC7F FD02 2207 C594 EC97 089D
---------------------------------------
Received: (at 340744-done) by bugs.debian.org; 25 Nov 2005 18:14:36 +0000
>From [EMAIL PROTECTED] Fri Nov 25 10:14:36 2005
Return-path: <[EMAIL PROTECTED]>
Received: from box79162.elkhouse.de ([213.9.79.162])
by spohr.debian.org with esmtp (Exim 4.50)
id 1Efi5j-0000JM-Oz
for [EMAIL PROTECTED]; Fri, 25 Nov 2005 10:14:36 -0800
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 D8E67C043C
for <[EMAIL PROTECTED]>; Fri, 25 Nov 2005 19:14:02 +0100 (CET)
Received: by localhost.localdomain (Postfix, from userid 1000)
id 748C64AD3; Fri, 25 Nov 2005 19:14:03 +0100 (CET)
Date: Fri, 25 Nov 2005 19:14:03 +0100
From: Martin Pitt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#340744: postgresql-common: 'Unknown Debian release: 3.1'
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.11
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=-2.4 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_SBLXBL,RCVD_IN_SBLXBL_CBL,
RCVD_IN_SORBS,RCVD_IN_SORBS_WEB autolearn=no
version=2.60-bugs.debian.org_2005_01_02
--jI8keyz6grp/JLjh
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Version: 35
Hi Giuseppe!
Giuseppe Sacco [2005-11-25 15:57 +0100]:
> I am updating my debian unstable and found that postgresql-common
> cannot configure since postinst fails. I debugged the problem and it
> seems that /usr/share/postgresql-common/supported-versions
> does not recognize any debian release different than 'testing/unstable'
> while =ABlsb_release -rs=BB give '3.1' on my system.
This was already fixed in version 35 which was uploaded yesterday:
postgresql-common (35) unstable; urgency=3Dlow
* pg_ctlcluster: If the socket already responds, but connections fail
several times in a row, give the postmaster some more time (5s) to
actually accept connections.
* t/060_obsolete_confparams.t: Start with a full configuration file for
every tested version, instead of just upgrading the previously upgraded
version. This gives an exhaustive check for obsolete parameters.
* pg_upgradecluster: Handle all outstanding obsolete parameters when
upgrading to 8.1:
- bgwriter_percent -> bgwriter_{lru,all}_percent
- bgwriter_maxpages -> bgwriter_{lru,all}_maxpages
* PgCommon.pm: Add new function set_cluster_start_conf() for easier change
of start.conf.
* Rename test 030_create_errors.t to 030_errors.t since it covers more
errors than just creation failures.
* Add test t/080_start.conf.t: Check start.conf handling and upgrading.
* debian/supported-versions: Add Debian release 3.1.
Closes: #340397, #340483
* debian/postgresql-common.config: Ignore things in /usr/lib/postgresql t=
hat
are not a version-specific postgresql subdirectory. Closes: #340470
* t/001_packages.t: Check that procps is installed, the selftests need it.
Thanks,
Martin
--=20
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org
In a world without walls and fences, who needs Windows and Gates?
--jI8keyz6grp/JLjh
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDh1RrDecnbV4Fd/IRAl8NAKCseR3qUuPXWSWouRtkHINM9izaPACg789y
mvrN/B1HljxOBLAaJAAfa0c=
=sgYR
-----END PGP SIGNATURE-----
--jI8keyz6grp/JLjh--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
