On Sat, May 12, 2007 at 02:07:40PM +0100, Dave Page <[EMAIL PROTECTED]> was heard to say: > On Fri, May 11, 2007 at 06:14:26PM -0700, Daniel Burrows wrote: > > > Could you send the output of > > > > ps uax | grep apt > > ps uax | grep dpkg > > dhansak:/home/grimoire# ps uax | grep apt > root 5081 0.0 0.2 2864 692 pts/3 R+ 14:02 0:00 grep apt > dhansak:/home/grimoire# ps uax | grep dpkg > root 5083 0.0 0.2 2860 688 pts/3 R+ 14:02 0:00 grep dpkg > > I have since rebooted the system, though I'm fairly sure there weren't > any other apt or dpkg processes running when I had my problem. > > Unfortunately, I needed to install some packages as a matter of some > urgency, so ran "apt-get dist-upgrade" which seems to have fixed the > problem with aptitude. However, it means it may be difficult to track > down this particular bug!
OK, it looks like the problem may be that aptitude complains about not being able to lock a file whenever a fatal error occurs (even a non-lock-related one) before it tries to acquire the lock. I can fix that pretty easily by aborting the install before I try to grab the lock. The underlying issue in your case was that apt error. It's generated in acquire-item.cc and appears to indicate that apt can't find anything to download for the package. The fix is probably to update the package cache, as you discovered. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
