FS#43510 - [duplicity] 0.7.0 to 0.7.01 breaks gs:// (Google Cloud Storage)

Attached to Project: Community Packages
Opened by Troy Engel (TE) - Monday, 19 January 2015, 17:20 GMT
Last edited by Lukas Fleischer (lfleischer) - Thursday, 29 January 2015, 10:03 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

I have submitted an upstream bug report, including the one minor change/fix I identified that allows it to work again:

https://bugs.launchpad.net/duplicity/+bug/1412514

I would like to request we add a patch to our package until this is fixed upstream, this buglet has broken backups on multiple machines for me. (all using gs:// backends) Here's a simple patch:

--- duplicity-0.7.01/duplicity/backends/botobackend.py-orig 2015-01-19 11:12:43.014227381 -0600
+++ duplicity-0.7.01/duplicity/backends/botobackend.py 2015-01-19 11:12:58.869398971 -0600
@@ -31,4 +31,4 @@
duplicity.backend.register_backend("gs", BotoBackend)
duplicity.backend.register_backend("s3", BotoBackend)
duplicity.backend.register_backend("s3+http", BotoBackend)
-duplicity.backend.uses_netloc.extend([ 'gs', 's3', 's3+http' ])
+duplicity.backend.uses_netloc.extend([ 's3', 's3+http' ])

It's possible upstream may choose to fix this another way, however I confirm the above small patch makes 0.7.01-1 work again and my systems back up to gs:// properly. The patch is based on what I believe to be an accident including 'gs' in that array when it do not exist 0.7.0 when they re-wrote the code - it should not affect any use cases other than gs://.
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Thursday, 29 January 2015, 10:03 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 0.7.01-2.
Comment by Troy Engel (TE) - Tuesday, 20 January 2015, 01:18 GMT
Update: upstream has confirmed and committed a fix; it turns out that s3+http was also broken by the same change. Here is the upstream fix revision:

http://bazaar.launchpad.net/~duplicity-team/duplicity/0.7-series/revision/1058

The broken s3+http was reported by another Arch user.

Loading...