Re: [Duplicity-talk] duply fails to determine duplicity version

[edgar . soldin]

it should. alternatively simply set appropriately

# override the used python interpreter, defaults to "python"
#   e.g. "python2" or "/usr/bin/python2.7"
#PYTHON="python"

in the duply profiles.. ede/duply.net

On 3/30/2018 23:41, Scott Classen wrote:
> I have python 2.6.6 installed from the distro and python 2.7 installed from 
> source. 
> This most certainly is the cause of my problems.
> 
> Adding an explicit PYTHONPATH appears to work for determining the version 
> number. Hopefully my overnight cronjobs will work too.
> 
> * * * * *        
> PYTHONPATH=$PYTHONPATH:/usr/local/lib/python2.7/site-packages/ duplicity 
> —version
> 
> Cheers,
> Scott
> 
> 
> 
> 
>> On Mar 30, 2018, at 2:34 PM, address@hidden <mailto:address@hidden> wrote:
>>
>> maybe different python versions? 
>>
>> duplicity uses 'python2', duply 'python'.. not sure why they differ, maybe 
>> Ken changed something. the python version for duply is configurable btw.
>>
>> ..ede/duply.net <http://duply.net/>
>>
>> On 3/30/2018 23:24, Scott Classen wrote:
>>> Hi ede,
>>>
>>> duplicity --version 2>&1 > dupver.txt
>>>
>>> Traceback (most recent call last):
>>>  File "/usr/local/duplicity-0.7.17/bin/duplicity", line 42, in <module>
>>>    import fasteners
>>> ImportError: No module named fasteners
>>>
>>> Which is odd because I know I installed fasteners
>>>
>>> pip list show:
>>>
>>> fasteners (0.14.1)
>>>
>>> Env for cron:
>>> SHELL=/bin/sh
>>> USER=root
>>> PATH=/usr/bin:/bin
>>> PWD=/root
>>> LANG=en_US.UTF-8
>>> SHLVL=1
>>> HOME=/root
>>> LOGNAME=root
>>> _=/usr/bin/env
>>>
>>>
>>>
>>>
>>>
>>>> On Mar 30, 2018, at 2:12 PM, edgar.soldin--- via Duplicity-talk 
>>>> <address@hidden <mailto:address@hidden> <mailto:address@hidden>> wrote:
>>>>
>>>> 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 <http://duply.net/> <http://duply.net/>
>>>>
>>>>
>>>> _______________________________________________
>>>> Duplicity-talk mailing list
>>>> address@hidden <mailto:address@hidden> <mailto:address@hidden>
>>>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>