It took me several attempts to setup bups, it seemed to abort when it encountered errors due to some files.
Permission denied for .dbus: For what ever reason this folder in the user directory is unaccessible, this is something most users are not aware of. As a workaround one can of course add ~/.dbus on the exclude list.
read Linux attr: [Errno 13] Permission denied: '/home/username/.dbus/'
Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in <module>
update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 164, in update_index
wi.add(path, pst, meta_ofs, hashgen=fake_hash)
File "/usr/lib/bup/bup/index.py", line 565, in add
self._add(ename, e)
File "/usr/lib/bup/bup/index.py", line 533, in _add
% (''.join(ename), ''.join(self.lastfile)))
When the home directory is encrypted with ecryptfs, the encrypted files are stored in .Private. I don't know what that error means, but since bup takes up the unencrypted files anyways, I put it on my exclude list.
bup.index.Error: '/home/username/.Private' must come before '/home/username/.Private'
These are issues that many users will encounter and that are not bup/bups' fault. There may even be other system software that creates root-owned files in home (as pulseaudio did). Since these errors are caused by individual files, I wonder whether it makes sense to abort backing up all other files, or whether these errors should be handled somehow?
Show a prompt about the error and ask the user whether to continue:
[Abort] [Continue] [Continue and add files … on exclude list]
Or just continue backing up other files first and show a summary of not backuped files.
It took me several attempts to setup bups, it seemed to abort when it encountered errors due to some files.
.dbus: For what ever reason this folder in the user directory is unaccessible, this is something most users are not aware of. As a workaround one can of course add~/.dbuson the exclude list..Private. I don't know what that error means, but since bup takes up the unencrypted files anyways, I put it on my exclude list.These are issues that many users will encounter and that are not bup/bups' fault. There may even be other system software that creates root-owned files in home (as pulseaudio did). Since these errors are caused by individual files, I wonder whether it makes sense to abort backing up all other files, or whether these errors should be handled somehow?
Show a prompt about the error and ask the user whether to continue: [Abort] [Continue] [Continue and add files … on exclude list]
Or just continue backing up other files first and show a summary of not backuped files.