Package: fakeroot
Version: 1.1.5, 1.5.10
Severity: Normal
NB: I am running gentoo, not debian. However this problem sounded
related so I thought I would post it here. I am having exact opposite
problem, where a symbolic link intermittenly will appear to be a regular
file within the fakeroot environment. Outside of that particular
fakeroot session, the file exists as it should. From within, I can
access it, but stats always seem to return that it is a file.
$ fakeroot -i fakeroot.env ls -al
/tmp/build-image-21517/dropbear-0.48.1/dropbear
-rwxr-xr-x 1 root root 13 Jun 8 08:23
/tmp/build-image-21517/dropbear-0.48.1/dropbear
$ fakeroot -i fakeroot.env cat
/tmp/build-image-21517/dropbear-0.48.1/dropbear | wc
8302 32783 856231
$ fakeroot -i fakeroot.env stat
/tmp/build-image-21517/dropbear-0.48.1/dropbear
File: `/tmp/build-image-21517/dropbear-0.48.1/dropbear'
Size: 13 Blocks: 0 IO Block: 4096 regular file
Device: 902h/2306d Inode: 1753595 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2007-06-08 08:23:05.000000000 -0500
Modify: 2007-06-08 08:23:05.000000000 -0500
Change: 2007-06-08 08:23:05.000000000 -0500
$ stat /tmp/build-image-21517/dropbear-0.48.1/dropbear
File: `/tmp/build-image-21517/dropbear-0.48.1/dropbear' ->
`dropbearmulti'
Size: 13 Blocks: 0 IO Block: 4096 symbolic
link
Device: 902h/2306d Inode: 1753595 Links: 1
Access: (0777/lrwxrwxrwx) Uid: ( 1027/mbenedict) Gid: ( 30/
sce)
Access: 2007-06-08 08:23:05.000000000 -0500
Modify: 2007-06-08 08:23:05.000000000 -0500
Change: 2007-06-08 08:23:05.000000000 -0500
$ fakeroot stat /tmp/build-image-21517/dropbear-0.48.1/dropbear
File: `/tmp/build-image-21517/dropbear-0.48.1/dropbear' ->
`dropbearmulti'
Size: 13 Blocks: 0 IO Block: 4096 symbolic
link
Device: 902h/2306d Inode: 1753595 Links: 1
Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2007-06-08 08:23:05.000000000 -0500
Modify: 2007-06-08 08:23:05.000000000 -0500
Change: 2007-06-08 08:23:05.000000000 -0500
An upgrade from 1.1.5 to 1.5.10 did not help. Like the original bug,
this is intermitten. I would say the bug happens 80% of the time. I
tried but failed to create a simply test case that would reproduce.
Same type of environment, though... A build script run under fakeroot
that makes a bunch of packages. Let me know if I can provide any
additional information that might help isolate the problem.
Regards,
Michael
