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

Bug#203483: marked as done (apt: chokes on a good /var/lib/dpkg/status)



Your message dated Wed, 30 Jul 2003 15:31:51 -0400
with message-id <20030730193151.GJ21966@alcor.net>
and subject line Bug#203483: apt: chokes on a good /var/lib/dpkg/status
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; 30 Jul 2003 12:12:27 +0000
>From lizzy@soggytrousers.net Wed Jul 30 07:12:25 2003
Return-path: <lizzy@soggytrousers.net>
Received: from remt27.cluster1.charter.net [209.225.8.37] 
	by master.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 19hpof-0007Sg-00; Wed, 30 Jul 2003 07:12:25 -0500
Received: from [66.190.65.189] (HELO liliwhite.renaissance.oasis)
  by remt27.cluster1.charter.net (CommuniGate Pro SMTP 4.0.6)
  with ESMTP id 105702702 for submit@bugs.debian.org; Wed, 30 Jul 2003 07:42:24 -0400
Received: from lizzy by liliwhite.renaissance.oasis with local (Exim 3.35 #1 (Debian))
	id 19hpLW-0002oH-00
	for <submit@bugs.debian.org>; Wed, 30 Jul 2003 06:42:18 -0500
To: submit@bugs.debian.org
Subject: apt: chokes on a good /var/lib/dpkg/status
From: Elizabeth Barham <lizzy@soggytrousers.net>
Date: 30 Jul 2003 06:42:16 -0500
Message-ID: <[🔎] 87fzkos0kn.fsf@liliwhite.renaissance.oasis>
Lines: 55
X-Mailer: Gnus v5.7/Emacs 20.7
Sender: Elizabeth Barham <lizzy@soggytrousers.net>
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0
	tests=BAYES_20,HAS_PACKAGE,USER_AGENT_GNUS_XM
	version=2.53-bugs.debian.org_2003_07_20
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_07_20 (1.174.2.15-2003-03-30-exp)

Package: apt
Version: 0.5.4
Severity: grave
Justification: renders package unusable
Tags: patch

Hi,

apt-get continued to error out stating it could not parse
/var/lib/dpkg/status:

     Unable to parse package file /var/lib/dpkg/status (1)

but I went over /var/lib/dpkg/status and could not find anything
amiss. So I checked the source code and noticed that at the
end of the file, the buffer was reset and had zero data in it
which caused Tag.Scan() to return false. (See tagfile.cc:70).
But this is an error because the code should have already
determined it was at the end of the file and *not* call
Tag.Scan() a second time.

*** tagfile.cc~	Mon May 14 00:56:26 2001
--- tagfile.cc	Wed Jul 30 05:36:05 2003
*************** bool pkgTagFile::Fill()
*** 112,119 ****
     unsigned long Actual;
     if (Fd.Read(End,Size - (End - Buffer),&Actual) == false)
        return false;
!    if (Actual != Size - (End - Buffer))
        Done = true;
     End += Actual;
  /*   
     if (Left < Size - (End - Buffer))
--- 112,121 ----
     unsigned long Actual;
     if (Fd.Read(End,Size - (End - Buffer),&Actual) == false)
        return false;
!    if (Actual != Size - (End - Buffer)) {
        Done = true;
+       return false;
+    }
     End += Actual;
  /*   
     if (Left < Size - (End - Buffer))


-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux miller 2.2.20-idepci #1 Sat Apr 20 12:45:19 EST 2002 i486
Locale: LANG=C, LC_CTYPE=C

Versions of packages apt depends on:
ii  libc6                  2.2.5-11.5        GNU C Library: Shared libraries an
ii  libstdc++2.10-glibc2.2 1:2.95.4-11woody1 The GNU stdc++ library

---------------------------------------
Received: (at 203483-done) by bugs.debian.org; 30 Jul 2003 19:31:57 +0000
>From mdz@csh.rit.edu Wed Jul 30 14:31:55 2003
Return-path: <mdz@csh.rit.edu>
Received: from smtp02.mrf.mail.rcn.net [207.172.4.61] 
	by master.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 19hwfw-0006C8-00; Wed, 30 Jul 2003 14:31:52 -0500
Received: from 216-15-124-77.c3-0.smr-ubr3.sbo-smr.ma.cable.rcn.com ([216.15.124.77] helo=mizar.alcor.net)
	by smtp02.mrf.mail.rcn.net with esmtp (Exim 3.35 #4)
	id 19hwfw-00071s-00; Wed, 30 Jul 2003 15:31:52 -0400
Received: from mdz by mizar.alcor.net with local (Exim 3.36 #1 (Debian))
	id 19hwfv-0006iE-00; Wed, 30 Jul 2003 15:31:51 -0400
Date: Wed, 30 Jul 2003 15:31:51 -0400
From: Matt Zimmerman <mdz@debian.org>
To: Elizabeth Barham <lizzy@soggytrousers.net>, 203483-done@bugs.debian.org
Subject: Re: Bug#203483: apt: chokes on a good /var/lib/dpkg/status
Message-ID: <20030730193151.GJ21966@alcor.net>
References: <[🔎] 87fzkos0kn.fsf@liliwhite.renaissance.oasis>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[🔎] 87fzkos0kn.fsf@liliwhite.renaissance.oasis>
User-Agent: Mutt/1.5.4i
Sender: Matt Zimmerman <mdz@alcor.net>
Delivered-To: 203483-done@bugs.debian.org
X-Spam-Status: No, hits=-15.5 required=4.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_MUTT
	version=2.53-bugs.debian.org_2003_07_20
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_07_20 (1.174.2.15-2003-03-30-exp)

severity 203483 normal
# unfortunately, #139328 is archived...
merge 203483 139328
thanks

On Wed, Jul 30, 2003 at 06:42:16AM -0500, Elizabeth Barham wrote:

> apt-get continued to error out stating it could not parse
> /var/lib/dpkg/status:
> 
>      Unable to parse package file /var/lib/dpkg/status (1)
> 
> but I went over /var/lib/dpkg/status and could not find anything
> amiss. So I checked the source code and noticed that at the
> end of the file, the buffer was reset and had zero data in it
> which caused Tag.Scan() to return false. (See tagfile.cc:70).
> But this is an error because the code should have already
> determined it was at the end of the file and *not* call
> Tag.Scan() a second time.

This is a duplicate of bug #139328, which was fixed in apt 0.5.5.  In the
unlikely event that you can still reproduce this bug with the most recent
version, please reopen this bug.

-- 
 - mdz



Reply to: