get_bucket unknown keyword location and my_location name error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
There are two bugs in duplicity/
1) my_location is used instead of self.my_location causing:
NameError: global name 'my_location' is not defined
2) An unknown keyword argument location is passed to get_bucker (copy paste error from create_bucket)
See: https:/
The attached patch fixes both problems.
Versions:
duplicity 0.7.07+bzr1206
Python 2.7.6
Ubuntu 14.04.4 LTS
boto 2.39.0
bucket in eu-central-1 location (requires AWS4 auth)
Backtrace of my_location name error:
Traceback (most recent call last):
File "/usr/bin/
with_
File "/usr/bin/
fn()
File "/usr/bin/
action = commandline.
File "/usr/lib/
backup, local_pathname = set_backend(
File "/usr/lib/
globals.backend = backend.
File "/usr/lib/
obj = get_backend_
File "/usr/lib/
return factory(pu)
File "/usr/lib/
self.
File "/usr/lib/
location=
NameError: global name 'my_location' is not defined
The unknown keyword error is in roughly the same location, so backtrace omitted.
Changed in duplicity: | |
status: | New → Fix Released |
milestone: | none → 0.7.08 |
importance: | Undecided → Medium |
Changed in duplicity: | |
milestone: | 0.7.08 → 0.7.07.1 |
Thanks Kenneth, working fine in duplicity 0.7.07+bzr1207.