Your message dated Tue, 16 Jan 2001 14:42:19 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed
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; 23 Nov 2000 22:30:43 +0000
>From [EMAIL PROTECTED] Thu Nov 23 16:30:43 2000
Return-path: <[EMAIL PROTECTED]>
Received: from (c3po.terralink.de) [194.97.37.23] (qmailr)
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 13z4t8-00029F-00; Thu, 23 Nov 2000 16:30:42 -0600
Received: (qmail 27138 invoked from network); 23 Nov 2000 22:30:40 -0000
Received: from 213?21?44?193.surf-callino.de (HELO localhost) ([EMAIL PROTECTED])
by c3po.t-link.de with SMTP; 23 Nov 2000 22:30:40 -0000
Received: from marcus by localhost with local (Exim 3.16 #1 (Debian))
id 13z4ul-00005m-00; Thu, 23 Nov 2000 23:32:23 +0100
From: [EMAIL PROTECTED]
Subject: hurd: write_node assertion failed building emacs
To: [EMAIL PROTECTED]
X-Mailer: bug 3.2.9
Message-Id: <E13z4ul-00005m-00@localhost>
Date: Thu, 23 Nov 2000 23:32:23 +0100
Organization: Marcus Brinkmann's Home
Delivered-To: [EMAIL PROTECTED]
Package: hurd
Version: N/A
Severity: normal
Hi,
building the Debian emacs20 package triggers an assertion failure in
ext2fs/inode.c (write_node):
assert (!np->dn_set_ctime && !np->dn_set_atime && !np->dn_set_mtime);
This happens when temacs dumps the emacs binary. It does only happen with a
full build. If one reboots, the build continues fine. The resulting emacs
binary segfaults, though. That is another bug, most likely.
I have not yet produced more info. It is clear to me that we must identify
the caller of write_node to be able to track this down further.
Thanks,
Marcus
-- System Information
Debian Release: 2.2
Kernel Version: Linux ulysses 2.4.0-test9 #1 Mon Okt 30 20:36:05 CET 2000 i686 unknown
---------------------------------------
Received: (at 77857-done) by bugs.debian.org; 16 Jan 2001 13:42:22 +0000
>From [EMAIL PROTECTED] Tue Jan 16 07:42:22 2001
Return-path: <[EMAIL PROTECTED]>
Received: from sunu422.rz.ruhr-uni-bochum.de [134.147.64.14]
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 14IWNR-0008Sc-00; Tue, 16 Jan 2001 07:42:21 -0600
Received: (qmail 29698 invoked from network); 16 Jan 2001 13:42:19 -0000
Received: from unknown (HELO ulysses.alg.ruhr-uni-bochum.de) ([EMAIL PROTECTED])
by mailhost.rz.ruhr-uni-bochum.de with SMTP; 16 Jan 2001 13:42:19 -0000
Received: from marcus by ulysses.alg.ruhr-uni-bochum.de with local (Exim 3.20 #1
(Debian))
id 14IWNP-00009M-00
for <[EMAIL PROTECTED]>; Tue, 16 Jan 2001 14:42:19 +0100
Date: Tue, 16 Jan 2001 14:42:19 +0100
From: Marcus Brinkmann <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: fixed
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: Marcus Brinkmann <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
This bug is fixed by now.
Marcus
_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
