Your message dated Thu, 2 Dec 1999 11:17:49 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#51719: debconf: segfault in postinst (again...)
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.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 25 Nov 1999 19:22:03 +0000
Received: (qmail 5917 invoked from network); 25 Nov 1999 19:22:01 -0000
Received: from wireless-067-123.tele2.co.uk (HELO gate.tao-group.com) ([EMAIL
PROTECTED])
by master.debian.org with SMTP; 25 Nov 1999 19:22:01 -0000
Received: from zircon.tao.co.uk (zircon.tao.co.uk [172.16.100.118])
by gate.tao-group.com (8.9.3/8.9.3) with ESMTP id TAA26695
for <[EMAIL PROTECTED]>; Thu, 25 Nov 1999 19:21:58 GMT
Received: from localhost (zircon.tao.co.uk) [127.0.0.1] (maydell)
by zircon.tao.co.uk with esmtp (Exim 3.03 #1 (Debian))
id 11r4Sr-0003Iu-00; Thu, 25 Nov 1999 19:21:57 +0000
To: [EMAIL PROTECTED]
Subject: debconf: segfault in postinst
Date: Thu, 25 Nov 1999 19:21:52 +0000
From: Peter Maydell <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
Package: debconf
Version: 0.2.44
Severity: grave
When I attempted to install debconf 0.2.44 it failed in the postinst:
Setting up debconf (0.2.44) ...
dpkg: error processing debconf (--configure):
subprocess post-installation script killed by signal (Segmentation fault),
core dumped
Errors were encountered while processing:
debconf
E: Sub-process returned an error code (1)
zircon# file core
core: ELF 32-bit LSB core file of 'http' (signal 11), Intel 80386, version 1
zircon# ls -l core
-rw------- 1 root root 327680 Nov 25 19:00 core
zircon# date
Thu Nov 25 19:05:49 GMT 1999
apt-get/dpkg dumped me back to a prompt, obviously. I then did
dpkg --configur debconf and it worked fine.
I have perl-5.005 version 5.005.03-4.
This system is more-or-less up to date with unstable.
It didn't do this when upgrading my Debian/Sparc box to 0.2.44, unfortunately.
Peter Maydell
---------------------------------------
Received: (at 51280-done) by bugs.debian.org; 2 Dec 1999 19:19:24 +0000
Received: (qmail 17780 invoked from network); 2 Dec 1999 19:19:22 -0000
Received: from unknown (HELO kitenet.net) ([EMAIL PROTECTED])
by master.debian.org with SMTP; 2 Dec 1999 19:19:22 -0000
Received: (qmail 31222 invoked by uid 500); 2 Dec 1999 19:17:49 -0000
Date: Thu, 2 Dec 1999 11:17:49 -0800
From: Joey Hess <[EMAIL PROTECTED]>
To: Peter Maydell <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Bug#51719: debconf: segfault in postinst (again...)
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0i
In-Reply-To: <[EMAIL PROTECTED]>; from [EMAIL PROTECTED] on Thu, Dec 02, 1999
at 01:44:05PM +0000
Peter Maydell wrote:
> I'm rather coming round to the opinion that it is a hardware fault.
> I've just tried continual kernel recompiles. It went OK for 8 runs
> and then gcc got a signal 11 on the 9th...
> Must just have been pure fluke that the two times it fell over were
> during debconf upgrades.
Yeah, looks that way.
> You'd better close this bug (and the other one against apt).
Will do.
--
see shy jo
