** Description changed: Let's say your backup contains a directory without write permissions (a common example is apparently the Jaunty Ubuntu One directory). When restoring that directory, you will get errors about any files under that directory (because Deja Dup can't move files into it!). The fix is to set directory permissions after writing subfiles and to fallback to copying from the temporary restore directory if moves don't work. + + For an Ubuntu 9.10 SRU: + + There are three closely related bugs: + - Restoring files from a read-only directory fails + - Restoring a file from a directory that doesn't exist yet fails + - Restoring a single file downloads all files + + The first two can manifest themselves as data loss (or at least, no easy + way to get your data that is locked inside your backup). The last could + make it very difficult to restore specific data if you are short on disk + space (would need to use a different computer). Thus, the SRU request. + + The first (read-only directory) is more common than the other problems + -- apparently the Jaunty Ubuntu One folder was read-only. + + This was fixed in Lucid by pushing new upstream version 11.1-0ubuntu1, + which included the fix. The attached patch for Karmic is modified from + upstream bug-fix release 10.3. + + To reproduce, create a folder that is read only. Put some files in it. + Back up that folder with Deja Dup. Move the folder out of the way. Run + Deja Dup, click restore, and restore the files in their original + location. With 10.2, it fails. With 10.2+patch, it succeeds. + + There shouldn't be much of a regression potential. The code changes are + light.
-- Can't restore files in a read-only directory https://bugs.launchpad.net/bugs/483631 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
