[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Error with 0.60
From: |
Kenneth Loafman |
Subject: |
Re: [Duplicity-talk] Error with 0.60 |
Date: |
Mon, 15 Jun 2009 09:51:56 -0500 |
User-agent: |
Thunderbird 2.0.0.21 (X11/20090318) |
Ian Barton wrote:
> Ian Barton wrote:
>> Kenneth Loafman wrote:
>>> Ian Barton wrote:
>>>> I have just upgraded on my notebook. When I run:
>>>>
>>>> /usr/bin/duplicity --encrypt-key "81AEC9E9" --full-if-older-than 7D
>>>> /home/ian/Documents
>>>> scp://address@hidden//media/usbdisk/duplicity/scamper/Documents
>>>>
>>>>
>>>> I get the following error:
>>>>
>>>> Last full backup is too old, forcing full backup
>>>> Traceback (most recent call last):
>>>> File "/usr/bin/duplicity", line 582, in <module>
>>>> with_tempdir(main)
>>>> File "/usr/bin/duplicity", line 576, in with_tempdir
>>>> fn()
>>>> File "/usr/bin/duplicity", line 557, in main
>>>> full_backup(col_stats)
>>>> File "/usr/bin/duplicity", line 233, in full_backup
>>>> sig_outfp = get_sig_fileobj("full-sig")
>>>> File "/usr/bin/duplicity", line 217, in get_sig_fileobj
>>>> fh.addfilehandle(dup_temp.get_fileobj_duppath(globals.archive_dir,
>>>> AttributeError: FileobjHooked instance has no attribute 'addfilehandle'
>>>
>>> Ummm, if you upgraded to 0.6.0, then somehow the old version of
>>> duplicity is still being run. get_sig_fileobj begins on line 360 in
>>> 0.6.0 and does not contain addfilehandle at all. Sounds like you need
>>> to redo the install.
>>>
>> It appears that 0.6.0 got installed in /usr/local/bin and the previous
>> version is in /usr/bin, where I would expect it to be. I just ran sudo
>> python setup.py as usual. It's late and I am tired, so I'll
>> investigate further in the morning.
>>
> I suspect that the problem may have arisen because this system was
> upgraded from Intrepid to Jaunty and has both Python 2.5 and 2.6 installed.
>
> I have manually removed the old 0.5.08 packages and re-installed 0.6.0.
> Duplicity now works correctly. However, there is one thing that is
> puzzling me. Previous to 0.6.0 the installer always placed duplicity in
> /usr/bin and now it defaults to /usr/local/bin.
>
> I haven't change the way I run the installer: sudo python setup.py
> install. Reading the distutils docs for python 2.5 and 2.6 indicates
> that the default was always /usr/local/bin, so I don't know why it
> originally ended up in /usr/bin.
Is it possible you installed it via a distro package? I'm not sure what
you're running, but I think some distros do put it in /usr/bin.
...Ken
signature.asc
Description: OpenPGP digital signature