On Wed, 2004-05-12 at 14:08 -0500, Bob Pendleton wrote: > On Wed, 2004-05-12 at 12:07, Scott James Remnant wrote: > > On Tue, 2004-05-11 at 23:03 -0700, Debian Bug Tracking System wrote: > > > > > > reassign 247234 dpkg > > > Bug#247234: g++-3.3: package is broken > > > Bug reassigned from package `g++-3.3' to `dpkg'. > > > > > Strange, normally I'd only expect to see EBUSY the item involved in the > > rename() was a directory... > > > > Can you do these on your system for me: > > > > $ ls -l /usr/lib/gcc-lib/i486-linux/3.3.3/specs > > $ dpkg-deb -c /var/cache/apt/archives/gcc-3.3_1%3a3.3.3-7_i386.deb | > > grep specs > > Here you go: > > voyager:~# ls -l /usr/lib/gcc-lib/i486-linux/3.3.3/specs > -rw-r--r-- 1 root root 3927 2004-04-30 06:55 /usr/lib/gcc-lib/i486-linux/3.3.3/specs > voyager:~# dpkg-deb -c /var/cache/apt/archives/gcc-3.3_1%3a3.3.3-7_i386.deb | grep specs > -rw-r--r-- root/root 3927 2004-04-30 06:55:18 ./usr/lib/gcc-lib/i486-linux/3.3.3/specs > voyager:~# > Ok... What filesystem is that? Does it work if gcc isn't running? Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
Description: This is a digitally signed message part