Hi, can it be, that this issue is a WONTFIX because it is a conceptual problem of fakechroot that absolute symbolic links within the fakechroot have to carry the full path to the fakechroot with them?
open(2) will automatically resolve symoblic links. it will resolve them wrongly if they are absolute links and do not have the path to the fakechroot prepended. Of course fakechroot could resolve the symoblic link for open(2) and then let it open the resolved version but this would break functionality of programs that rely upon from which symlink they were called. I was under the impression that I could just chroot(1) into a fakechroot environment and use it just as with fakechroot. Could it be that this is not the case (due to the absolute symbolic link issue) and I always have to fakechroot(1) into the directory? So is this actually indeed a conceptual problem? If so, it would be good to mention this in the man page or readme? cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
