Bug#555499: Residual lock file after running aptitude

2009-11-11 Thread Jason White
Daniel Burrows wrote: > /var/lib/apt/lists/lock is an fcntl lockfile, not a dotlock-style > lockfile. i.e., its mere existence isn't enough for the lock to be > held; a currently running process has to be holding the lock. Removing > the lockfile doesn't remove the lock; instead, it causes a

Bug#555499: Residual lock file after running aptitude

2009-11-10 Thread Daniel Burrows
On Tue, Nov 10, 2009 at 12:10:26PM +1100, Jason White was heard to say: > ja...@jdc:~$ sudo aptitude update && sudo aptitude dist-upgrade > E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily > u > navailable) > E: Couldn't lock list directory..are you root? > ja...@jdc

Bug#555499: Residual lock file after running aptitude

2009-11-09 Thread Jason White
Package: aptitude Version: 0.6.0.1-1 Severity: normal ja...@jdc:~$ sudo aptitude update && sudo aptitude dist-upgrade E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily u navailable) E: Couldn't lock list directory..are you root? ja...@jdc:~$ but if I then run sudo rm