currently --no-compression is broken. since 2 years or so.. it's workaroundable as described below, but what do you think?
should we disable the option for now, raising an error that it is broken or such? seems to be an easy fix, i'd look at it, but currently i've got the cough plus butt loads of work. ..ede -------- Original Message -------- Subject: Re: [Duplicity-talk] Backup not restorable with no compression? Date: Mon, 27 Jan 2014 18:03:09 +0100 From: Knut Krause <[email protected]> Reply-To: Discussion of the backup program duplicity <[email protected]> To: [email protected] OK, I'd have to dig into that. Maybe I will. Until then it would be at least great if the option is disabled. This is just 1 minute work for the devs and it would prevent duplicity from creating a backup it cannot restore any more. Knut Am Montag, 27. Januar 2014, 17:39:18 schrieb [email protected]: > good to know! maybe some warm heart comes around and does just that. the > reason that no compression isn't fixed is simply - no one cares enough for > this option, obviously. > > speaking of "you guys should". how about you dig in and supply a patch? > python is not brain surgery ;) > > the lesson for you should be. don't trust, verify! while duplicity is quite > robust, it still has nooks and corners. just now, 0.6.23 fixed a bug that > resulted in data loss when a backup was resumed. > > all this can be easily circumvented by periodically verifying your backups. > > ..ede/duply.net > > On 27.01.2014 16:06, Knut Krause wrote: > > 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 > >> [email protected] > >> https://lists.nongnu.org/mailman/listinfo/duplicity-talk > > > > _______________________________________________ > > Duplicity-talk mailing list > > [email protected] > > https://lists.nongnu.org/mailman/listinfo/duplicity-talk > > _______________________________________________ > Duplicity-talk mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/duplicity-talk _______________________________________________ Duplicity-talk mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/duplicity-talk _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
