Your message dated Tue, 22 Feb 2005 16:09:19 +0100 (CET)
with message-id <[EMAIL PROTECTED]>
and subject line pgsql was not running
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; 11 Feb 2005 22:42:22 +0000
>From [EMAIL PROTECTED] Fri Feb 11 14:42:22 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail21.bluewin.ch [195.186.18.66]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CzjUU-0007PF-00; Fri, 11 Feb 2005 14:42:22 -0800
Received: from localhost (81.62.228.15) by mail21.bluewin.ch (Bluewin AG
7.0.035)
id 4202A910000FA1BF; Fri, 11 Feb 2005 22:41:51 +0000
Received: from tpo by localhost with local (Exim 3.36 #1 (Debian))
id 1CzjTz-0005QW-00; Fri, 11 Feb 2005 23:41:51 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Tomas Pospisek <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: fails to upgrade
X-Mailer: reportbug 3.2
Date: Fri, 11 Feb 2005 23:41:51 +0100
Message-Id: <[EMAIL PROTECTED]>
Sender: Tomas Pospisek <[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-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
RCVD_IN_BL_SPAMCOP_NET autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: gforge-db-postgresql
Version: 3.1-26
Severity: important
While upgrading from gforge 3rc2-1 I got the following error (might be that
you'll
consider this bugreport as irrelevant and close it since gforge was not in
woody -
that's fine me)
Setting up gforge-db-postgresql (3.1-26) ...
Installing new version of config file /etc/cron.d/gforge-db-postgresql ...
Configuring for PostgreSQL 7.3 or later
Replacing file /etc/postgresql/pg_hba.conf with changed version
You'll see some debugging info during this installation.
Do not worry unless told otherwise.
DBI connect('dbname=gforge;host=127.0.0.1','gforge',...) failed: FATAL: IDENT
authentication failed for user "gforge" at /usr/lib/gforge/lib/include.pl line
45
Uncaught exception from user code:
Cannot connect to database: at /usr/lib/gforge/lib/include.pl line 47.
main::db_connect called at /usr/lib/gforge/bin/db-upgrade.pl line 36
dpkg: error processing gforge-db-postgresql (--configure):
subprocess post-installation script returned error exit status 255
I'm too tired to think so I'll not debug this at this time (it's only a backup
server update).
*t
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.22
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages gforge-db-postgresql depends on:
ii debconf 1.4.30.11 Debian configuration management sy
hi debianutils 2.8.4 Miscellaneous utilities specific t
pn gforge-common Not found.
pn libdbd-pg-perl Not found.
hi libdbi-perl 1.46-6 Perl5 database interface by Tim Bu
hi libhtml-parser-perl 3.45-1 A collection of modules that parse
ii perl [libmime-base64-perl] 5.8.4-6 Larry Wall's Practical Extraction
pn php4-cgi Not found.
pn php4-pgsql Not found.
ii postgresql 7.4.7-1 object-relational SQL database man
---------------------------------------
Received: (at 294862-close) by bugs.debian.org; 22 Feb 2005 15:09:52 +0000
>From [EMAIL PROTECTED] Tue Feb 22 07:09:51 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail4.bluewin.ch [195.186.4.74]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D3bfb-0000XA-00; Tue, 22 Feb 2005 07:09:51 -0800
Received: from localhost (83.77.74.36) by mail4.bluewin.ch (Bluewin AG 7.0.035)
id 41E5802C003DFAE8 for [EMAIL PROTECTED]; Tue, 22 Feb 2005 15:09:20
+0000
Received: from tpo (helo=localhost)
by localhost with local-esmtp (Exim 3.36 #1 (Debian))
id 1D3bf5-0005ek-00
for <[EMAIL PROTECTED]>; Tue, 22 Feb 2005 16:09:19 +0100
Date: Tue, 22 Feb 2005 16:09:19 +0100 (CET)
From: Tomas Pospisek <[EMAIL PROTECTED]>
X-X-Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: pgsql was not running
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Due to unrelated circumstances the postgres DB was not running, which
delivered a major headache to the gforge upgrade procedure.
It was not the fault of gforge-db-postgresql that the DB was not up
therefore I'm closing the report.
Thanks a lot,
*t
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
