Thanks for the reply. You're correct---that command gives root root 0 /usr/bin/dpkg
I ran the dpkg-statoverride command and I couldn't reproduce the behaviour, so it seems the issue is resolved. Is this a problem peculiar to my system, or have I found a real live bug? :-) Thanks for your help. 2009/12/28 Sven Joachim <svenj...@gmx.de>: > On 2009-12-28 07:48 +0100, Cameron Horsburgh wrote: > >> came...@jupiter:~/Downloads$ ls -l /usr/bin/dpkg >> -rwxr-xr-x 1 root root 371824 Dec 23 03:26 /usr/bin/dpkg >> came...@jupiter:~/Downloads$ sudo dpkg -i dpkg_1.15.5.5_i386.deb >> [sudo] password for cameron: >> (Reading database ... 290683 files and directories currently installed.) >> Preparing to replace dpkg 1.15.5.5 (using dpkg_1.15.5.5_i386.deb) ... >> Unpacking replacement dpkg ... >> Setting up dpkg (1.15.5.5) ... >> Processing triggers for man-db ... >> came...@jupiter:~/Downloads$ which dpkg >> came...@jupiter:~/Downloads$ ls -l /usr/bin/dpkg >> ---------- 1 root root 371824 Dec 23 03:26 /usr/bin/dpkg > > The reason is almost certainly a bad statoverride for /usr/bin/dpkg. > What does "dpkg-statoverride --list /usr/bin/dpkg" print? I bet it's > something like > > root root 000 /usr/bin/dpkg > > and you can fix that with "dpkg-statoverride --remove /usr/bin/dpkg". > > Sven > -- Cameron Horsburgh blog: http://spiritcry.wordpress.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
