Your message dated Sat, 29 May 1999 15:35:54 -0600 (MDT)
with message-id <[EMAIL PROTECTED]>
and subject line Bug#38530: apt-get update hangs my machine (potato, powerpc)
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'm
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Ian Jackson
(administrator, Debian bugs database)
Received: (at submit) by bugs.debian.org; 29 May 1999 18:55:56 +0000
Received: (qmail 6130 invoked from network); 29 May 1999 18:55:56 -0000
Received: from critters.rs.itd.umich.edu (141.211.83.12)
by master.debian.org with SMTP; 29 May 1999 18:55:56 -0000
Received: from [207.75.178.18] (pm469-08.dialip.mich.net [207.75.178.18])
by critters.rs.itd.umich.edu (8.8.8/2.5) with SMTP id OAA11264
for <[EMAIL PROTECTED]>; Sat, 29 May 1999 14:55:56 -0400 (EDT)
X-Sender: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sat, 29 May 1999 15:01:10 -0400
To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Sean McMillan)
Subject: apt-get update hangs my machine (potato, powerpc)
Package: apt
Version 0.3.6
If I run apt-get update, it will happily go out and download all
the package files, then hang my machine at the "Reading Package Files..."
Line. (I believe that is while it creates the pkgcache.bin files, since
they almost always end up corrupted.) It freezes at any number of different
percentages.
The most frustrating part is that it works about 15% of the time,
so I keep trying. It also seems to work more often if I'm using a source
other than debian's main archive. (I was using the gnome-stage-2 archive
for a while, and that worked if it was the only source I had listed)
When it locks up, I can still switch virtual consoles, and
sometimes I can type into one, but I can never successfully start a new
program (say, for example...kill?) The only way out is to reboot my
machine, and then play with fsck.
