Duplicity will not produce .tar.bz2.gpg extensions, it will produce
...tar.gz or ...tar.gpg extensions.
What is the full command line you are using? Do you know what version
of duplicity you have?
...Ken
Madhusudan Singh wrote:
The google search did reveal that I should be getting
.tar.bz2.gpg extensions. So, I do not know if my mac's version of
duplicity is broken somehow (unlikely, since it passes on this task to
gpg) or its a gpg problem.
From a pure size expectation perspective, it does not look like
that the files generated at bzipped (from what I know of the chuck
size, and the actual files that went into the chunk). How can I check
(remove the gpg extension first, somehow) ?
On Thu, Aug 26, 2010 at 5:02 PM, Scott
Hannahs <address@hidden> wrote:
Those
are man page arguments for gpg.
But arguments to gpg will not change or set the filenames generated by
duplicity?
-Scott
On Aug 26, 2010, at 17:25, Madhusudan Singh wrote:
That is what I have found on googling. Are these options valid options
for gpg ?
On Thu, Aug 26, 2010 at 2:00 PM, Olivier Berger <address@hidden> wrote:
Le mercredi 18 août 2010 à 09:57 -0500, Madhusudan Singh a écrit :
> 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.
>
Uh... are you sure this relates to gpg-options ? ... doesn't have
anything to do with GPG operations, I would say...
_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk
|
signature.asc