As far as I can tell, you made no changes to the file that was released.
Could you provide a diff of the file?
On Sun, Apr 10, 2016 at 11:53 PM, Florian Kruse <email address hidden> wrote:
> Issue was introduced here, I believe:
>
> http://bazaar.launchpad.net/~duplicity-
> team/duplicity/0.7-series/revision/1175
>
>
> ** Summary changed:
>
> - duplicity failing to use existing bucket in boto backend
> + duplicity fails to use existing S3 bucket in boto backend
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1568677
>
> Title:
> duplicity fails to use existing S3 bucket in boto backend
>
> Status in Duplicity:
> New
>
> Bug description:
> I recently updated to duplicity 0.7.07 and suddenly my backup to S3
> fails. I believe, I managed to trace the issue to
> duplicity/backends/_boto_single.py. I am running
>
> /usr/bin/duplicity --name duply_system --verbosity 9 / s3://s3-eu-
> central-1.amazonaws.com/my_bucket/duplicity
>
> with the environment variables
>
> S3_USE_SIGV4=True
> AWS_ACCESS_KEY_ID=MYACCESSKEY
> AWS_SECRET_ACCESS_KEY=MYSECRET
>
> This fails with the output given below (line number in _boto_single.py
> approximate as I added some debug output). I managed to reconstruct:
> In my case, BotoBackend._list fails as self.bucket is None. Before,
> BotoBackend.resetConnection is called, which sets self.bucket to None.
> Inside BotoBackend.resetConnection, self.bucket is only set to a valid
> bucket in case the bucket does not yet exist (in which case it is
> created via self.conn.create_bucket). In case the bucket already
> exists, self.bucket is left None. No other attempt inside BotoBackend
> is made to set self.bucket, eventually letting BotoBackend._list fail.
>
> Output of call:
>
> Using archive dir: /root/.cache/duplicity/duply_system
> Using backup name: duply_system
> Import of duplicity.backends.acdclibackend Succeeded
> Import of duplicity.backends.azurebackend Succeeded
> Import of duplicity.backends.b2backend Succeeded
> Import of duplicity.backends.botobackend Succeeded
> Import of duplicity.backends.cfbackend Succeeded
> Import of duplicity.backends.copycombackend Succeeded
> Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
> Import of duplicity.backends.gdocsbackend Succeeded
> Import of duplicity.backends.giobackend Succeeded
> Import of duplicity.backends.hsibackend Succeeded
> Import of duplicity.backends.hubicbackend Succeeded
> Import of duplicity.backends.imapbackend Succeeded
> Import of duplicity.backends.lftpbackend Succeeded
> Import of duplicity.backends.localbackend Succeeded
> Import of duplicity.backends.mediafirebackend Succeeded
> Import of duplicity.backends.megabackend Succeeded
> Import of duplicity.backends.multibackend Succeeded
> Import of duplicity.backends.ncftpbackend Succeeded
> Import of duplicity.backends.onedrivebackend Succeeded
> Import of duplicity.backends.par2backend Succeeded
> Import of duplicity.backends.pydrivebackend Succeeded
> Import of duplicity.backends.rsyncbackend Succeeded
> Import of duplicity.backends.ssh_paramiko_backend Succeeded
> Import of duplicity.backends.ssh_pexpect_backend Succeeded
> Import of duplicity.backends.swiftbackend Succeeded
> Import of duplicity.backends.sxbackend Succeeded
> Import of duplicity.backends.tahoebackend Succeeded
> Import of duplicity.backends.webdavbackend Succeeded
> Main action: inc
>
> ================================================================================
> duplicity 0.7.07 ($reldate)
> Args: /usr/bin/duplicity --name duply_system --verbosity 9 / s3://
> s3-eu-central-1.amazonaws.com/backup-git.point-8.de-gitlab/duplicity
> Linux git 4.2.0-35-generic #40~14.04.1-Ubuntu SMP Fri Mar 18 16:37:35
> UTC 2016 x86_64 x86_64
> /usr/bin/python 2.7.6 (default, Jun 22 2015, 17:58:13)
> [GCC 4.8.2]
>
> ================================================================================
> Using temporary directory /tmp/duplicity-OwOHZf-tempdir
> Registering (mkstemp) temporary file
> /tmp/duplicity-OwOHZf-tempdir/mkstemp-gDTnhP-1
> Temp has 35986862080 available, backup will use approx 34078720.
> Backtrace of previous error: Traceback (innermost last):
> File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line
> 367, in inner_retry
> return fn(self, *args)
> File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line
> 569, in list
> return [tobytes(x) for x in self.backend._list()]
> File
> "/usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py", line
> 253, in _list
> raise BackendException("No connection to backend")
> BackendException: No connection to backend
>
> Attempt 1 failed. BackendException: No connection to backend
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1568677/+subscriptions
>
As far as I can tell, you made no changes to the file that was released.
Could you provide a diff of the file?
On Sun, Apr 10, 2016 at 11:53 PM, Florian Kruse <email address hidden> wrote:
> Issue was introduced here, I believe: bazaar. launchpad. net/~duplicity- 0.7-series/ revision/ 1175 /bugs.launchpad .net/bugs/ 1568677 backends/ _boto_single. py. I am running 1.amazonaws. com/my_ bucket/ duplicity KEY_ID= MYACCESSKEY ACCESS_ KEY=MYSECRET resetConnection is called, which sets self.bucket to None. resetConnection , self.bucket is only set to a valid create_ bucket) . In case the bucket already cache/duplicity /duply_ system backends. acdclibackend Succeeded backends. azurebackend Succeeded backends. b2backend Succeeded backends. botobackend Succeeded backends. cfbackend Succeeded backends. copycombackend Succeeded backends. dpbxbackend Failed: No module named dropbox backends. gdocsbackend Succeeded backends. giobackend Succeeded backends. hsibackend Succeeded backends. hubicbackend Succeeded backends. imapbackend Succeeded backends. lftpbackend Succeeded backends. localbackend Succeeded backends. mediafirebacken d Succeeded backends. megabackend Succeeded backends. multibackend Succeeded backends. ncftpbackend Succeeded backends. onedrivebackend Succeeded backends. par2backend Succeeded backends. pydrivebackend Succeeded backends. rsyncbackend Succeeded backends. ssh_paramiko_ backend Succeeded backends. ssh_pexpect_ backend Succeeded backends. swiftbackend Succeeded backends. sxbackend Succeeded backends. tahoebackend Succeeded backends. webdavbackend Succeeded ======= ======= ======= ======= ======= ======= ======= ======= ======= ======= === 1.amazonaws. com/backup- git.point- 8.de-gitlab/ duplicity ======= ======= ======= ======= ======= ======= ======= ======= ======= ======= === OwOHZf- tempdir OwOHZf- tempdir/ mkstemp- gDTnhP- 1 python2. 7/dist- packages/ duplicity/ backend. py", line python2. 7/dist- packages/ duplicity/ backend. py", line _list() ] python2. 7/dist- packages/ duplicity/ backends/ _boto_single. py", line n("No connection to backend") /bugs.launchpad .net/duplicity/ +bug/1568677/ +subscriptions
>
> http://
> team/duplicity/
>
>
> ** Summary changed:
>
> - duplicity failing to use existing bucket in boto backend
> + duplicity fails to use existing S3 bucket in boto backend
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https:/
>
> Title:
> duplicity fails to use existing S3 bucket in boto backend
>
> Status in Duplicity:
> New
>
> Bug description:
> I recently updated to duplicity 0.7.07 and suddenly my backup to S3
> fails. I believe, I managed to trace the issue to
> duplicity/
>
> /usr/bin/duplicity --name duply_system --verbosity 9 / s3://s3-eu-
> central-
>
> with the environment variables
>
> S3_USE_SIGV4=True
> AWS_ACCESS_
> AWS_SECRET_
>
> This fails with the output given below (line number in _boto_single.py
> approximate as I added some debug output). I managed to reconstruct:
> In my case, BotoBackend._list fails as self.bucket is None. Before,
> BotoBackend.
> Inside BotoBackend.
> bucket in case the bucket does not yet exist (in which case it is
> created via self.conn.
> exists, self.bucket is left None. No other attempt inside BotoBackend
> is made to set self.bucket, eventually letting BotoBackend._list fail.
>
> Output of call:
>
> Using archive dir: /root/.
> Using backup name: duply_system
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Import of duplicity.
> Main action: inc
>
> =======
> duplicity 0.7.07 ($reldate)
> Args: /usr/bin/duplicity --name duply_system --verbosity 9 / s3://
> s3-eu-central-
> Linux git 4.2.0-35-generic #40~14.04.1-Ubuntu SMP Fri Mar 18 16:37:35
> UTC 2016 x86_64 x86_64
> /usr/bin/python 2.7.6 (default, Jun 22 2015, 17:58:13)
> [GCC 4.8.2]
>
> =======
> Using temporary directory /tmp/duplicity-
> Registering (mkstemp) temporary file
> /tmp/duplicity-
> Temp has 35986862080 available, backup will use approx 34078720.
> Backtrace of previous error: Traceback (innermost last):
> File "/usr/lib/
> 367, in inner_retry
> return fn(self, *args)
> File "/usr/lib/
> 569, in list
> return [tobytes(x) for x in self.backend.
> File
> "/usr/lib/
> 253, in _list
> raise BackendExceptio
> BackendException: No connection to backend
>
> Attempt 1 failed. BackendException: No connection to backend
>
> To manage notifications about this bug go to:
> https:/
>