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

[Scott Classen]

My duplicity installation is slightly modified (mostly because of my dual 
python problem). I’m including my installation notes here so you can wee that I 
substituted python2 with python in several duplicity scripts which may inform 
your interpretation of the subsequent commands:


# get duplicity 0.7.17
cd /usr/local/src/
wget 
https://code.launchpad.net/duplicity/0.7-series/0.7.17/+download/duplicity-0.7.17.tar.gz
tar zxvf duplicity-0.7.17.tar.gz 
cd duplicity-0.7.17

# edit the following files to change from python2 (2.6.6) to python (2.7.13)
cp bin/duplicity bin/duplicity.bak ; sed -i 's/python2/python/g' bin/duplicity
cp bin/rdiffdir bin/rdiffdir.bak ; sed -i 's/python2/python/g' bin/rdiffdir
cp dist/makedist dist/makedist.bak ; sed -i 's/python2/python/g' dist/makedist
cp duplicity/compilec.py duplicity/compilec.py.bak ; sed -i 
's/python2/python/g' duplicity/compilec.py
cp duplicity/backend.py duplicity/backend.py.bak ; sed -i 's/python2/python/g' 
duplicity/backend.py
cp setup.py setup.py.bak ; sed -i 's/python2/python/g' setup.py

# install everywhere
python setup.py install
python setup.py install --prefix=/usr
python setup.py install --prefix=/usr/local
python setup.py install --prefix=/usr/local/duplicity-0.7.17



# duply version
duply version 2.0.4
Using installed duplicity version 0.7.17, 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)'.

# PYTHON=python duply version
duply version 2.0.4
Using installed duplicity version 0.7.17, 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)'.

# PYTHON=python2 duply version
duply version 2.0.4
Using installed duplicity version 0.7.17, python 2.6.6, 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)'.




# duply version
duply version 2.0.5dev
Using installed duplicity version 0.7.17, python 2.7.13 
(/usr/local/bin/python), 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)'.

# PYTHON=python duply version
duply version 2.0.5dev
Using installed duplicity version 0.7.17, python 2.7.13 
(/usr/local/bin/python), 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)'.

# PYTHON=python2 duply version
  duply version 2.0.5dev


  
INFO:

duplicity version check failed (please report, this is a bug)
the command
  python2 /usr/local/bin/duplicity --version 2>&1
resulted in
  Traceback (most recent call last):
  File "/usr/local/bin/duplicity", line 42, in <module>
    import fasteners
ImportError: No module named fasteners


Using installed duplicity version INVALID, python 2.6.6 (/usr/bin/python2), 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)'.



> On Apr 2, 2018, at 1:44 AM, address@hidden wrote:
> 
> hey Scott,
> 
> because of your setup i found an inconsistency in duply, which will hopefully 
> be fixed in the next version. would  you be willing to try the latest snapshot
>  http://duply.net/wiki/index.php/Duply-code#Latest_Development_Snapshot
> 
> and run
> 
> duply version
> PYTHON=python duply version
> PYTHON=python2 duply version
> 
> and send me the output? ..thanks ede/duply.net
> 
> On 3/30/2018 23:45, edgar.soldin--- via Duplicity-talk wrote:
>> 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
>>> 
>> 
>> 
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>> 
>