Some tar implementations like star or bsdtar/libarchive support extensions to store ACLs and extended attributes and there seems to be a python wrapper for libarchive: http://code.google.com/p/python-libarchive/
Couldn't that be used by duplicity? Those tar archives would still be usable by say GNU tar which would just warn that it doesn't understand those extensions.
$ touch a b c d
$ setfattr -n user.test a
$ setfacl -m u:nobody:r b
$ chattr +a c
$ bsdtar cf - . | tar tf -
./
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
./c
tar: Ignoring unknown extended header keyword `SCHILY.acl.access'
./b
tar: Ignoring unknown extended header keyword `LIBARCHIVE.xattr.user.test'
./a
./d
Some tar implementations like star or bsdtar/libarchive support extensions to store ACLs and extended attributes and there seems to be a python wrapper for libarchive: http:// code.google. com/p/python- libarchive/
Couldn't that be used by duplicity? Those tar archives would still be usable by say GNU tar which would just warn that it doesn't understand those extensions.
$ touch a b c d xattr.user. test'
$ setfattr -n user.test a
$ setfacl -m u:nobody:r b
$ chattr +a c
$ bsdtar cf - . | tar tf -
./
tar: Ignoring unknown extended header keyword `SCHILY.fflags'
./c
tar: Ignoring unknown extended header keyword `SCHILY.acl.access'
./b
tar: Ignoring unknown extended header keyword `LIBARCHIVE.
./a
./d