tag 247234 unreproducible thanks Hi!
On Thu, 2004-06-03 at 14:32:06 -0300, Scott James Remnant wrote: > On Wed, 2004-05-12 at 14:08 -0500, Bob Pendleton wrote: > > On Wed, 2004-05-12 at 12:07, Scott James Remnant wrote: > > > 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? Bob, if you still remember that'd be useful, also if you have found this problem afterwards? Marked this bug unreproducible, and I guess that if we don't get additional data we should probably close it after some time. regards, guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
