duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] full backups failing using duply


From: edgar . soldin
Subject: Re: [Duplicity-talk] full backups failing using duply
Date: Tue, 14 Oct 2014 13:13:12 +0200
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.2

debian is usually very slow in adopting new package versions..

best you install duplicity/duply manually from tarball. here is a mini howto
 http://duply.net/wiki/index.php/Duply-documentation

get the tarballs from
http://duply.net
http://duplicity.nongnu.org/

..ede/duply.net

On 14.10.2014 12:28, Pacuraru, Ovidiu wrote:
> Looking into it but this is a Debian Wheezy installation and all packages you 
> mentioned are up-to-date (at least according to my Debian version) - could 
> try and install them from unstable?
> 
> 
> -- 
> The information in this email and attachments hereto may contain legally 
> privileged, proprietary or confidential information that is intended for a 
> particular recipient. If you are not the intended recipient(s), or the 
> employee or agent responsible for delivery of this message to the intended 
> recipient(s), you are hereby notified that any disclosure, copying, 
> distribution, retention or use of the contents of this e-mail information is 
> prohibited and may be unlawful. When addressed to customers or vendors, any 
> information contained in this e-mail is subject to the terms and conditions 
> in the governing contract, if applicable. If you have received this 
> communication in error, please immediately notify us by return e-mail, 
> permanently delete any electronic copies of this communication and destroy 
> any paper copies.
> 
> On 13 October 2014 17:13, <address@hidden <mailto:address@hidden>> wrote:
> 
>     probably
>      https://answers.launchpad.net/duplicity/+question/253609
> 
>     but first!
>     - update your duply/duplicity .. your versions are very old!
>     - update python boto to the latest version
> 
>     check if the error persists after you updated. ..ede
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]