Activity log for bug #1266753

Date Who What changed Old value New value Message
2014-01-07 13:01:40 Kurt Huwig bug added bug
2014-01-07 16:15:14 Reik Keutterling bug added subscriber Reik Keutterling
2014-01-13 09:07:03 Kurt Huwig attachment added Raise an error instead of suppressing connection errors https://bugs.launchpad.net/duplicity/+bug/1266753/+attachment/3947458/+files/1266753.patch
2014-01-13 10:05:56 Louis Bouchard duplicity: status New Confirmed
2014-01-13 10:05:58 Louis Bouchard duplicity: assignee Louis Bouchard (louis-bouchard)
2014-01-13 12:54:50 Kenneth Loafman duplicity: status Confirmed Fix Committed
2014-01-13 12:55:10 Kenneth Loafman duplicity: assignee Louis Bouchard (louis-bouchard)
2014-01-13 15:55:27 Launchpad Janitor branch linked lp:~mterry/duplicity/boto-list-fix
2014-01-13 15:56:05 Michael Terry duplicity: status Fix Committed In Progress
2014-01-13 15:59:03 Kenneth Loafman duplicity: status In Progress Fix Committed
2014-01-13 16:04:17 Louis Bouchard bug added subscriber Louis Bouchard
2014-01-15 12:08:38 Pierre Amadio bug added subscriber Pierre Amadio
2014-01-15 14:07:02 Louis Bouchard bug task added duplicity (Ubuntu)
2014-01-15 14:07:45 Louis Bouchard nominated for series Ubuntu Precise
2014-01-15 14:08:11 Louis Bouchard duplicity (Ubuntu): status New Triaged
2014-01-15 14:08:14 Louis Bouchard duplicity (Ubuntu): importance Undecided Medium
2014-01-15 14:08:16 Louis Bouchard duplicity (Ubuntu): assignee Louis Bouchard (louis-bouchard)
2014-01-15 14:54:22 Chris J Arges bug task added duplicity (Ubuntu Precise)
2014-01-15 14:54:35 Chris J Arges duplicity (Ubuntu Precise): assignee Louis Bouchard (louis-bouchard)
2014-01-15 14:54:37 Chris J Arges duplicity (Ubuntu Precise): importance Undecided Medium
2014-01-15 14:54:39 Chris J Arges duplicity (Ubuntu Precise): status New Triaged
2014-01-15 20:23:14 Ubuntu Foundations Team Bug Bot tags patch
2014-01-15 20:23:27 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Review Team
2014-01-20 13:27:22 Launchpad Janitor branch linked lp:~louis-bouchard/ubuntu/precise/duplicity/fix-s3-and-add-locking
2014-01-20 14:00:30 Louis Bouchard duplicity (Ubuntu Precise): status Triaged In Progress
2014-01-20 14:23:07 Launchpad Janitor branch linked lp:~louis-bouchard/ubuntu/trusty/duplicity/fix-s3-and-add-locking
2014-01-20 15:58:43 Launchpad Janitor branch linked lp:~louis-bouchard/ubuntu/saucy/duplicity/fix-s3-and-add-locking
2014-01-20 15:59:17 Launchpad Janitor branch linked lp:~louis-bouchard/ubuntu/raring/duplicity/fix-s3-and-add-locking
2014-01-20 16:17:16 Louis Bouchard duplicity (Ubuntu): status Triaged In Progress
2014-01-22 13:04:47 Louis Bouchard branch linked lp:~louis-bouchard/ubuntu/precise/duplicity/fix-s3-and-add-locking
2014-01-22 13:05:40 Louis Bouchard branch linked lp:~louis-bouchard/ubuntu/raring/duplicity/fix-s3-and-add-locking
2014-01-22 13:05:51 Louis Bouchard branch linked lp:~louis-bouchard/ubuntu/saucy/duplicity/fix-s3-and-add-locking
2014-01-22 13:06:02 Louis Bouchard branch linked lp:~louis-bouchard/ubuntu/trusty/duplicity/fix-s3-and-add-locking
2014-01-24 12:26:13 Kenneth Loafman duplicity: milestone 0.6.23
2014-01-24 12:31:22 Kenneth Loafman duplicity: importance Undecided Medium
2014-01-24 13:13:20 Kenneth Loafman duplicity: status Fix Committed Fix Released
2014-01-24 14:10:55 Chris J Arges nominated for series Ubuntu Quantal
2014-01-24 14:10:55 Chris J Arges bug task added duplicity (Ubuntu Quantal)
2014-01-24 14:10:55 Chris J Arges nominated for series Ubuntu Saucy
2014-01-24 14:10:55 Chris J Arges bug task added duplicity (Ubuntu Saucy)
2014-01-24 14:14:10 Louis Bouchard duplicity (Ubuntu Quantal): status New In Progress
2014-01-24 14:14:12 Louis Bouchard duplicity (Ubuntu Saucy): status New In Progress
2014-01-24 14:14:15 Louis Bouchard duplicity (Ubuntu Quantal): assignee Louis Bouchard (louis-bouchard)
2014-01-24 14:14:17 Louis Bouchard duplicity (Ubuntu Saucy): assignee Louis Bouchard (louis-bouchard)
2014-01-24 14:14:20 Louis Bouchard duplicity (Ubuntu Quantal): importance Undecided Medium
2014-01-24 14:14:22 Louis Bouchard duplicity (Ubuntu Saucy): importance Undecided Medium
2014-03-06 21:21:50 Chris J Arges description When there is no connection to the S3 backend, the local cache files are deleted. To reproduce: 1. disable the connection to S3 2. run a "collection-status" (basically I run 'duply X status') You'll get a bunch of these: Deleting local /srv/duply-cache/duply_srv/duplicity-inc.20140106T010002Z.to.20140107T010002Z.manifest (not authoritative at backend). Deleting local /srv/duply-cache/duply_srv/duplicity-new-signatures.20131211T124323Z.to.20131211T124519Z.sigtar.gz (not authoritative at backend). This is fatal if you run it in a configuration using GPG and having only the public key for encryption as well as a separate signing key. Then you cannot backup any more, as the decrypted local cache has been deleted and the files on the S3 are encrypted. Probably reason: There is no check if the connection to the backend could be established Workaround: If you replace at http://bazaar.launchpad.net/~duplicity-team/duplicity/0.6-series/view/head:/duplicity/backends/_boto_single.py#L270 the line return [] with return None Then duplicity will crash instead of deleting the local files. Not the proper solution but at least you can do a backup when the connection comes back up. SRU Justification [Impact] * When there is no connection to the S3 backend, the local cache files are deleted. [Test Case] 1. disable the connection to S3 2. run a "collection-status" (basically I run 'duply X status') [Regression Potential] * Already fixed in latest duplicity. Needs to be fixed in lockstep with deja-dup as it Breaks: deja-dup (<< 27.3.1-0ubuntu2 ). -- When there is no connection to the S3 backend, the local cache files are deleted. To reproduce: 1. disable the connection to S3 2. run a "collection-status" (basically I run 'duply X status') You'll get a bunch of these: Deleting local /srv/duply-cache/duply_srv/duplicity-inc.20140106T010002Z.to.20140107T010002Z.manifest (not authoritative at backend). Deleting local /srv/duply-cache/duply_srv/duplicity-new-signatures.20131211T124323Z.to.20131211T124519Z.sigtar.gz (not authoritative at backend). This is fatal if you run it in a configuration using GPG and having only the public key for encryption as well as a separate signing key. Then you cannot backup any more, as the decrypted local cache has been deleted and the files on the S3 are encrypted. Probably reason: There is no check if the connection to the backend could be established Workaround: If you replace at http://bazaar.launchpad.net/~duplicity-team/duplicity/0.6-series/view/head:/duplicity/backends/_boto_single.py#L270 the line     return [] with     return None Then duplicity will crash instead of deleting the local files. Not the proper solution but at least you can do a backup when the connection comes back up.
2014-03-12 08:09:54 Chris Halse Rogers duplicity (Ubuntu Saucy): status In Progress Fix Committed
2014-03-12 08:09:58 Chris Halse Rogers bug added subscriber Ubuntu Stable Release Updates Team
2014-03-12 08:10:01 Chris Halse Rogers bug added subscriber SRU Verification
2014-03-12 08:10:05 Chris Halse Rogers tags patch patch verification-needed
2014-03-12 08:18:29 Launchpad Janitor branch linked lp:ubuntu/saucy-proposed/duplicity
2014-03-26 14:45:04 Louis Bouchard tags patch verification-needed patch verification-done
2014-03-27 20:34:23 Brian Murray tags patch verification-done patch verification-done-saucy
2014-03-27 20:39:47 Brian Murray description SRU Justification [Impact] * When there is no connection to the S3 backend, the local cache files are deleted. [Test Case] 1. disable the connection to S3 2. run a "collection-status" (basically I run 'duply X status') [Regression Potential] * Already fixed in latest duplicity. Needs to be fixed in lockstep with deja-dup as it Breaks: deja-dup (<< 27.3.1-0ubuntu2 ). -- When there is no connection to the S3 backend, the local cache files are deleted. To reproduce: 1. disable the connection to S3 2. run a "collection-status" (basically I run 'duply X status') You'll get a bunch of these: Deleting local /srv/duply-cache/duply_srv/duplicity-inc.20140106T010002Z.to.20140107T010002Z.manifest (not authoritative at backend). Deleting local /srv/duply-cache/duply_srv/duplicity-new-signatures.20131211T124323Z.to.20131211T124519Z.sigtar.gz (not authoritative at backend). This is fatal if you run it in a configuration using GPG and having only the public key for encryption as well as a separate signing key. Then you cannot backup any more, as the decrypted local cache has been deleted and the files on the S3 are encrypted. Probably reason: There is no check if the connection to the backend could be established Workaround: If you replace at http://bazaar.launchpad.net/~duplicity-team/duplicity/0.6-series/view/head:/duplicity/backends/_boto_single.py#L270 the line     return [] with     return None Then duplicity will crash instead of deleting the local files. Not the proper solution but at least you can do a backup when the connection comes back up. N.B. This should not be released until after deja-dup - bug 1281066. SRU Justification [Impact]  * When there is no connection to the S3 backend, the local cache files are deleted. [Test Case]  1. disable the connection to S3  2. run a "collection-status" (basically I run 'duply X status') [Regression Potential]  * Already fixed in latest duplicity. Needs to be fixed in lockstep with deja-dup as it Breaks: deja-dup (<< 27.3.1-0ubuntu2 ). -- When there is no connection to the S3 backend, the local cache files are deleted. To reproduce: 1. disable the connection to S3 2. run a "collection-status" (basically I run 'duply X status') You'll get a bunch of these: Deleting local /srv/duply-cache/duply_srv/duplicity-inc.20140106T010002Z.to.20140107T010002Z.manifest (not authoritative at backend). Deleting local /srv/duply-cache/duply_srv/duplicity-new-signatures.20131211T124323Z.to.20131211T124519Z.sigtar.gz (not authoritative at backend). This is fatal if you run it in a configuration using GPG and having only the public key for encryption as well as a separate signing key. Then you cannot backup any more, as the decrypted local cache has been deleted and the files on the S3 are encrypted. Probably reason: There is no check if the connection to the backend could be established Workaround: If you replace at http://bazaar.launchpad.net/~duplicity-team/duplicity/0.6-series/view/head:/duplicity/backends/_boto_single.py#L270 the line     return [] with     return None Then duplicity will crash instead of deleting the local files. Not the proper solution but at least you can do a backup when the connection comes back up.
2014-03-27 21:04:25 Brian Murray duplicity (Ubuntu Precise): status In Progress Fix Committed
2014-03-27 21:04:31 Brian Murray tags patch verification-done-saucy patch verification-done-saucy verification-needed
2014-03-27 21:28:08 Launchpad Janitor branch linked lp:ubuntu/precise-proposed/duplicity
2014-03-31 08:48:47 Louis Bouchard tags patch verification-done-saucy verification-needed patch verification-done verification-done-saucy
2014-04-10 23:29:12 Launchpad Janitor duplicity (Ubuntu Precise): status Fix Committed Fix Released
2014-04-10 23:29:26 Brian Murray removed subscriber Ubuntu Stable Release Updates Team
2014-04-10 23:30:01 Launchpad Janitor duplicity (Ubuntu Saucy): status Fix Committed Fix Released
2014-04-10 23:35:49 Brian Murray duplicity (Ubuntu): status In Progress Fix Released
2014-04-10 23:49:11 Launchpad Janitor branch linked lp:ubuntu/precise-updates/duplicity
2014-04-23 08:46:32 Louis Bouchard duplicity (Ubuntu Quantal): status In Progress Won't Fix