Bug#548691: getcwd fails to return proper path for relatively-specified roots

2010-03-30 Thread Robie Basak
tags 548691 patch thanks I've just come across this. The problem is that the narrow_chroot_path macro that applies the chroot to a particular path uses a substring match and so misses the path if it contains extra /./ type components. Patch below. It seems to work. I haven't touched the test

Bug#548691: getcwd fails to return proper path for relatively-specified roots

2009-09-28 Thread Jameson Rollins
retitle 548691 getcwd fails to return proper paths when root includes '.' thanks So as was pointed out to me, this isn't really an issue of relative vs. absolute, since fakeroot fakechroot chroot root pwd does not use an absolute root path, but doesn't exhibit the problem. Instead, it appears to