On 2009-08-12 10:35 +0200, Patrick Schoenfeld wrote: > Package: dpkg > Version: 1.15.3.1 > Severity: serious > > Hi, > > today I noticed something that I consider really serious: > I've started an aptitude purge gimp, without noticing that I had > an aptitude dist-upgrade (waiting for input, because of apt-listchanges) > running in another terminal, which I forgot to finish the day before. > Now would I have expected would be to stop and warn me about > the locked dpkg database.
If it did not do that, then the database was almost surely not locked in the first place. Here is what I got after starting aptitude's TUI as root: ,---- | % LANG=C sudo dpkg -P ed | dpkg: status database area is locked by another process `---- Sven -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
