[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] duply fails to determine duplicity version
From: |
edgar . soldin |
Subject: |
Re: [Duplicity-talk] duply fails to determine duplicity version |
Date: |
Fri, 30 Mar 2018 23:12:31 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 |
On 3/30/2018 18:09, Scott Classen via Duplicity-talk wrote:
> Hello,
>
> I updated from duplicity 0.7.13 to 0.7.17 yesterday as well s duply 2.0.1 to
> 2.0.4
>
> Last night all of my duply cron jobs failed to determine the duplicity
> version:
>
>> Start duply v2.0.4, time is 2018-03-30 03:30:01.
>>
>> INFO:
>>
>> duplicity version check failed (please report, this is a bug)
>>
>> Using profile '/etc/duply/xxxxxxxx'.
>> Using installed duplicity version MISSING, python 2.7.13, gpg 2.0.14 (Home:
>> ~/.gnupg), awk 'GNU Awk 3.1.7', grep 'grep (GNU grep) 2.20', bash
>> '4.1.2(2)-release (x86_64-redhat-linux-gnu)’.
>
>
> The backup appears to have completed, but I was instructed to report this as
> a bug.
>
hey Scott,
could you please post the 'duplicity --version' output from the command line?
if it looks normal could you quickly add a test cronjob like
* * * * * duplicity --version 2>&1 > /tmp/dupversionout.txt
and attach the resulting text file '/tmp/dupversionout.txt'?
thanks ..ede/duply.net