Comment 2 for bug 322532

Jamie-

A few notes...

 * I'm going to add bzr to the affected packages, in case those guys have an idea of what might be going on, and what this error actually means. Its possible that bzr is doing something "smart" by looking at underlying data, perhaps?

This looks to be a regression in the ecryptfs kernel code, probably introduced by the filename encryption patch.

Testing your methodology on an ecryptfs WITH filename encryption, it seems to work fine. However, WITHOUT filename encryption, symlink creation seems to break.

I'm pretty sure it has something to do with the actual creation of the symlink. If I untar the tarball in /tmp first, and then rsync -aP to my Private directory, the problem does not exist. I don't understand the difference between the way tar creates symlinks and rsync does, but whatever that difference is, seems to trigger the problem.

I'm subscribing Tyler to the bug. Hopefully he can track down the fix.

:-Dustin