Re: [Duplicity-talk] Re: BZIP2 support on Mac OSX does not seem to work

[Madhusudan Singh]

On Thu, Aug 26, 2010 at 6:22 PM, Tim Riemenschneider <address@hidden> wrote:

Am 18.08.2010 17:37, schrieb Madhusudan Singh:

The .tar.gpg should read .difftar.gpg. The question stands.

On Wed, Aug 18, 2010 at 9:57 AM, Madhusudan Singh <address@hidden> wrote:

Hello,

I am trying to use duplicity (latest version and dependencies from MacPorts) to create .tar.bz2.gpg (compressed and encrypted) backups on a remote Linux server.

I am using --gpg-options='--compress-algo=bzip2 --bzip2-compress-level=9' as the command line option as suggested in various discussions accessible via Google.

However, the remote backups created are .tar.gpg (and hence are not compressed).

So the filename is still the same, who cares? The filename / file extension does not define the filetype. (At least not on anything but Windows)
So gpg probably uses bzip.
To be sure, you could create 2 backups of the same files (to different diretories) and compare sizes.
(The fileextension .difftar.gpg does not mean the files are uncompressed. They are probably gzip-compressed with the default-options)

cu
Tim

_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk

I should have thought of that. The sizes for some of the chunks do not look right, but I will check.

For instance, I have a 6 MB text file (I am using verbose mode, so I know which file is being worked on). With a chunk size of 5 MB, this file is split over two chunks (one complete chunk of the first, and partially, the second, strongly suggesting that the file was not compressed). Normally, text files compress extremely well. A separate bzip2 command on the file (unencrypted) yields a file that is 1.2 MB in size.