[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Backup not restorable with no compression?
|
From: |
Knut Krause |
|
Subject: |
Re: [Duplicity-talk] Backup not restorable with no compression? |
|
Date: |
Mon, 27 Jan 2014 16:06:57 +0100 |
|
User-agent: |
KMail/4.12.1 (Linux/3.12.9-1-ARCH; KDE/4.12.1; x86_64; ; ) |
Just for your information: renaming the *.difftar files to *.difftar.gz seems
to result in a working restore again.
You guys should really either remove or FIX the --no-compression option
though. This is behaviour is not acceptable for backup software.
Knut
Am Montag, 27. Januar 2014, 15:21:14 schrieb Knut Krause:
> Hi,
>
> I created a backup using --no-compression. The filenames are
> duplicity-inc.20140113T152430Z.to.20140123T112751Z.vol8.difftar
> without the .gz ending.
>
> file on the other hand says:
> duplicity-inc.20140113T152430Z.to.20140123T112751Z.vol9.difftar:
> gzip compressed data, last modified: Thu Jan 23 13:16:42 2014, max
> compression
>
> Now I found
> http://lists.gnu.org/archive/html/duplicity-talk/2013-03/msg00001.html and
> https://bugs.launchpad.net/duplicity/+bug/1029516
> which suggests that this option is buggy since 2012.
>
> Any suggestions how to fix this? Can I just rename the files to *.gz or will
> this break the signature stuff?
>
>
> Knut
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk