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
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ecryptfs-utils (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Tyler Hicks (tyhicks)
Status: New => Confirmed
--
ecryptfs does not handle symlinks within bzr
https://bugs.launchpad.net/bugs/322532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
