[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#47323: marked as done (dpkg occationally destroys <package>.list)



Your message dated Fri, 22 Oct 1999 13:43:49 -0400
with message-id <19991022134349.D550@lappy.djj.state.va.us>
and subject line no more info, not reproducible
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; 13 Oct 1999 12:31:21 +0000
Received: (qmail 6364 invoked from network); 13 Oct 1999 12:31:19 -0000
Received: from hermine.idb.hist.no (root@158.38.50.15)
  by master.debian.org with SMTP; 13 Oct 1999 12:31:19 -0000
Received: from idb.hist.no (helgehaf@hh.idb.hist.no [158.38.51.89])
	by hermine.idb.hist.no (8.8.7/8.8.7) with ESMTP id OAA32410
	for <submit@bugs.debian.org>; Wed, 13 Oct 1999 14:30:51 +0200
Sender: Helge.Hafting@idb.hist.no
Message-ID: <38047BBE.23D027AA@idb.hist.no>
Date: Wed, 13 Oct 1999 14:31:58 +0200
From: Helge Hafting <helge.hafting@idb.hist.no>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.20 i686)
X-Accept-Language: no, en
MIME-Version: 1.0
To: submit@bugs.debian.org
Subject: dpkg occationally destroys <package>.list
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Package: dpkg
Version:1.4.1.13_i386

When I install/upgrade packages I now and then
get an error message about how the
<package>.list file for some package contains an empty filename.
As far as I remember, this <package> is usually one that
the package being installed depends on in some way.

dpkg quits after this, and apt-get/dselect gives up also.

When I look at /var/lib/dpkg/info/<package>.list I see
that the usual list of plaintext filenames isn't there, the
content is binary.  I don't know why this happens, but it is
annoying.  It is always only one ruined package, this makes me believe
dpkg does the trashing shortly before the error message.

I have seen this for a long time, (since slink) but I thought it was a
bad disk.
But now I see this on two newer machines also.

I rebuild the <package>.list file by running dpkg --contents against
the package.deb file.  Then I trim off unnecessary stuff from the file
list.
This gets boring after a while.  It happens only occationally, perhaps
once per 50 packages installed. 

A wild guess:
I dpkg using mmap for looking at file lists?  If it does, and it is
a writeable mapping, then a random pointer error could do something
like this.

Kernel versions: 2.3.6 - 2.3.20
C library: libc-2.1.2.so
Hardware doesn't matter, this happens with scsi drives, ide drives,
single and multiple processors.

Helge Hafting
---------------------------------------
Received: (at 47323-done) by bugs.debian.org; 22 Oct 1999 17:40:15 +0000
Received: (qmail 8320 invoked from network); 22 Oct 1999 17:40:15 -0000
Received: from djj.state.va.us (HELO lappy.djj.state.va.us) (209.96.130.218)
  by master.debian.org with SMTP; 22 Oct 1999 17:40:15 -0000
Received: from bmc by lappy.djj.state.va.us with local (Exim 3.03 #1 (Debian))
	for 47323-done@bugs.debian.org
	id 11eijF-0002t1-00; Fri, 22 Oct 1999 13:43:49 -0400
Date: Fri, 22 Oct 1999 13:43:49 -0400
From: Ben Collins <bcollins@debian.org>
To: 47323-done@bugs.debian.org
Subject: no more info, not reproducible
Message-ID: <19991022134349.D550@lappy.djj.state.va.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0pre4i

Since no one seems to be able to confirm this, and the submitter does not
respond to requests for updates, I am writing this off as a kernel issue
(the submitter was using an early 2.3.x kernel) and closing the report. If
some one can confirm the bug, or the submitter replies with more info,
then I will reopen it.

Ben


Reply to: