Re: [Duplicity-talk] Broken after 0.5.10 upgrade

[Kenneth Loafman]

Simon Ravnič wrote:
> Hi!
> 
> I upgraded 0.5.08 (which worked flawlessly) to 0.5.10 and now it's broken:
> 
> E.g.
> # duplicity --version
> 
> Traceback (most recent call last):
>   File "/usr/bin/duplicity", line 34, in ?
>     import duplicity.backends
>   File
> "/usr/lib/python2.4/site-packages/duplicity/backends/__init__.py", line
> 30, in ?
>     import duplicity.backends.botobackend
>   File
> "/usr/lib/python2.4/site-packages/duplicity/backends/botobackend.py",
> line 25, in ?
>     import duplicity.backend
>   File "/usr/lib/python2.4/site-packages/duplicity/backend.py", line 34,
> in ?
>     import duplicity.dup_temp as dup_temp
>   File "/usr/lib/python2.4/site-packages/duplicity/dup_temp.py", line
> 25, in ?
>     import log, path, file_naming
>   File "/usr/lib/python2.4/site-packages/duplicity/path.py", line 30, in ?
>     import librsync, log, dup_time
>   File "/usr/lib/python2.4/site-packages/duplicity/dup_time.py", line
> 47, in ?
>     bad_interval_string = _("""Bad interval string "%s"
> NameError: name '_' is not defined
> 
> I'm using Debian and installed Duplicity with "python setup.py install"
> in the source directory. What to do now expect of learning that one
> should not try to fix something if it aint broken.

Weird!  I tested (as always) on Python 2.3, 2.4, 2.5, and 2.6, and I did
not see this at all.  The '_' function is installed by gettext in the
main module and should be available to all modules from that point on.
I'm wondering what version of Python you have.. Is it perhaps 2.4.0?

Could you reinstall the package and post the install logs?
# python setup.py install >& install.log

This would happen if a previous version of duplicity main were somehow
mixed with the newer modules, so I'm thinking an install problem.

...Thanks,
...Ken

signature.asc
Description: OpenPGP digital signature